Corruption and Cleaning

FAQ ››
Parent Previous Next

PROBLEM



Environmental factors may leave your database file damaged. The symptoms of a corrupted database can range from #Deleted appearing in certain records, to the inability to open one of the objects in the database, to the complete inability to open the file in Access. The Repair and Compact utilities in Microsoft Access are useful tools for recovering and optimizing Microsoft Access database files. This article describes these utilities and offers additional alternatives for repairing damaged databases.



SYMPTOMs



If ERPlite is not behaving the way it used to, then suspect corruption.



BACKGROUND




Corruption is usually caused when the PC is powered down, with ERPlite still running, but can occur for other reasons as well..


Corruption can be in the backend or the frontend. Frontend corruption is 5 times more likely than backend corruption (probably because there are a lot more client PC's that may get turned off or rebooted).



Corruption is easily cleaned with the following protocols. No significant amount of customer data has ever been lost due to corruption (sometimes you have to reenter one data record).




RESOLUTION




FRONTEND CORRUPTION CLEANING


If you are using a regular ERPLite release then: To clear frontend corruption, reinstall ERPlite from our website onto the client PC's and the server.




However, if your frontend has been customized , then compact and repair the front end:


open ERPlite > tools > database utilities > compact and repair


If compact and repair doesn't fix the problem then to clear corruption, you must import the corrupt frontend into a blank database. Here's how:


1. Make a copy of the frontend, and name it DbM_fe_old.mdb.


2. Open Microsoft Access


3. Create a "Blank Database", and save it as db1.mdb.

NB: The frontend file should be maintained as an Access 2003 mdb file to make sure it is compatible with all users copies of Access.


4. Open the Blank Database.


Turn off the "Name AutoCorrect" check boxes ::


For Access 2000- 2003 (for older versions of Access jump to step 5):


4.1 tools > options > general tab > uncheck "track name...", which will also uncheck "Performance Autocorrect"


For Access 2007:


4.2 Office Button > Access Options > Current database > uncheck the Name AutoCorrect check boxes.


5. Access 95-2003 n File menue...Click "get external data", then "import".

Access 2007: choose "External data"> Import > Access


6. Import the corrupt database (i.e DbM_fe_old.mdb)


7. Select all: tables, queries, forms, reports, macros, modules.


8. Select Options, then select: Import Relationships, Menus and Toolbars, Import/Export Specs; Import Tables Definitions and Data; Import Queries as Queries.


Note: this import process is memory intensive, so if it hangs then import the objects one group at a time.


9. Click Ok



10. Rename db1.mdb to DbM_fe.mdb, and paste it into the the \Program Files\ERPlite folder, if it is not already there.




11. Open DbM_fe.mdb.




12. Reset Startup (which opens the Switchboard ): Click Tools > Startup. Then, Display Form > startup. Uncheck Display Database Window. Click OK.


In Access 2007: Microsoft Office Button > Access Options >Current database > display format = startup + don't display Navigation Pane



13. Close ERPlite. Make a copy of ERPlite and test the copy for proper operation.




14. Distribute the corruption cleaned master copy of the ERPlite frontend to all users by copy and paste of the DbM_fe.mdb file.




If the problem still exists, then you need to email our support staff at support@erplite.com




BACKEND CORRUPTION CLEANING


50% of the time a simple compact and repair will clear the corruption...


open ERPlite > tools > database utilities > compact and repair


If compact and repair doesn't fix the problem then to clear corruption, you must import the corrupt backend into a blank database. Here's how:


To clear backend corruption, you must import the corrupt backend into a blank database. Here's how:




1. Make a copy of the backend, and name it DbM_be_old.mdb.




2. Open Microsoft Access




3. Create a "Blank Database", and save it as db1.mdb.




4. Open the Blank Database.


Turn off the "Name AutoCorrect" check boxes ::


For Access 2000- 2003 (for older versions of Access jump to step 5):


4.1 tools > options > general tab > uncheck "track name...", which will also uncheck "Performance Autocorrect"


For Access 2007:


4.2 Office Button > Access Options > Current database > uncheck the Name AutoCorrect check boxes.


5. Access 95-2003 n File menue...Click "get external data", then "import".

Access 2007: choose "External data"> Import > Access


6. Import the corrupt database (i.e DbM_be_old)


7. Select all: tables, queries, forms, reports, modules, macros.


8. Click Ok


9. Rename db1.mdb to DbM_be.mdb, and paste it into the backend folder.




If the problem still exists, then you need to email our support staff at support@erplite.com

Created with the Personal Edition of HelpNDoc: Write eBooks for the Kindle