Teessider66 Posted November 19, 2006 Report Share Posted November 19, 2006 I have scheduled a macro to run each at at 06:00. The sole purpose is to open an Access database, which updates some tables and then shuts itself down. The macro simply opens the database. It runs fine, dead on 06:00, but then opens the database again about 5 seconds later, and I get an error #29. Why is it running twice and why the error? I am using 3.5.5.1, 3.5e Build 1 Quote Link to comment Share on other sites More sharing options...
rolf Posted November 19, 2006 Report Share Posted November 19, 2006 I don't have an answer off hand, but throw your code up here and maybe we'll spot something. Also is this macro running on an XP or NT box? Assuming here not '98 or SE. Quote Link to comment Share on other sites More sharing options...
Teessider66 Posted November 19, 2006 Author Report Share Posted November 19, 2006 Is this what you mean? Macro code .... <LAUNCHDEL2:0:00C:\db1.mdb> MS Access Code .... DoCmd.SetWarnings False DoCmd.RunSQL ("INSERT INTO Table1 ( Events ) SELECT Now() AS Expr1;") DoCmd.Quit This is just to test the repeated triggering of an Access database. I'm on XP SP2, MS Access 2000 Quote Link to comment Share on other sites More sharing options...
rolf Posted November 20, 2006 Report Share Posted November 20, 2006 Looks good, nothing jumps out at me. Since this is a pretty simple macro, maybe you should just delete it and create a new one? The only modification I suggest, just for kicks, is to build in some delay - say five seconds. Grasping here but maybe Access is sending back an odd event code. Macro code ....<LAUNCHDEL2:0:00C:\db1.mdb> Here is a 5 second delay - <LAUNCHDEL2:0:5C:\db1.mdb> Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.