Reserve Words in Access 2003

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I read a response to a recent question that said you should never name a
field date, as it is a reserve word for access. I have a database that i
have been using for 6 months and i have used date as a field in several of my
tables. I was wondering how important is it to not do this and what might
happen if i am?
 
using reserved words as names (of anything that *you* name in a database) is
like setting little booby-traps in your database. sooner or later you're
going to run into problems when using those mis-named objects in
expressions, or macros, or VBA code. you may get unexpected results that you
can't figure out, or error messages that make no apparent sense for the
circumstances. and not having problems "so far" is unfortunately not an
accurate predictor of potential problems in the future. many developers feel
that it's better to avoid the problem from the get-go, rather than take
their chances. (btw, an easy way to make sure you don't *accidentally* use a
reserved word that you didn't realize was reserved, is to put a prefix or a
suffix on the name of anything that you name in your database.)

hth
 
Back
Top