limitations in the access runtime

[Jesper F]

I want to distribute an app in the office and it's seems
cheaper to use a the runtime rather than installing
access on all computers.

Are there any limitations in using the runtime compared
with using an mde-file?

Also, where the xp developer version was used before it's
now called something like office developer tools.
Since I'm using office xp and not office 2003 do I need
the xp developer or will the off.dev.tools work?

Are there other things in this I should worry about?

Thanks for your help.

 

[Allen Browne]

There are several fairly obvious limitations with the runtime. Particlarly,
any unhandled code error causes the program to shut down, so it looks to the
user as if the software just crashed. Error handling is absolutely
essential, so you will have no macros except those that use RunCode to pass
control to a function that does have error handling.

The Office library is not available in the runtime. So if you used something
like the FileDialog object, that code will need to be replaced with an API
call.

You can test how your application would behave before you actually buying
the Developer edition by starting your application with a shortcut that uses
the /runtime switch.

 

[Jesper F]

That was very helpful. Thanks once again Allen.