469,904 Members | 2,049 Online
Bytes | Developer Community
New Post

Home Posts Topics Members FAQ

Post your question to a community of 469,904 developers. It's quick & easy.

A97 query field named "Description" is a problem

MLH
I have a query field...
Description: [VColor] & "2-tone"

When I run it, the output in that field is empty.
If I change the name to MyDescription - it works fine.
I noticed the query field has a Description property setting.
That's what's causing my problem. Just a 'heads-up' to the
group letting you know to watch out for it.

It took me a long time to recognize the error. I have another
query with a field of the same name that has NEVER caused
me a problem. I used that query as a template when creating
this one. So it wasn't my first instinct to suspect the chosen
field name was a problem.
Nov 13 '05 #1
11 1830
MLH
Looking further, I see I have a table with one field
named "Description" in another database. Even
though HELP (under Field Names) doesn't strictly
forbid it and the HELP (under naming conventions)
doesn't strictly forbid it - anybody think that could
cause confusion down the line?

Believe me, the deal with the query was difficult to
figure out. Reports referencing that query and that
field would sometimes say [Description] field not found
and other times, Access 97 would lock up saying it
had to close when I merely attempted to open the report
in design view after creating and saving it.
Nov 13 '05 #2

"MLH" <CR**@NorthState.net> wrote in message
news:nk********************************@4ax.com...
I have a query field...
Description: [VColor] & "2-tone"

When I run it, the output in that field is empty.
If I change the name to MyDescription - it works fine.
I noticed the query field has a Description property setting.
That's what's causing my problem. Just a 'heads-up' to the
group letting you know to watch out for it.

It took me a long time to recognize the error. I have another
query with a field of the same name that has NEVER caused
me a problem. I used that query as a template when creating
this one. So it wasn't my first instinct to suspect the chosen
field name was a problem.


Yep. Description is a reserved word in Access. It should never be used for
the name of an object. Some place in the help there's a complete list of
reserved words, but it's near impossible to find.

Nov 13 '05 #3
MLH wrote:
Looking further, I see I have a table with one field
named "Description" in another database. Even
though HELP (under Field Names) doesn't strictly
forbid it and the HELP (under naming conventions)
doesn't strictly forbid it - anybody think that could
cause confusion down the line?

Believe me, the deal with the query was difficult to
figure out. Reports referencing that query and that
field would sometimes say [Description] field not found
and other times, Access 97 would lock up saying it
had to close when I merely attempted to open the report
in design view after creating and saving it.


I have never seen a problem with a field named "Description". There is a help
topic in Access 97 that lists all of the reserved words and "Description" is not
one of them (though "Desc" is).

--
I don't check the Email account attached
to this message. Send instead to...
RBrandt at Hunter dot com
Nov 13 '05 #4
Randy Harris wrote:
Yep. Description is a reserved word in Access. It should never be
used for the name of an object. Some place in the help there's a
complete list of reserved words, but it's near impossible to find.


Not in Access 97 it's not. At least the help topic doesn't mention it.

--
I don't check the Email account attached
to this message. Send instead to...
RBrandt at Hunter dot com
Nov 13 '05 #5
MLH
>Yep. Description is a reserved word in Access. It should never be used for
the name of an object. Some place in the help there's a complete list of
reserved words, but it's near impossible to find.


Personally, I think it should come with a flashing red warning anytime
someone tries to use it. Its such a natural choice one can easily get
lulled into picking - whether by accident or on purpose. Either way,
can cause real probs down the road with very non-descript errors.
If a fieldname choice can cause Access to hang or unexpectedly
close, it deserves some kind of special treatment.
Nov 13 '05 #6
MLH wrote:
Personally, I think it should come with a flashing red warning anytime
someone tries to use it.


Now that would be an excellent enhancement to Accesss, IMO. I remember
about 8 years ago, I couldn't for the life of me figure out why a Jet
query I'd worked very hard on was crashing. Turned out it was the use
of "Tag" as a field name, another choice quite natural for someone
relatively new to this business to choose like "decription" or "name" or
"date".

Mind you, it's also a good reason to settle on a naming convention that
will certainly bypass any reserved word. Personally, for field names, I
use the underscore technique a lot of Oracle developers use, along with
a prefix, ie, VEH_DESCRIPTION for description of a vehicle in a a
vehicle table. I find this method much easier to read than the Resnick
convention, though I still use the latter for naming variables and
procedures in my VBA code.

--
Tim http://www.ucs.mun.ca/~tmarshal/
^o<
/#) "Burp-beep, burp-beep, burp-beep?" - Quaker Jake
/^^ "Whatcha doin?" - Ditto "TIM-MAY!!" - Me
Nov 13 '05 #7
Sorry. It's a property in A2K, I mistakenly assumed that it was in A97
also.
"Rick Brandt" <ri*********@hotmail.com> wrote in message
news:8b****************@newssvr11.news.prodigy.com ...
Randy Harris wrote:
Yep. Description is a reserved word in Access. It should never be
used for the name of an object. Some place in the help there's a
complete list of reserved words, but it's near impossible to find.


Not in Access 97 it's not. At least the help topic doesn't mention it.

--
I don't check the Email account attached
to this message. Send instead to...
RBrandt at Hunter dot com


Nov 13 '05 #8
rkc
Randy Harris wrote:
Sorry. It's a property in A2K, I mistakenly assumed that it was in A97
also.
"Rick Brandt" <ri*********@hotmail.com> wrote in message
news:8b****************@newssvr11.news.prodigy.com ...
Randy Harris wrote:
Yep. Description is a reserved word in Access. It should never be
used for the name of an object. Some place in the help there's a
complete list of reserved words, but it's near impossible to find.


Not in Access 97 it's not. At least the help topic doesn't mention it.


http://support.microsoft.com/kb/q109312/

Nov 13 '05 #9

"rkc" <rk*@rochester.yabba.dabba.do.rr.bomb> wrote in message
news:OO*******************@twister.nyroc.rr.com...
Randy Harris wrote:
Sorry. It's a property in A2K, I mistakenly assumed that it was in A97
also.
"Rick Brandt" <ri*********@hotmail.com> wrote in message
news:8b****************@newssvr11.news.prodigy.com ...
Randy Harris wrote:

Yep. Description is a reserved word in Access. It should never be
used for the name of an object. Some place in the help there's a
complete list of reserved words, but it's near impossible to find.

Not in Access 97 it's not. At least the help topic doesn't mention it.


http://support.microsoft.com/kb/q109312/


Hmm... It seems Microsoft thinks it's a reserved word.

Nov 13 '05 #10
Randy Harris wrote:
"rkc" <rk*@rochester.yabba.dabba.do.rr.bomb> wrote in message
news:OO*******************@twister.nyroc.rr.com...
Randy Harris wrote:
Sorry. It's a property in A2K, I mistakenly assumed that it was
in A97 also.
"Rick Brandt" <ri*********@hotmail.com> wrote in message
news:8b****************@newssvr11.news.prodigy.com ...

> Randy Harris wrote:
>
> > Yep. Description is a reserved word in Access. It should
> > never be used for the name of an object. Some place in the
> > help there's a complete list of reserved words, but it's near
> > impossible to find.
>
> Not in Access 97 it's not. At least the help topic doesn't
> mention it.


http://support.microsoft.com/kb/q109312/


Hmm... It seems Microsoft thinks it's a reserved word.


I guess they expanded the list at some point. Here are all of the "D"s listed
in my help file

DATABASE
DATE
DATETIME
DELETE
DESC
DISALLOW
DISTINCT
DISTINCTROW
DOUBLE
DROP

--
I don't check the Email account attached
to this message. Send instead to...
RBrandt at Hunter dot com
Nov 13 '05 #11
Rick Brandt wrote:
it's a reserved word.

I guess they expanded the list at some point. Here are all of the
"D"s listed in my help file

DATABASE
DATE
DATETIME
DELETE
DESC
DISALLOW
DISTINCT
DISTINCTROW
DOUBLE
DROP


On further review I see that the help topic I was looking at is entitled "SQL
Reserved words". I had searched and found a topic labelled "Reserved words" in
the index and never noticed the "SQL" part in the title that came up. I'm sure
that the list for VBA and SQL have some overlap but that there are also distinct
entries in both as well.

--
I don't check the Email account attached
to this message. Send instead to...
RBrandt at Hunter dot com

Nov 13 '05 #12

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

2 posts views Thread by Michele Fondry via .NET 247 | last post: by
1 post views Thread by Waqarahmed | last post: by
By using this site, you agree to our Privacy Policy and Terms of Use.