Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

cinfo.mdb

Status
Not open for further replies.

acr1

Programmer
Oct 12, 2001
73
NZ
Team
I have read all the threads here regarding cinfo.mdb. My question is that our copy of this has blown to over a gigabyte. We are using SI Vs7.0.

My questions are:...

1. Can we compact with MSAccess97.
2. Should we repair/compact..??
3. What causes the 'bloat' in the cinfo.mdb...???
4. and is their an optimium file size..??

A test compact went to 1400kb.

TIA
Angus
 
Your cinfo.mdb is over 1GB?! I'm surprised your system even runs. To answer your questions:[ol][li]Yes, you can compact cinfo.mdb.[/li][li]Yes, repair/compact on a regular basis. Remember to shut down your APS first and back up your cinfo.mdb prior to attempting the repair/compact.[/li][li]MS Access doesn't free up space when records are deleted. Records can be deleted, for example, when instances are deleted from Info.[/li][li]I believe the optimum file size is between 20 and 30Mb, according to Crystal Decisions. My old Info system worked fine up to 100Mb, but I always compacted it monthly to be safe. If your environment is so large that its still over 1GB (1400KB) then you should definitely migrate your Info database to a SQL Database (Oracle, SQL Server, etc...).[/li][/ol]
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top