1. Home
  2. Program Maintenance
  3. Improving the Performance of Stone Edge

Improving the Performance of Stone Edge

Overview

This topic provides suggestions and possible causes for the SEOM to experience degraded performance. Some of the tips are software release-dependent or specific and may not apply to your environment.

Improving the Performance of Stone Edge

  1. Refer to System Requirements to ensure that the processor speed and RAM requirements of all servers and workstations are being met.
  2. Move the SEOM data file to a dedicated server rather than using a host PC that is busy performing other tasks.
    1. If possible, use a server with a solid-state drive (SSD) to house SEOM‘s data file.
  3. Do NOT use ZoneAlarm Personal Firewall software.
  4. Check the settings of the anti-virus software installed on each workstation to see if it is possible to exclude MS Access from the list of programs and/or files it scans as they are opened and closed.
    1. Stone Edge Technologies Inc. suggests using the Microsoft Security Essentials software.
  5. Use a gigabit ethernet network (LAN or WAN).
    1. All network components must be capable of processing at that speed, or the user will not reap the benefits of increased performance.
    2. Ensure that the ethernet cables, routers, hubs, and NICs (network interface cards) that are being used support gigabit speeds. A High-speed ethernet cable is preferred.
  6. Compact an Access data file weekly after creating a backup copy.
  7. Run OM Compiler regularly on each workstation.
  8. Change the DefaultOrderView parameter (in the Program group) to All.
  9.  Archive old data to reduce the size. Click HERE for more information.
  10. Add indexes to frequently searched fields (refer to Microsoft’s documentation for adding indexes to an Access or SQL Server database. Always make a backup copy of the database before adding or re-building indexes.
  11. If using a Shared or Local Stack, check the stack viewer (Ctrl+Shift+S key combination at the Main Menu) to ensure that records are not “stuck” there.
    1. Sometimes, a record can fail to be sent, and the program will exceed the limit of retries, but the program will never remove the failed record from the queue. All other records behind it in the stack remain in the stack queue, which continues to grow as new orders are processed, causing the program to slow down.
    2. Manually delete the “stuck” record from the stack queue.
  12. Check Parameter UseGenericStatusUpdates
    1. When set to TRUE as a system wide parameter rather than in the cart-based parameter, the program to create status update records for every shopping cart in the current data file – whether or not the shopping cart requires that setting to send status updates. Any status records going to shopping carts that do not require UseGenericStatusUpdates=TRUE will fail, clogging the stack.
    2. Review each shopping cart to determine if it requires UseGenericStatusUpdates=TRUE and if so, set it in the Program group of the cart-based parameters. Leave the UseGenericStatusUpdates parameter in the main parameters set to FALSE, unless only one shopping cart is defined in the data file. It is one of the types that require it to be set TRUE.
  13. Check if Send Updates to the Order Status System is enabled.
    1. The Order Status System (OSS) subscription is an add-on to the SEOM program; inquires can be sent to sales@stoneedge.com
    2. If not subscribed to the OSS, the stack will become clogged with records that cannot be delivered. This setting can be found on Page 1 of the Order Status System section of the Setup Wizard.
  14. If only one shopping cart is defined in the current data file, and it does not support receiving status events at all, make sure there are no Status Events that have the Notify Cart box selected.
    1. Verify the status events settings by going to Main Menu > Settings > System Functions > Status Events.
  15. Stay current with Microsoft Service Packs and recommended hotfixes for Access and the operating system, as well. Make sure that they are being applied as well as downloaded to your PCs.
  16. As a last resort, try uninstalling the current version of SEOM and reinstalling it if the user has retained the installer for the currently installed version of SEOM.
    1. Email support@stoneedge.com for link to the download gateway and credentials if needed.

Note: Back up the SEOM data files, including email templates and custom reports, before uninstalling and reinstalling the program. Make sure all custom reports, forms, or queries are stored in the Custom Reports database. Use the key combination of Ctrl+Shift+C at the main menu to determine the location of files used by the program.

Upgrade to a SQL Database

The Standard Edition of SEOM uses Microsoft Access as the back-end database to store your orders, customer, inventory, etc. The maximum database capacity for an Access .mdb file is 2GB (Gigabytes). However, based on how MS Access works in a server/client environment, the realistic, usable size for a SEOM data file is around 500MB-800MB. The reason for this is that whenever a client workstation requests the server housing the data file, the program must move the entire file to the client machine to service the request (i.e., copying an 800-megabyte file from one PC to another). This is a feature of MS Access and cannot be modified. Therefore, as your data file grows, it will take longer and longer to serve the client requests.

For clients who run stores that handle large volumes and do not wish to move to the “Enterprise” Edition of SEOM, many have made the change to Gigabit Ethernet (1000BaseT). They have found that this dramatically increases network performance and SEOM response times. For example, compare it to emptying a swimming pool through a cocktail straw (10baseT), then a drinking straw (100BaseT), and then a fire hose (1000BaseT). The more bandwidth that is available, the faster files can be moved.

  • Click HERE for steps to convert and existing Access database to a SQL database.
  • Contact support@stoneedge.com if you are interested in moving to a SQL database and need help.
Updated on March 2, 2026

Was this article helpful?

Related Articles