Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
C0005 Bug in VFP8???
Message
From
06/02/2003 16:55:48
 
 
To
06/02/2003 16:33:18
Ted Cooper
Cooper Consultants & Systems
Dayton, Ohio, United States
General information
Forum:
Visual FoxPro
Category:
Other
Miscellaneous
Thread ID:
00750117
Message ID:
00750256
Views:
24
Hi Ted,

Actually, C5s are unhandled exceptions and can be caused be a variety of situations...if the code, for example, expects a certain cast or value at a certain point it might C5.

As to your report preview C5, I can tell you that this specific issue was resolved...does not occur in VFP8.


>Let me confess I am jumping into the middle of this :}
>
>I have seen a number of C005's - under strange circumstances.
>
>C005 is a result of an invalid memory reference -
>1) you don't have access rights
>2) it's nolonger in your address space
>
>The typical cause of one of these is a reference to something through a pointer after what is being pointed at is now invalid. Someone releases a resource but doesn't cleanup, someone clobbers the datastructure for the resource, someone saves a pointer and doesn't notice that resource is gone!.
>
>I have gotten them in apps generated using the application framework in 7.0 if you use reports with preview in a form and with the form open but not the current form you close the app after having generated a report.
>
>I hope this helps some - I really don't have a smoking gun here only a severe headache.
>
>Ted
------------------------------------------------
John Koziol, ex-MVP, ex-MS, ex-FoxTeam. Just call me "X"
"When the going gets weird, the weird turn pro" - Hunter Thompson (Gonzo) RIP 2/19/05
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform