Error calling VB .dll from SQL Trigger

[pdx1ajm]

This may be a VB question, but it only happens when called from sqlServer(MSDE) , so I'll post it in both places.

Using the sp_aocreate and sp_oamethod objects I am succesfully calling an ActiveX .dll written in VB. Whenever I call it from sqlServer, though, I get an error returned ('482 Printer Error') - regardless of whether I use the Windows API or the .printform method.

I can succesfully call this .dll from a standard VB executable, and I do have Visual Studio SP 5.

Any known conflicts between SQL Server and the printer object? Any ideas?

 

[pdx1ajm]

Answered my own question. It seems SQL Server, by default, logs in to the System account which, by default, has no printers assigned to it. Two options for repair - reset the SQL server service to log into some other account OR adjust the registry to assign the necessary printers to the System account.