>Dmitry,
>
>The error log may be helpful but I doubt it. C5 error is essentially Windows telling VFP that it is hosed. It usually is a result of some program overwriting the memory space of another program. The most common culprits are the video and pritner drivers smashing VFPs memory. C5 is NOT a VFP error it is not a result of your code and there is very littel you can do in your code to deal with it. It is some other program or driver messing with VFPs memory space and the soultion is invariably to find out what the other app or driver is and to replace it with something that doesn't violate the memory for other apps.
>
Agreed. I know I used to get C5s when running VFP at the same time as WinFax. It wasn't the most elegant workaround but temporarily exiting WinFax always got VFP working again.
Previous
Reply
View the map of this thread
View the map of this thread starting from this message only
View all messages of this thread
View all messages of this thread starting from this message only