>I have migrated from VFP5 to VFP6 SP4. Does anybody know of any other commands in VFP6 that will cause the Fatal Error: Exception code=C0000005, error? I have migrated from VFP5 to VFP6 SP4 a month ago and have experienced this problem with my application. This application ran very smoothly in VFP5. This problem crops up everytime I open a form with one form opened previously. When the aforementioned forms are opened one at a time there is no problem. The form objects are loaded to an array variable in order to insure that only one instrance of a certain form is loaded at any given time. Any help is appreciated. Thanks.
>

There are lots of things that generate this error message - it's an OS-generated message, not a VFP message, that indicates that an illegal memory reference was made by an app. There's no single cure; you need to track down the code that's at fault. There's a good summary of this error and some causes and cures on fox.wikis.com

>
>Hello Erik
>I have seen that error before. You might want to check your MODIFY WINDOW SCREEN command.
>Do you have an Icon file attached to the Title bar? If you do, that Icon could infact cause the error if you have more than 16 million colors in it. It would also conflict with some Windows 2000 machines.
>Those are just a few possible reasons for the C5 error.