Any issues with Access Runtime?

[discodave101]

Currently i work for a company for whom i design access databases, yet they purchase the full access licences for all users. Realistically only runtime is needed as users only alter the data, so I have recommended we purchase a developer license and roll out runtime to save on cost. Are there any issues using runtime that I need be aware of? I remember a colleague at an old place of work telling me once that some kind of coding can conflict with runtime but be ok in the full version.

Any help would be much appreciated.

Thanks,
Dave

 

[jfischer]

Runtime works fine for 99% of what you need. The main problem I run into is differences in menus and toolbars.

1) Most of the functionality is present, but the stock toolbars that you use in the full version of Access are missing in the Runtime version. A toolbar I always have to come up with for Runtime is PrintPreview.

2) The Shortcut (right-click) menus in the full version of Access don't exist in run-time. You have to code your own.

3) Some keystrokes are disabled.

4) You should write your own application help file.

You can read more about the differences in this MSDN article at Microsoft's Web site:

http://msdn.microsoft.com/library/d.../detskDevelopingAccessRuntimeApplications.asp