I noticed that some (user-defined) class property names change case when I compile (e.g. "Firstname" to "FIRSTNAME" , etc). I have not been able to find a reason for this on any technical forum. Can someone enlighten me?
-
-
This generally happens when an item somewhere accessible in the project already has that name defined. Scope is not too important. It may well not clash scope-wise, but it maintains a list of all terms used and assumes the case should be consistent across all usages.
Bear in mind this is not compilation or interpretation of code. This is related to IntelliSense.
Welcome to Bytes! -
Thanks NeoPa. It does save it that way when I compile. I have to use rudimentary tactics to maintain common code among different databases and this case change throws out differences when I use WinDiff to compare code. I was hoping for a way to prevent the case change. It appears if I change the case and do not compile, then the code does not change when exported.Comment
-
It's unfortunate. It's a limitation in Access - Pure and simple :(
However, this is pretty rare when you use a convention for naming objects. I use a three character prefix for most of my names. "txt" for TextBox control; "int" for integer variables; etc; etc. Although there is still leeway for this to occur, it is much less than without such a naming convention. It's worth considering, but I'll leave it with you.Comment
Comment