Will do. Thanks for your post.

>Hi Russell
>
>I have encountered this problem as well. It's not really critical within foxpro, but; if you are building dlls that are called by case sensitive languages like C#, then you have some real problems. As a property, perhaps, called "verifypassword", when changed to "VERIFYPASSWORD" by FoxPro is going to cause a fatal error, for a C# developer, when he attempts to call it in his code.
>
>I too, can find no rhyme or reason for it. I even took all my class code over to a programmatic class (prg), in case it was something to do with the class builder interface - but no joy. Yet, I can come in the next day build the dll, create an instance of it and dah! dah! all back to lowercase again.
>
>Opening the class vcx as at table and checking out the properties, yields no answers either, as all of them are lowercase - except the native FoxPro properties which are camel case.
>
>Looking through the programmatic class (prg) that I created's fxp; I noticed that all the non-native properties are uppercase, this doesn't prove anything, but it does make you wonder if FoxPro is doing something to allow it to differentiate between native and non-native properties - I don't know.
>
>If you find out an answer, please pass it on. I'm keen to find out myself.
>
>Thanks