|
We are using the Xtreme Calendar version 15.3.1 in MSAccess 2007. We compile a version of the access database in Windows XP on Access 2007 on a 32 bit virtual machine in our development environment. This is working correctly on a windows vista 32 bit machine at one of our clients locations. It is not working however at another clients location. They are using Windows Server 2008 on a terminal server setup with a 64 bit machine. We have loaded the Codejock.Calendar.x64.v15.3.1.ocx file in their system32 directory and MSAccess is finding this reference correctly. There are no broken references in the MS Access setup.
When we try and open the calendar form we get the following error. "ActiveX component can't create object [CODE: 429]
Below is a copy of the code that is causing the error.
Public g_DataResourcesMan As CalendarResourcesManager
Private Sub SetShuffleBoard_Scenario() On Error GoTo Err_Procedure
If Not g_DataResourcesMan Is Nothing Then If Not g_DataResourcesMan.DataProvider(0) Is Nothing Then g_DataResourcesMan.RemoveDataProvider (0) Set g_DataResourcesMan = Nothing End If End If
-- ERROR OCCURS WHEN THE FOLLOWING LINE IS CALLED Set g_DataResourcesMan = New CalendarResourcesManager strCalDBName_Scenario = "Kassidee_calShuffleBoard_Scenario.mdb" strConnectionDB_Scenario = CurrentProject.Path & "\" & strCalDBName_Scenario strConnectionString_Scenario = "Provider=Microsoft.Jet.OLEDB.4.0;Data Source='" & strConnectionDB_Scenario & "';" If Dir(strConnectionDB_Scenario) <> "" Then Kill strConnectionDB_Scenario DoEvents Dim pData As CalendarDataProvider Dim bResult As Boolean bResult = g_DataResourcesMan.AddDataProvider( _ strConnectionString_Scenario, xtpCalendarDPF_CreateIfNotExists + _ xtpCalendarDPF_SaveOnDestroy + xtpCalendarDPF_CloseOnDestroy) Set pData = g_DataResourcesMan.DataProvider(0)
If Not bResult Then Exit Sub End If
The line Set g_DataResourcesMan = New CalendarResourcesManager is causing the error but is working correctly in the 32 bit environment on vista with the Codejock.Calendar.v15.3.1.ocx file.
Is this a license problem? Would the problem be resolved by compiling the MS Access database in a 64bit environment before releasing it?
Thanks Kym
|