Database won't work in Runtime Version

[Mike Collard]

I have created a number databases that work fine with the
full version of MS Access but when colleagues try them
using only the runtime version they get a variety of
errors. In particular ODBC connections fail but with the
latest mdb I included an Autoexec macro that seems to
cause a problem.

Are there particular features and methods that I should or
should not use for the Runtime version?

Thank you

Mike Collard

 

[Jamie]

If I recall correctly macros either won't work with Access runtime or it's
recommended that you only use VBA code. Instead of using an Autoexec macro
try converting it to VBA and then place the code on the onOpen event of your
startup form.

Jamie
www.jamiesoftware.tk

 

[Rick Brandt]

If I recall correctly macros either won't work with Access runtime or it's
recommended that you only use VBA code. Instead of using an Autoexec macro
try converting it to VBA and then place the code on the onOpen event of your
startup form.

Sorry, but you recall incorrectly. While seasoned developers frown on Macro use on
general principle, there is nothing about their use that is affected by the Runtime.

To the OP:
The Runtime removes built-in toolbars and menus and there is some loss of
functionality. There is a help topic that discusses these differences that you
should check out. There is nothing I know of that would specifically cause ODBC
problems.

There are lots of problems that can be caused whenever an app is moved from one PC to
another. Missing references being the most common. So it's possible that your
problems on these other PCs are not related to the Runtime at all.

 

[Mike Collard]

Thanks to Jamie and Rick for the tips

-----Original Message-----


Sorry, but you recall incorrectly. While seasoned

developers frown on Macro use on