Hi all,
Here the story goes: after downloading VFP9, I use it daily to create
and edit several forms on my current project. I really loved all the IDE
enhancement (even though once I put any properties in the Favorites Tab,
I still don't know how to get them out!). I didn't use any VFP9 specific
feature (such as Report Listener), because I am going to compile it with
VFP8.
Problem begins today when I tried to open a form that was previously
modified and saved with VFP9b. VFP8 refused to open the form and throw
an error message; something like 'invalid value for property lDrawMode'.
Trying to fix the error, I re-opened the form with VFP9b and set the
property value to default. Didn't help. The error still there with
another property in question so I tried to open the form as table. In
the Reserved3 and Properties field of the scxs, I found some suspicious
tags begin with _MemberData and there were more tags that looks like an
XML tag. I deleted those tag, and tried to open the form in VFP8.
Another error occurred; VFP8 said that there are invalid value for
Alignment property in one of the Optiongroup control in the form. I
opened the form as table once more, locate the row that contains the
Optiongroup mentioned, and delete the alignment property ('Alignment =
6'). After that, I manage to open the form successfully in VFP8.
<sigh> Great. Fortunately, I 'only' wasted half an hour fixing that (but
I haven't count *other* forms).
Is it just me, or is (are) there some setting(s) I missed? Or maybe,
it's a bug -considering that VFP Team has spend so much time and effort
to maintain compatibility. Or maybe, VFP9 Beta is actually just for fun
and it should come with warning 'You can try this but don't-even-try-to
open your real work with this' Um, on second thought, I think VFP9b *is*
already come with that warning <sigh>. Oh well, I know that one should
not deploy apps based on beta product, but today I learn another lesson:
one should not use beta product for a non-beta work.
Opinion anyone?
TIA,
Willianto