MS Access VB Error: -2147319765 (8002802b)
I'm working with a client who is receiving errors on an Access Database application. When preparing a report, they use a custom form to select a date. When clicking on the date, the following error occurs:
Microsoft Visual Basic
Runtime error '-2147319765 (8002802b)':
Method 'Value' of object '_CustomControl' failed
I do not believe this to be a code issue.
The database works fine on other client computers.
The database application used to work fine on this server until an upgrade to Exchange was made. I had to re-register a dll to get some stored procedures to work and I believe that this will be the case here.
Does anyone know which DLLs should be registered with Access 2003 for VB to run properly? Should I just have the client reinstall Access?
Microsoft Visual Basic
Runtime error '-2147319765 (8002802b)':
Method 'Value' of object '_CustomControl' failed
I do not believe this to be a code issue.
The database works fine on other client computers.
The database application used to work fine on this server until an upgrade to Exchange was made. I had to re-register a dll to get some stored procedures to work and I believe that this will be the case here.
Does anyone know which DLLs should be registered with Access 2003 for VB to run properly? Should I just have the client reinstall Access?
ASKER
Thanks for your response.
Unfortunately, I did not write the application. And I'm also working with the client remotely (300 mi across the state). The Access file pulls data from an MSSQL server to run queries, so I'm not sure how useful this will be offsite.
I can give it a try, but in the meantime, what DLLs does ActiveX like to have on by default? Like I said, this database file runs perfectly on all other client computers. Only since a recent software upgrade on one computer (a server) has this database not worked properly on that one computer. All other machines run fine.
Unfortunately, I did not write the application. And I'm also working with the client remotely (300 mi across the state). The Access file pulls data from an MSSQL server to run queries, so I'm not sure how useful this will be offsite.
I can give it a try, but in the meantime, what DLLs does ActiveX like to have on by default? Like I said, this database file runs perfectly on all other client computers. Only since a recent software upgrade on one computer (a server) has this database not worked properly on that one computer. All other machines run fine.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Found it... the control used to select the date was the 'calendar' module. The server's version of Access was set to use MSACal70.ocx (c:\winnt\system32\msacal7
I changed this to use Calendar Control 9.0 (c:\winnt\system32\mscal.o
To change/register controls through Access, go to Tools -> ActiveX Controls.
I changed this to use Calendar Control 9.0 (c:\winnt\system32\mscal.o
To change/register controls through Access, go to Tools -> ActiveX Controls.
ASKER
The response wasn't much of a solution, but it was a hint. If the expert had asked a followup about the date selector (ie - was this using the calendar control?), that would have solved the issue immediately.
The expert basically repeated what I already stated... but thanks for a taking a few minutes to respond.
The expert basically repeated what I already stated... but thanks for a taking a few minutes to respond.
Personally I feel that I steered you to the correct answer and as such I have atleast partly answered the question.
Cheers, Andrew
Cheers, Andrew
"The response wasn't much of a solution, but it was a hint. If the expert had asked a followup about the date selector (ie - was this using the calendar control?), that would have solved the issue immediately. "
In your question you stated that they used a custom form to select the date, not the ActiveX control. Many developers use forms to do the job of the calendar control due to the way the Calendar Control used to be handled in earlier versions. There was no hint that the developer had used that specific custom control.
Best wishes, Andrew
In your question you stated that they used a custom form to select the date, not the ActiveX control. Many developers use forms to do the job of the calendar control due to the way the Calendar Control used to be handled in earlier versions. There was no hint that the developer had used that specific custom control.
Best wishes, Andrew
Open on your PC and check what references you have and what controls you have on the form / report.
Cheers, Andrew