Order Manager
Version 8
Order Manager
Version 8
Contents of this Topic: Show
As the Microsoft Access program file of Monsoon Order Manager is used, it may become necessary to re-compile the program file to avoid problems running the application. This process can be accomplished manually through the MS Access database utilities, or, Monsoon Commerce has provided a standalone utility called the OM Compiler, which allows the user to easily re-compile the application's program file.
If you’re experiencing frequent MS Access crashes while running Monsoon Order Manager or getting error messages such as ”Runtime Error: 3265 Item not found in this collection” or ”Runtime Error= 13 Type Mismatch”, try running the OM Compiler, which may resolve the situation. If not, contact Monsoon Order Manager Tech Support for further assistance.
The OM Compiler is a utility that re-compiles, and compacts and repairs the Monsoon Order Manager program file, SEOrderManager.mdb
This utility is located in your Monsoon Order Manager program installation folder and is run automatically during the installation of the program. This process does not affect, nor it is appropriate for, the store data file.
Close Monsoon Order Manager on the computer that is experiencing the problems.
The OM Compiler can executed by double-clicking the file,OM Compiler.mdb, found in the program installation folder. The default installation location is c:\Monsoon Order Manager, but select Info on the Main Menu, or press CTRL+Shift+C to verify the path to the location of the program file.
When the screen opens, select Compile. The file named at the bottom of the screen is the file that will be re-compiled.
The message ”Compacting data file, please wait" eventually appears in the lower left-hand section of the screen. This message is referring to the Monsoon Order Manager program file, not the store data file.
Note1: If you receive a message saying that "Monsoon Order Manager appears to be running" and it is not, close OM Compiler, go to the folder where the program file resides and look for a lock file with the same name as the program file (SEOrderManager.ldb; this is not a typographical error, it is the extension that denotes that it is a lock file, and it is 1KB in size). Lock files are often left behind when an Access program ends abnormally. Delete this file and then re-open the OM compiler utility and repeat steps 2-6.
Note2: If the program file noted at the bottom of the window is not the correct program file, select Exit and follow the directions in the next section for manually re-compiling the program file and the directions in article Compact and Repair database to manually compact the program file. This situation can occur when multiple versions of Monsoon Order Manager are installed in the same folder (if program is not un-installed before upgrading).
When the process is complete, the Done! message box pops up. Select OK and Exit to close the utility.
Launch Monsoon Order Manager normally.
Close the Monsoon Order Manager program.
Press and hold down the Shift key while double-clicking the Monsoon Order Manager shortcut on the desktop to open the database window.
Press Ctrl+G to open a Visual Basic window.
From the MS Visual Basic menu, select Debug > Compile SEOM.
If Compile SEOM is grayed-out, take the following actions to force a re-compile of the program. Otherwise, skip to Step 6:
Go to Tools > References.
Select the first unchecked, check box (make a note of the label of box that you select).
Select OK.
Go to Debug and select Compile SEOM from the drop-down list.
Go to Tools > References.
Clear the check box you selected previously.
Select OK.
Go to Debug and select Compile SEOM from the drop-down list.
When the program file has been re-compiled successfully, close the Visual Basic window, close the Microsoft Access window and re-start Monsoon Order Manager normally.
Created: 1/26/11
Revised: 9/18/14
Published: 08/19/15