By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
446,327 Members | 1,789 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 446,327 IT Pros & Developers. It's quick & easy.

Runtime Code

P: n/a
DD
Can someone advise if there is code that i should avoid when writing a
database that will be packaged using Runtime.
thanks in advance
dd
Nov 12 '05 #1
Share this Question
Share on Google+
2 Replies


P: n/a
Hi David

It's not difficult, but some of the issues are:

1. Don't use macros. If anything goes wrong, your application will close
(which to the user looks like a crash) because macros have no error
handling. Use error handling in every routine. If you need to use a macro,
it should contain only the RunCode action, which passes control to a
procedure that does have error handling.

2. Don't try to open forms/reports in design view. That also means Filter By
Form is not available. Using an MDE catches this anyway.

3. If you code for different printers, PrtMip etc won't help.

4. Use fonts that will be on the target system such as Arial and MS Sans
Serif. Although it is possible to specify fonts in the installation package,
doing so confuses users if the font is already on the target system (e.g.
when they re-install).

5. If you split (shared back end, local front end), be sure to included code
that verifies the data file on start up. You may choose NOT to install the
data file by default (i.e. user has to copy it to desired location) so that
a) it does not get installed multiple times for different users, and b) it
does not get overwritten in a re-install.

--
Allen Browne - Microsoft MVP. Perth, Western Australia.
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.

"DD" <da**********@bigpond.com.au> wrote in message
news:14**************************@posting.google.c om...
Can someone advise if there is code that i should avoid when writing a
database that will be packaged using Runtime.
thanks in advance
dd

Nov 12 '05 #2

P: n/a
Allen Browne wrote:

5. If you split (shared back end, local front end), be sure to included code
that verifies the data file on start up. You may choose NOT to install the
data file by default (i.e. user has to copy it to desired location) so that
a) it does not get installed multiple times for different users, and b) it
does not get overwritten in a re-install.


One thing to consider is a separate install just for the tables rather
than having the tables and/or code as an option as in most cases the
installation will be mutually exclusive.
Nov 12 '05 #3

This discussion thread is closed

Replies have been disabled for this discussion.