>This posting is an addition to my previous posting (Thread 1339927).
>
>We have been running SBT PRO series 5.0i on our network for a long time, have made a lot of changes and are not planning to replace it with a newer version.
>It works fine for us, but we seem to be having crashes in one module SBT - Account Receivable (Creating and editing of Invoices).
>This part works fine on most days but once or twice a week SBT crushes (one user, one person, she edits the most invoices).
>
>It’s not a FoxPro error, it’s a system crush. No errors appear on the window the program just closes.
>The only information about this I can find is in the System Log. The following is listed:
>
>Faulting application sbtw.exe, version 0.0.0.0 faulting module ntdll.dll,
>version 5.1.2600.5512, fault address 0x000109f9.
>
>I tried to duplicate this error on my development environment, but it happens unexpectedly and does not give me any additional information.
>The computer have been replaced twice and has a pretty basic configuration similar to all other users computers.
>All service packs were installed and both the ntdll.dll and vfp500.dll are up to date.

Typically VFP5 runtime files are installed to C:\Windows\System32

Can you confirm that the version for both VFP500.DLL and VFP5ENU.DLL is 5.0.0.415? Might there be older versions elsewhere on the system?

If antivirus is deployed can you exclude VFP file types and folders (including temp file folders)?

How thorough is the setup of your new computers? Has anyone checked for, and applied if available:

- Motherboard BIOS update
- Motherboard driver updates e.g. chipset, IDE/SATA etc,
- Up-to-date reference driver for the exact display adapter in the system e.g. nVidia, ATI, Intel?
- Many offices these days use so-called "all-in-one" (AIO) printers. These often have immense, buggy printer drivers/print monitors etc. If you're using such a printer be sure to download and install the latest drivers from the manufacturer's site. Don't use the CD that came with the printer - these days that's typically version 0.99 software, barely out of beta

Are you saying that you can reproduce the problem on your dev machine, or have you never seen it there?

What is different between the user seeing the problems, and everyone else? Different computer? Does she use different parts of SBT?

If the problem machine has lots of add-on hardware like webcam, scanner etc. can it be simplified temporarily for test purposes?

This is a long shot, but googling the fault address you gave led me to a thread, where one user said they fixed their problem by uninstalling OmniPage. If the user has OmniPage installed (either for an attached scanner or as part of an AIO software installation package) it might be worth trying uninstalling that.