John Skolits
askolits at ot.com
Thu Jun 5 22:20:01 CDT 2003
Thanks Charlotte. I figured it out. It was the MDAC that fixed it. Thanks, John -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com]On Behalf Of Charlotte Foust Sent: Thursday, June 05, 2003 1:25 PM To: accessd at databaseadvisors.com Subject: RE: [AccessD] ADO function problem. Set Cnn=CurrentProject.connectionFails? Someone reported the same problem in Woody's Lounge (www.wopr.com) and I don't recall that we ever found the reason for it. I couldn't recreate it on my machines. Do you have all the Jet service packs as well as O2k service releases installed? Charlotte Foust -----Original Message----- From: John Skolits [mailto:askolits at ot.com] Sent: Thursday, June 05, 2003 9:13 AM To: accessd at databaseadvisors.com Subject: [AccessD] ADO function problem. Set Cnn=CurrentProject.connection Fails? I am having a strange problem on one PC. Application is (A2k) running in Access XP. The following line of code gives me a strange error, indicating a problem with the DLL. Set cnn = CurrentProject.connection It says Run-Time error -2147220999 (800401f9) Automation Error Error in the DLL I replaced the DLL from a PC that the application is working but same issue. Application compiles without a problem. Anyone know what this is. _______________________________________________ AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com _______________________________________________ AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com