Is this happening on every windows xp machine you run the app on? Can you recreate this on any xp machine? I am sure that this is not xp - I have a lot of clients running all flavors of fp on xp, with no problems.

You need to attack this problem from a different angle - work with the client and find out if they have another machine with xp - if so, try to get them to run it on the other machine. If they experience the same problem, find out what other applications are similar between the two machines. Maybe virus software, etc. If they are in a network environment, find out about any limitations that they have on their accounts from the administrators of the network.

If they don't experience the same problem, then it is probably a problem with hardware of some sort. Have them test the memory and see if there is anything wrong. I had a problem with a RAM stick a few months ago - I wrote about it in next months UT Magazine. There is an analyzer for RAM for MS - http://oca.microsoft.com/en/windiag.asp

hth


>Wayne, that piece of code don't seem to be the problem.
>I took out that code and ran the program and it came up
>to the main menu as normal.
>
>I could even use the menu and other dialogs etc.
>However, once I quit the program, the C5 error occured
>and the same error message about not being able to write
>to memory.
>
>Is there some part of memory that the program can't write to
>in Windows xp ?
>Should I set limits on the memory it uses and if so
>what would you recommend.
>
>Is there a command to force the program to write to memory or
>flush it's memory ?
>
>Loren