Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
One useful behaviour unsupported
Message
 
 
To
22/10/2004 12:47:42
General information
Forum:
Visual FoxPro
Category:
Visual FoxPro Beta
Miscellaneous
Thread ID:
00953256
Message ID:
00953914
Views:
16
Yes eventually you will find issues in the revisions to the VFP Report System, I have no doubt, Fabio .

I will of course be sorry to hear about them *after* the beta period, since there will be nothing I can do to help get them fixed at that point.

As far as availability goes... I don't know if I'll be "here" or not. But, if I am around, and if I see your messages, I will do my best to explain and discuss anything that interests you.

As a final thought for the subject under discussion in this thread, the following "mixed" strategy occurred to me after I wrote last time:

1. Create an access method for _memberdata in your baseclasses

2. Have it create an empty root XML document, or append into the existing XML document contents if it exists, and read the necessary values out of your methods (containing the #IF + TEXT information tagged appropriately) using GETPEM(), appending these nodes into the memberdata document dynamically.

3. No performance penalty since if you don't use _memberdata the access method won't get called. And you have the memberdata for each method in-situ, I mean within the method, which you and I both prefer.

It also occurred to me that the COMATTRIB information could be useful to perform some of this service, for properties. Would be a good use of it for non-COM objects, in fact. I haven't done this but it should work.

Regards,

>L<
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform