General information
Category:
Visual FoxPro Beta
You won't need to do that, Torgny.
I've now verified that this information *belongs* in the field, the compiler does handle nested include files in this manner, on purpose.
So here's what will happen:
* 60FRX.DBF will be updated to include this information. We really didn't realize before, and thanks again for your help pinning this down. It's quite important that we have a full record of the product's usage of every field for every objtype, so that people extending reports know what to expect.
* XML Listener will get rid of this information, same as it gets rid of the compiled method code in Tag2.
* As a result, HTMLListener won't have to deal with the binary characters and your compile should work fine.
Thank you!!
>L<
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