>VFP 3.0 doesn't include report writer in its distubution runtime, so I can't let user to design their reports by themself. For a alternative, we write a OCX to simulate foxpro build-in report writer, then save user designed form to the *.FRX file. We have learned the structure of *.frx from filespec.dbf included within foxpro. But now, after finish the ocx we found the *.frx generated by our program can't be executed correctly by VFP, foxpro will hang up occassionally while producing reports.
>
>Does anybody got any idea about this situation? or anybody have some experiment similiar to mine? Guys in Q.A. department drive me crazy!!!
>
>Thanks a lot!!!!

Jack

I am not sure about the FRX file (except maybe Tag & Tag2) but in the DBC they use some binary encoding in the memo fields. I have fooled with the DBC Memos & know that for a fact. Tag & Tag2 'may' be possible to leave them empty -- in fact it may be best.

Thats all I know except 'Your a braver man then I Gunga Din!'

HTH,
Tom