Lisa, thank you for biting :)

We all remember the messageboxes that warn us that something will gonna be converted, for example old-style 2.6 frx's. I hope that the vfp-team still uses that mechanism in any case where such irreversible conversions will take place, not only for frx's, but also for vcx's, scx's and so on. And moreover, that they mention such cases in the What's New section. If such conversions are none, then I would appreciate it if that fact is mentioned in What's New.

Agree?


>>> to invoke the reaction of the community
>
>OK Peter, I didn't "bite" before but now I will...
>
>In your "reaction" to me you said:
>
>>> I now presume that first running my code in vfp9 and then again in vfp7 or vfp8 will be fine.
>
>As a test, yes that is a good idea to test this thoroughly. And for the most part tests will bear out your presumption.
>
>There are probably limitations (somewhere). If by "running your code" you mean "running code that may modify the SCXs/FRXs on the fly", such as developer tools, you might run into some issues. I can't think of any -- even what the ReportBuilder adds to the FRX contents in various fields shouldn't render the FRX invalid in 7 or 8 -- but there certainly *might* be some.
>
>Here's a possibility:
>
>If by "running your code" you include running some developers' tools that allow you to modify, say values and descriptions in the property sheet of a class, and if you add more information in there than 7 or 8 can handle while modifying this class as part of "running your code", there is a good chance that 7 or 8 won't like the class any more!
>
>You ask:
>
>----
>Actually, a list of possible changes and an advice should be a crucial part of each help text ("What's New in ...").
>-----
>
>I think that the above information is available already, in the sense that you will get the information about extended property descriptions now being possible. IMHO, the idea that such extended property descriptions might not be handled properly in previous versions is only common sense, and hardly "crucial" to list in each help topic. It is even a stretch for me to call it a limitation (I had to think hard to think of one <g>).
>
>NB: I have no idea if "what's new" lists this improvement (extended property descriptions, memberdata and so on) right now, but it is an enhancement and would be so listed as such in the final help. It may be listed somewhere separately in your release notes.
>
>>L<