column named "group" causes problems with new SQLServer

[Maury Markowitz]

Unwisely we called a column in one of our tables "group". We talk to
the table primarily though ADODB code in VBA in Access. This works
fine with our SQL2000 box, but we're moving to SQL2008 (with
compatibility 80) and in testing we found that Access will now give
errors during .Updates on this table.

Any advice here?

Maury

 

[Douglas J. Steele]

I'm actually surprised that it works in any version of SQL Server.

It might work if you put square brackets around the name in your SQL
statement.

For the future, check what Allen Browne has at
http://www.allenbrowne.com/AppIssueBadWord.html It's a comprehensive list of
names to avoid in Access, as well as a link to a free utility to check your
application for compliance.

 

[Maury Markowitz]

But this is the SQL from within Access - not something we wrote. Is
there some way we can tell Access to do this? An ANSI quoting switch
or something?

Maury

 

[Douglas J. Steele]

Change the name of the field!

If you can't change it, create an Alias that is an acceptable name.