Dennis - converted over to VFP9 with all my applications. Occassionaly I will get a C% error in the report writer for VFP9 - othewise I never get a C5 error. I have never had a C5 error from the client in either 8 or 9. That is over a 3 year period with three large applications with over 42 users.

The report writer in VFP9 to me is rather troublesome. Never have a form and the report writer open at the same time and then close the form. The closing of the form can create a c5 error when you try to close the report writer.


Gaylen


>>><snip>
>>>
>>>>>But It is very frustrating when you are doing a presentation of your award winning application to a client and the C05 goes out like a party finisher, then I sayd to them "it is a windows problem don' t worry" and the client look at me with a face that is a poem.
>>>>
>>>>Yes it is. That is why presentations have to been done on tested equipment and rehearsed in the demo system.
>>>
>>>You mean fake that the application is flawless? <g>
>>
>>I'd say, in a way, YES!
>>By demonstrating an application from start to finish withut incident you *DO* show the prospects that the application does run.
>>
>>Now this doesn't completely make the story true because it is possible that something within the demo environment itself is a necessary component and unknown to the developer. So best case is to do what AlexF said on a 'foreign' system.
>>
>>Are you back, or just poppin in?
>
>Hi Jim,
>
>Back from where? <s>
>
>I'm not as loud as I used to be but I'm still here every day. I'm sooo busy with VFP development. I'm still working with VFP 7 but I'll probably jump to VFP 9 soon because I still have a ?%(%/*/&&?/ C5 error and I hope that getting to VFP 9 will fix it. Based on something I read from Alex F where he said that he had C5 in VFP7 a lot less in VFP8 and none in VFP9 since he began to use it.
>
>So you're up to date on what's going on with me.
>
>Later.