Sometimes my Access Program has an ODBC fail, requiring my users to restart the program. Is there a way I can Restart the ODBC connection programmaticely, so my users do not have to restart the program?
Sometimes my Access Program has an ODBC fail, requiring my users to restart the program. Is there a way I can Restart the ODBC connection programmaticely, so my users do not have to restart the program?
Can you provide a little more information about this issue? What kind of error message are they getting? Are they using Windows NT Authentication for the ODBC connection or a hard coded username/password? Are you sure that the data source is available when this error occurs? What kind of data source are you trying to connect to via ODBC?
-Randy Shea
I'm a programmer, but I'm also pro-grammar!
If your issue is resolved, please use Thread Tools to mark your thread as Solved!
PODA (Professional Office Developers Association) | Certifiable | MOS: Access 2003
What kind of error message are they getting?
Error#3146ODBC--call failed. [Oracle][ODBC][Ora]ORA-00001: unique constraint (WMS.PKO_HDP1) violated (#1)
Are they using Windows NT Authentication for the ODBC connection or a hard coded username/password?
Hardcoded
Are you sure that the data source is available when this error occurs?
It should be - it is available than it crashes.
What kind of data source are you trying to connect to via ODBC?
Oracle
Sorry, I have no Oracel experience. I know a few of the other guys do, so one of them might be able to help you with this. I've never had an ODBC call fail with SQL Server unless the target data source was unavailable for some reason.
-Randy Shea
I'm a programmer, but I'm also pro-grammar!
If your issue is resolved, please use Thread Tools to mark your thread as Solved!
PODA (Professional Office Developers Association) | Certifiable | MOS: Access 2003
Posting Permissions
Reply With Quote
