Sage Accpac 5.6, VB6, Windows 7

[Bluejay07]

Hello,

I have a Windows 7 machine that is running Sage Accpac 5.6 and VB6. I have a program which has been working for years in the XP environment and using Accpac 5.3 - 5.5.

I am now encountering an error with the Accpac sign on manager. I have a reference to 'Accpac Signon Manager 1.0' and the following:

'// Sage Accpac objects used by the main form.
Public msiSignonManager As AccpacSignonManager.AccpacSignonMgr
Public msiSESS As AccpacCOMAPI.AccpacSession
Public msiDBLINK As AccpacCOMAPI.AccpacDBLink
Public CSCOMPANY As AccpacCOMAPI.AccpacCompany

Public Function Open_Connections() As Boolean
'// Start the program.
   Dim l_strDSN As String, l_strCompany As String
   Dim l_strUser As String, l_strPWD As String
   
   On Error GoTo ERR_Handler
   
   '// Set the Sage Accpac objects.
   Set msiSignonManager = New AccpacSignonManager.AccpacSignonMgr
   Set msiSESS = New AccpacCOMAPI.AccpacSession
...
End Function

If I press '.' after AccpacSignonManager, I do see the option for the signon manager appear so I know that the reference is working.

When the code is executed, I get the following error:

ActiveX component can't create object

Can anyone help me to identify why I cannot use the sign on manager?

Thanks.

 

[vb5prgrmr]

I don't know a thing about Accpac but as has been the culprit of so may woes, I have to ask... Is UAC enabled? And does your problem go away if it is then disabled?



Good Luck

 

[dilettante]

I forget what they call the mechanism for add-ins providing things like "security token" and biometric sensor logins.

However I do recall that starting with Vista the APIs changed for these items. You'd need Vista/Win7 versions of the "drivers" for these things, and there is no telling what the manufacturers may have changed in the user-APIs for their software.

But this sounds more like some sort of ERP product, so that may be irrelevent.

 

[Bluejay07]

Thank you both for the replies.

I adjusted a few settings, set the compatibility to 'Run As Administrator' and restarted the computer. After all of these steps, the problem seems to be fixed.