Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion GroupsFormsForms ProgrammingQueriesModules / DAO / VBAReports / PrintingMacrosDatabase DesignSecurityConversionImporting / LinkingSQL Server / ADPMultiuser / NetworkingReplicationSetup / ConfigurationDeveloper ToolkitsActiveX ControlsNew UsersGeneral 1General 2
Access DirectoryToolsTutorialsUser Groups
Related Topics
SQL ServerOther DB ProductsMS OfficeMore Topics ...

MS Access Forum / Database Design / August 2004

Tip: Looking for answers? Try searching our database.

Compact Errors

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Lloyd - 25 Aug 2004 21:35 GMT
I am developing a small Access97 database and attempted to
compact it.  The process failed and I checked out some
websites that recommended that one use the jetcomp utility
from Microsoft.  This seemed to be successful and when I
opened the application there was a MSysCompactError table
with a single -1017 error.  

I then tried to run the Compact feature under Tools,
Database Utilities.  The error table was deleted and the
database seems to function properly.  My questions:

1)  How does one check on the version of Jet that is
running?

2)  Is there a way to know if my database is now "clean"?

3)  How often is it recommended that a database be
compacted?

Thanks,

Lloyd
Allen Browne - 26 Aug 2004 05:21 GMT
Q1. JET version
Locate the JET dll, and you can read the version directly.
For Access 97, the file is msjet35.dll
For Access 2000 and later, the file is msjet40.dll
It is typically in Windows\System32.
When you find it, right-Click and choose Properties.
On the Version tab, you should see something like This:
   3.51.3328.0
   4.0.8618.0

If you want to get the versions programmatically, see:
   http://www.mvps.org/access/api/api0065.htm

Q2. Not corrupt?
If the database repaired, and all tables, indexes, relations, and data are
still present, you are probably okay. It may be a good idea to create a new
(blank) database, and import everything: File | Get External | Import. This
forces Access to recreate everything, and is probably the best easy way to
know that things are okay.

Q3. When to compact
Compacting is useful after modifying objects (forms, reports, tables), or
deleting large amounts of data. During development, my practice is to back
up and compact twice a day, because everything is constantly being changed.
That way if something does go corrupt, we never lose more than half a day's
work.

After the database is developed and objects are not being modified, if the
data is relatively stable, compacting once very few months may be often
enough.

For suggestions on how to avoid corruption, see:
   Preventing Corruption
at:
   http://members.iinet.net.au/~allenbrowne/ser-25.html

Signature

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.

>I am developing a small Access97 database and attempted to
> compact it.  The process failed and I checked out some
[quoted text clipped - 18 lines]
>
> Lloyd
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.