Runtime Access 1

[Ed2020]

Hi,

I have been asked to put together a list of conditions that a system must satisfy before it can be used in Runtime Access.

So far I have:

1. The system must have a fully-developed GUI; users must not have any requirement to access the database window.
2. All code should handle exceptions gracefully. Unhandled exceptions cause Runtime Access to crash.
3. Because of point two automation should be provided by VBA and not through macros (macros do not provide the facility for exception handling). An AutoExec and AutoKeys macro may still be used.
4. Filter By Form, Filter By Selection, and Advanced Filter do not work under Runtime Access so an alternative method of searching/filtering data must be provided.

Can anyone else think of anything else worth adding?

Many thanks,

Ed Metcalfe.


Please do not feed the trolls.....

 

[jrbarnett]

In the runtime version of Access, it isn't possible to open an object in design view, regardless of database security settings. With some limitation, changes to objects (forms, reports, commandbars etc) can be made through code but not saved.

John

 

[Ed2020]

Thanks John.

Please do not feed the trolls.....

 

[jrbarnett]

Another quickie:

If there is no autoexec macro, there must be a form designated as the startup form, otherwise there will be no means for the user interface to run at database startup.

John

 

[Ed2020]

Aha, good point!

I've actually found it surprisingly difficult to come up with a definitive list.

Ed Metcalfe.

Please do not feed the trolls.....

 

[jrbarnett]

I seem to recall another item relating to printing reports in preview mode, but can't remember the exact details (its a while since I deployed apps for use in the runtime).

Its something like you have to press Ctrl P to print a report to your printer, shown in preview mode because the default report print preview toolbar has limitations.
The alternative is to set up your own toolbar with a print icon on it and set this as the default toolbar for the report.

This was for Access 2002, not sure what happens with other versions.

John