From: Tony T. <to...@gr...> - 2005-02-03 05:10:08
|
At 12:39 PM 02-03-2005 +1000, you wrote: >I've experienced issues myself with corrupt db's returning errors - >loading them up into to Access and repairing them seems to fix most >cases. FWIW the only real way to ensure Access MDBs are free from corruption is to also import them into a new MDB. Just repairing isn't always sufficient as minor corruptions can still exist and thus grow in major corruptions. This is according to Peter Miller of PK Solutions who retrieves data from corrupt MDBs. >Based on the Page Usage Maps section of the HACKING document, >there is a theoretical limit of about 1GB for Jet3 and 2GB for >Jet4. I have not worked with any files of that size, so I do >not have any first-hand experience. This is correct. There's a misleading error that occurs once the MDB gets too large. I forget the exact text though. Tony ----- Tony Toews, Microsoft Access MVP Microsoft Access Links, Hints, Tips & Accounting Systems at http://www.granite.ab.ca/accsmstr.htm |