>>When running the VFP application in Windows 7 on Novell Client 2, Zenworks 7, I am getting a blue screen sometimes when a sql insert statement is trying to execute. Sometimes the computer freezes and you can not even do a ctrl-alt-del. You have to turn the computer off. When the problem occurs, it is always during the insert statement in different forms.
>>
>>Previously, I had the insert in the referential integrity set to restrict for many of the tables in the dbc. Since this problem occurred, I have since changed the insert in the ri to ignore. Even after doing this, we are still getting the blue screen.
>>
>>The same VFP application runs fine in Windows XP.
>>
>>I have reindexed all the tables. I also deleted all the index tags and recreated them for all the tables in the dbc. This problem has just started occurring. Prior to this the application ran fine in windows 7.
>
>A few ideas:
>
>- If you're accessing data tables and index files on a network server or otherwise over the network, try working against a copy of the tables on your local C: drive

Yep -- might be a good idea to to eliminate network as possible culprit. Had problem years ago w/ Novell and WinXP -- took a few versions before all the "quirks" got worked out between XP and Netware. The drivers that came with Windows mostly worked, though none of the Netware management tools worked under it. Drivers downloaded from Novell would get the management tools working, but had weird crashses or strange behavior. Took a few revisions before there ws one that worked for me 100%.

>
>- Temporarily disable any real-time antivirus scanning on your local computer
>
>- Create a bootable CD or USB stick and test your RAM memory with MemTest86+: http://www.memtest.org/

Yep, was stung by this one before. Had bad RAM. Thought it was rather suspicious that frequently when booting it would have to do an integrity test. Had the system completely crash -- to the point where something the registry was so badly damaged Windows would not boot. After the second time I'd reinstalled Windows, I decided it was time to run a RAM test. One failure after another during the more extensive tests. Replaced the memory modules and "magically" all the problems disappeared.

>- Make sure your hardware drivers are up-to-date and exactly correct for your hardware, especially video adapter. Printer drivers are also sometimes problematic but if you're hitting the problem on a SQL command I don't believe that would be your issue

One other thing too -- on occasion you could get away with running drivers for the previous version of Windows. Sometimes it worked, other times it wouldn't.
The other thing that gets a bit fiddly is if your system is 64-bit. Sometimes you'll discover that the driver disc doesn't have a 64-bit driver, and running the install will try to install the 32-bit drivers (which will NOT work). This is especially the case if the hardware is relatively old.