SYMPTOMs
If ERPlite is not behaving the way it used to, then suspect corruption. The frontend contains custom changes that you do not want to lose.
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.
RESOLUTION
Frontend Corruption
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 o 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.
4. Open the Blank Database.
For Access 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"
5. Click "get external data", then "import".
6. Import the corrupt database (i.e DbM_fe_old.mdb)
7. Select all: tables, queries, forms, reports, macros.
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. Select all: modules
11. Reset References : Select any Module and click View > Code. Then, click Tools > References.
uncheck "Microsoft ActiveX Data Objects" (if checked)
check " Microsoft DAO 3.6"
check " Microsoft Visual Basic Extensibility 5.3"
check " quickiifx"
If any of the needed references are not visible in the scroll down the list, then use the Browse button to find them.
12. Rename db1.mdb to DbM_fe.mdb, and paste it into the the C:\DbM folder, if it is not already there.
13. Open DbM_fe.mdb.
14. Reset Startup (which opens the Switchboard ): Click Tools > Startup. Then, Display Form > startup. Uncheck Display Database Window. Click OK.
15. Compile Frontend: Select a form or module, and click view > code. Click Debug > Compile.
16. Close ERPlite. Make a copy of ERPlite and test the copy for proper operation.
17. 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 us our support staff at support@erplite.com
Backend Corruption
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.
For Access 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"
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.
If the problem still exists, then you need to email our support staff at support@erplite.com