>Hello;
>
>My VFP5 application running on WinXP gets:
>
>"my_app.exe has generated errors and will be closed by windows".
>
>This happens on SOME computers. On those computers, it happens randomly in different places in the application, it happens often, and it generates the Dr. Watson report and sends it to Microsoft.
>
>I have asked customers to update their WinXP with SP1, but the problem still continues.
>
>1) Is there a FIX for this ? if so, exactly which WinXP patch needs to be applied ?
>
>2) Otherwise, How can I get Mirosoft to respond to the Dr. Watson report ? I need to find out WHY WinXP is closing vfp5.
>
>This is KILLING me guys!!. please H E L P !!
>
>Cyrus

Cyrus;

In my applications I capture and log errors to a table which defines as much as possible.

My brother is using XP and for the last year all was well. He just installed a HP 1200 series printer and it worked – for a few days. Now when he boots the mouse or keyboard will not work. Either one or the other will not work. If he pulls the printer cable from the computer both mouse and keyboard work fine.

I am getting the impression XP is a lot of “fun”.

George has given you some great ideas for a logical way to approach this problem. Let me add you should be sure anything installed (hardware and software) on a XP machine must be compatible. Using an older piece of hardware on an XP machine for example does not guarantee it will work.

As a last resort I would suspect VFP 5. It is an older piece of software and God only knows how compatible it is with any number of XP machines.

I remember George Goley saying years ago, “One computer in 500 will not run with FoxPro no matter what you do”! In reality I think you can solve the problem but you must logically eliminate the variables.

Be a third person and write down an outline of your plan of action. Define the machines if possible, and as much detail as you can. Then just go down your checklist.

1. Which video cards/drivers are installed on working machines vs those that have a problem?
2. Printer drivers
3. CPU
4. BIOS and level
5. Version of I.E. and what service pack is installed. (I kid you not!)
6. Motherboard

Prioritize your list and be methodic. You will win!

Tom