Solved

Option :sql server compatible syntax ansi 92

Posted on 2015-02-20
3
520 Views
Last Modified: 2015-02-24
I am upgrading several Access 2003 databases to Access 2013.  These are slit databases with Access fornt ends and backends.

One of the options that can be set in the 'Object Designers' window of the 'Access Options is:

sql server compatible syntax ansi 92
  'This Database'                              can be checked
  or
  'Default for New Databases'       can be checked'

I have read that the difference is that queries etc.. have to be Ansi 92 compliant if this box is checked for an existing database.  Is this also true of any SQL executed in the VBA code?

Without looking at every query I have no idea if the queries would be compliant since I didn't create most of them.  Seems like the safe thing to do would be to leave this box unchecked for database being upgraded from earlier versions of Access.
However, upgrading to 2013 is just the first step in the long term plan, which will later transition the backend database, now in Access to SQL Server.

Step 1. Upgrade to the 2013 version of Access, test and install in production using an Access DB as the data respository.
Later, as a separate project
Step 2. Replace the Access backend with SQL Server.

I just want to make you aware of the long term plan, in case it would influence your answer to the question:  Which of these options should I choose when upgrading from 2003 to 2013 and what are the implications of the choice.
0
Comment
Question by:mlcktmguy
3 Comments
 
LVL 49

Expert Comment

by:Gustav Brock
ID: 40622766
If you don't mark this option, you will use ANSI-89 which is what Access uses by default for SQL.

A reason for marking the ANSI-92 option is that it makes it easier to interchange SQL between SQL Server and Access. If you have no plans for this, continue using ANSI-89.

/gustav
0
 
LVL 35

Accepted Solution

by:
PatHartman earned 500 total points
ID: 40625073
Whether you convert the BE to SQL Server or not, you can leave the default as ANSI-89 syntax.  There isn't any benefit to moving to a different version since ACE doesn't support newer operations anyway.  ANSI-92 is pretty old and there are newer standards.  The ODBC driver takes care of any conversion that is necessary so I wouldn't spend the time and money to change the syntax for no real benefit.
0
 
LVL 1

Author Closing Comment

by:mlcktmguy
ID: 40628468
Thanks you, that is exactly the kind of detailed feedback I was hoping for.
0

Featured Post

Optimizing Cloud Backup for Low Bandwidth

With cloud storage prices going down a growing number of SMBs start to use it for backup storage. Unfortunately, business data volume rarely fits the average Internet speed. This article provides an overview of main Internet speed challenges and reveals backup best practices.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Overview: This article:       (a) explains one principle method to cross-reference invoice items in Quickbooks®       (b) explores the reasons one might need to cross-reference invoice items       (c) provides a sample process for creating a M…
This article shows gives you an overview on SQL Server 2016 row level security. You will also get to know the usages of row-level-security and how it works
With Microsoft Access, learn how to start a database in different ways and produce different start-up actions allowing you to use a single database to perform multiple tasks. Specify a start-up form through options: Specify an Autoexec macro: Us…
With Secure Portal Encryption, the recipient is sent a link to their email address directing them to the email laundry delivery page. From there, the recipient will be required to enter a user name and password to enter the page. Once the recipient …

773 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question