Function called via Autoexec fails when using Access 2007 Runtime

[haggis999]

I am making my very first tentative steps to convert my most complex Access 2003 app to run under Access 2007. There are no obvious problems when simply opening my original MDB file in Access 2007 or running it after conversion to an ACCDB file. However, when I try to run the ACCDB file under the Access 2007 Runtime I get a "You can't carry out this action at the present time..." error. This is then followed by the "Execution of this application has stopped due to a runtime error..."




To be more specific, I only get that error when I deliberately hide the back end database and thus invoke code triggered via Autoexec to allow the user to browse for the missing database. This code works fine when running under normal Access 2007 so it appears to be a Runtime issue.


Any suggestions?


David

[alansidman]

Not sure what the issue is, but here is a link on RunTime that may be helpful

http://www.hitechcoach.com/index.php...=article&id=62

[haggis999]

Hi Alan,
Thanks for the link but it didn't tell me much that I hadn't already learned from the usual Microsoft sources.

One thing maybe worth mentioning is that getting the errors quoted in my OP implies that I have no error trapping in my app. In fact, the vast majority of my VBA functions and subroutines do have error trapping, including the code triggered via Autoexec, so I'm not sure which code is actually generating the errors (and there appears to be no way to set breakpoints when using the Runtime).

David

[haggis999]

BTW, I have selected the 'Enable all macros' setting in the Access Trust Center.