Harry,

>>I'd copy all the classlibs from their 6 location to a parallel place for 8 and never use the other version to edit the respective classlib.
>
>not even after the copying?

I'd only ever use VFP6 on the VFP6 version of the classlib, and VFP8 on the VFP8 version. If you have to maintain the codebase in both versions you are up for a bit of duplicated work.

>never done that just for a classlib. Just tried it and got "unrecognised command". Whats the appropriate command and syntax?

COMPILE CLASSLIB xyz

>Just 3 Properties ('proper','upper','orivalue'). Other than that the customisation consists of some code in the standard PEMs.

proper and upper do conflict with VFP reserved words. VFP8 is probably choking on these. The error it chokes with isn't a very good indication of what's really wrong, but then again VFP has several places where its error messages don't give you much help diagnosing what's wrong.

go back to 6, copy the classlib to a new classlib name, go in and edit the copy and change proper and upper to harryproper and harryupper. then copy the newclasslib to vfp8, compile it and see if you can edit the beast.

>Just cleared both the Properties and Methods memos to see if that makes any difference. Nada.

In this case the problem might be stemming from the reserved memo that's holding the PEM names.

>Clutching at straws: just tried recreating the class by creating a new line in the vcx and cutting and pasting the contents of the original into the new line. I manually amended the Unique ID to keep it unique and didn't copy the objcode.

You have to make sure lots of other stuff is right if you are trying to do this. it's better to go to the row, scatter name ox memo, append blank, gather name ox memo, then change things. Issue a COMPILE CLASSLIB before you try to use the designer.