Hi Al,
you're welcome
As for info on decompiling, here are some links:
'~~~~~~~~~
Here's what I know about Decompiling:
http://www.rogersaccesslibrary.com/DecompilingDatabases.zip
The document is for Access 97, but it is still essentially
correct for Access 2000.
-- --Roger Carlson MS Access MVP
www.rogersaccesslibrary.com
'~~~~~~~~~~
from (e-mail address removed)
* WORKING WITH LARGE PROGRAM DATABASES IN ACCESS 97
from the October 1998 issue of Access/Office/VB Advisor Magazine
http://web.archive.org/web/20030204023622/http://www.databasecreations.com/largedb.htm
'~~~~~~~~~~
Decompile or how to reduce Microsoft Access MDB/MDE size and
decrease start-up times
http://www.granite.ab.ca/access/decompile.htm
Unless there is a symptom I'd suggest no more than every
month or so for a front end under active development.
Tony
--
Tony Toews, Microsoft Access MVP
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
'~~~~~~~~~~
In addition to the other links you've been given, check out
what Michael Kaplan says at the following URL ...
http://www.trigeminal.com/usenet/usenet004.asp?1033
Always make a back up copy of your MDB or ADP before using
the decompile switch. It doesn't happen very often, but I
have personally seen the situation where a class module was
no longer recognised as a class module, but appeared to
Access and VBA be a standard module, after a decompile.
-- Brendan Reynolds
'~~~~~~~~~~
Warm Regards,
Crystal
Microsoft Access MVP 2006
*
Have an awesome day
remote programming and training
strive4peace2006 at yahoo.com
*