Hi Michel,

Since I'm just getting into VB I thought I would share the neat (in my humble opinion) way that VB has to get around this. . .

You can include reserved words as names (maybe only for certain things only (not certain on that) ) provided that the "user's" (ie the coder's) names are enclosed in the "[" / "]" (left-bracket / right-bracket) characters.

This also gives a way to get around this if some FUTURE reserved word conflicts with a name already used in a program. Sure, one has to change one's code when that happens, but only to add the brackets, not to actually change names everywhere.

Cheers,

Jim N

>>So, is it the consenus then that it is a bad/dangerous thing to name my Primary index "PRIMARY"?
>
>This is an interesting discussion. I think we've all been in that situation once.
>
>More than that, we also have to think ahead. Which means, a word used in code, index definition, etc., might be available to use now but may become a reserved word for upcoming versions.