DataBase - column named "group" causes problems with new SQLServer
Asked By Maury Markowitz
20-Nov-09 02:42 PM
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 are 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
SQL Server 2008
(1)
SQL Server 2000
(1)
ADODB
(1)
VBA
(1)
DougSteele
(1)
Douglas J. Steele replied to Maury Markowitz
I am 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 is a comprehensive list of
names to avoid in Access, as well as a link to a free utility to check your
application for compliance.
--
Doug Steele, Microsoft Access MVP
http://I.Am/DougSteele
(no e-mails, please!)
Maury Markowitz replied to Douglas J. Steele
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 replied to Maury Markowitz
Change the name of the field!
If you cannot change it, create an Alias that is an acceptable name.
--
Doug Steele, Microsoft Access MVP
http://I.Am/DougSteele
(no e-mails, please!)
Might be outgrowing Access but daunted by SQL Server DataBase I am close to completing the consolidation of various small Access databases and a spent the last 10 hours downloading, installing and trying to get my head around Microsoft SQL Server 2008 Express and how it might help me out. It all started when I came across encouraging article on keeping your Access database as your front end application and linking to SQL Server database tables. I am finding it MUCH more complicated than I had hoped. Can anyone be happy to use my quite powerful workstation at the office as some kind of server. You may have guessed by now that I am no IT guru by any stretch
SQL Server DataBase Hall?schen, ich habe mit einem SQL Server noch nie was am Hut gehabt. Alles was ich bisher gemacht hatte, da war Access immer ausreichend. Nun aber ist eine Anforderung, das ein Backend auf einem SQL-Server laufen soll, wobei dar?ber noch nicht fertig diskutiert ist. Ich habe da noch eine alte Vollversion von VB6, dort ist ein SQL-Server dabei (fracht mich aber nicht welche Version, der Karton mit der VB6 steht noch in
proof DataBase https: / / mcp.microsoft.com / authenticate / validatemcp.aspx transcript: 944364 AccessCode: helloworld Access Discussions SQL Server 2008 R2 (1) SQL Server 2008 (1) SQL Server 2005 (1) Microsoft SQL Server Reporting Services (1) Regards Larry Linson Microsoft Office Access (1
Using Mysql or SQL server as backend to Access front end DataBase Have a client having problems with a fairly end. Using access 2003 / mdb format with Access 2007 software. We are surmising that recent server problems or connectivity problems may be to blame. If we converted to MySQL or SQL server as the back end, would that eliminate the potential for Database corruption that can occur drivers? I also read that Jet will process query criteria that it can on the SQL server before the results are sent back. correct? does this also happen when you link to MySQL? A while back I got the book "Microsoft Access Developer's Guide to SQL Server" - SAMs - Chipman and Baron. As I recall, switching to SQL server is not for
Cannot link to SQL server DataBase Can any of you guys help? I am new to using SQL Server. I have a database that I wish to upsize from Access to put the back end on a server, and use Access as a front-end. However, I am stuck at the very first stage - I cannot link Access to the SQL server. I am using SQL Server Management Studio on a single computer for development purposes, no network involved yet. In