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.
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.
RESOLUTION
Frontend Corruption
To clear frontend corruption, reinstall ERPlite from our website onto the client PC's and the server. However, if your frontend has been customized , see the troubleshooting item re custom changes.
Backend Corruption
To clear backend corruption, you must import the corrupt backend into a blank database. Here's how:
0. Tools > Utilities > compact and repair DbM_be.mdb (note Access will suggest renaming the file to db1.mdb. Be sure to name it DbM_be.mdb)
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.
If you have Access 2003 or later, then do the following. Otherwise, go to step 5.
4.1 tools > options > general tab > uncheck "track name", which will also uncheck "performance autocorrect"
5. Click "get external data", then "import".
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.
Test to see if the problems are fixed. If not, email support@erplite.com