>>>>>>Another thing to check for is if you've used the MEMBERDATA property while n VFP9. Once you do that, you may have problems moving back to earlier versions of VFP.
>>>>>
>>>>>Fred,
>>>>>
>>>>>Is there any way to get this working back in VFP8? I probably added MemberData thinking I would not need to use the class in VFP8. But now I have to work with VFP8 again and I'm having this error.
>>>>>
>>>>>UPDATE. Hacking the class and removing _memberdata fixed the problem.
>>>>
>>>>Wow, sure glad you have it solved. I couldn't even remember that message until I saw that it was over a year and a half ago. Really digging in the archives, aren't we? <g>
>>>
>>>Yes. I have another question for something I have in mind and haven't yet tried. Would I be able to use Mark McCasland CABuilder class for VFP9 in VFP8?
>>
>>I'm not sure if he has specific code for VFP9 in his class or not. I haven't looked at it recently.
>
>The memberdata property is not a problem in VFP 8 if the length is less than or equal to 256bytes; under VFP9 any property can now be longer -- upto 8192 bytes. If any property is longer than 256 bytes, then it is incompatible in VFP8 and earlier.


Good point to remember if you need to switch back and forth. I currently have no apps in VFP8 in distribution, so that's not an issue for me.