Hum, I am not aware of one.
For the most part, things should work as if you were not using a server
based system.
A few tips
For all tables, include a timestamp field. ms-access will use this to
detect when data changes. This especially helps for sub-forms.
For all tables, include a primary key. Again, this helps for updates.
Ask the user what they need before you load a form!
The above is so simple, but so often I see the above concept ignored.
For example, when you walk up to a instant teller machine, does it
download every account number and THEN ASK YOU what you want to do? In
access, it is downright silly to open up form attached to a table WITHOUT
FIRST asking the user what they want! So, if it is a customer invoice, get
the invoice number, and then load up the form with the ONE record (how can
one record be slow!). When done editing the record...the form is closed, and
you are back to the prompt ready to do battle with the next customer. You
can read up on how this "flow" of a good user interface works here (and this
applies to both JET, or sql server applications):
http://www.members.shaw.ca/AlbertKallal/Search/index.html
So, use caution in how many records you load to a form....
