Access 97 to SQL Conversion

I have an Access 97 program that for many years linked to tables in another
database through drive letter access. Recently, because of speed, we
converted the Access tables to a SQL Server 2000 database and linked the
tables via an ODBC connection.
The program can read the tables but there are several problems. The append
queries that are trying to build new records in one of the SQL tables keep
giving a key violation error. Also, a few of the screens used to append
records to some of the tables no longer let me add records. It will show th
e
records that were originally imported, and let me delete them, but not add.
The first time I converted, many of the Access queries wouldn't work and we
discovered that in the conversion, the Autonumbering in many of the tables
got lost. Since then, I have set the Identity to Yes and when viewing the
design of the ODBC tables through Access, they are now showing as Autonumber
.
Is there some incompatibility between Access 97 and SQL server 2000, or do I
have the wrong data types in the SQL tables? Is there something wrong with
the way I set up Autonumbering in SQL? When the data was all in Access, I
had no problem appending records, but now that the data is in SQL.... what
am I missing?
Please help!
Thanks,
DianneIs your front-end Access 97? If so, then you'll solve a lot of your
problems by upgrading to Access 2003. Access 97 is no longer
supported, and never worked smoothly with SQLS 2000, mostly due to
data type incompatibilities.
--Mary
On Fri, 20 May 2005 11:49:37 -0700, Dianne
<Dianne@.discussions.microsoft.com> wrote:

>I have an Access 97 program that for many years linked to tables in another
>database through drive letter access. Recently, because of speed, we
>converted the Access tables to a SQL Server 2000 database and linked the
>tables via an ODBC connection.
>The program can read the tables but there are several problems. The append
>queries that are trying to build new records in one of the SQL tables keep
>giving a key violation error. Also, a few of the screens used to append
>records to some of the tables no longer let me add records. It will show t
he
>records that were originally imported, and let me delete them, but not add.
>The first time I converted, many of the Access queries wouldn't work and we
>discovered that in the conversion, the Autonumbering in many of the tables
>got lost. Since then, I have set the Identity to Yes and when viewing the
>design of the ODBC tables through Access, they are now showing as Autonumbe
r.
>Is there some incompatibility between Access 97 and SQL server 2000, or do
I
>have the wrong data types in the SQL tables? Is there something wrong with
>the way I set up Autonumbering in SQL? When the data was all in Access, I
>had no problem appending records, but now that the data is in SQL.... what
>am I missing?
>Please help!
>Thanks,
>Dianne|||You are so right! I am upgrading the program as we speak. Thanks!
Dianne
"Mary Chipman [MSFT]" wrote:

> Is your front-end Access 97? If so, then you'll solve a lot of your
> problems by upgrading to Access 2003. Access 97 is no longer
> supported, and never worked smoothly with SQLS 2000, mostly due to
> data type incompatibilities.
> --Mary
> On Fri, 20 May 2005 11:49:37 -0700, Dianne
> <Dianne@.discussions.microsoft.com> wrote:
>
>|||"Dianne" wrote:
[vbcol=seagreen]
> You are so right! I am upgrading the program as we speak. Thanks!
> Dianne
> "Mary Chipman [MSFT]" wrote:
>|||I am experiencing the same issues with SQL Server 2005 and Access 97. I don'
t
think it is cost effective for us to convert to Access 2003 because we would
have to purchase 12+ liscenses and we are re-writing the app in ASP.Net afte
r
we get the backends converted and stable.
So ... is there any workarounds for this incompatibilities? What are they in
more detail, I am just testing and finding the same issues Dianne is having
(certain forms will not allow edits, some DOA recordsets will not not add
records?).
Thanks ahead of time, Rick
"Mary Chipman [MSFT]" wrote:

> Is your front-end Access 97? If so, then you'll solve a lot of your
> problems by upgrading to Access 2003. Access 97 is no longer
> supported, and never worked smoothly with SQLS 2000, mostly due to
> data type incompatibilities.
> --Mary
> On Fri, 20 May 2005 11:49:37 -0700, Dianne
> <Dianne@.discussions.microsoft.com> wrote:
>
>|||From a SQL Server perspective, you can TRY running the SQL
Server 2005 user database is a lower compatibility mode but
if you are using a front end that's no longer supported, it
would probably just minimize some of the issues - if even
that.
But you'd probably find more information on working around
the Access 97 issues in one of the Microsoft Access
newsgroups.
-Sue
On Fri, 29 Sep 2006 14:12:01 -0700, Rick Vooys
<RickVooys@.discussions.microsoft.com> wrote:
[vbcol=seagreen]
>I am experiencing the same issues with SQL Server 2005 and Access 97. I don
't
>think it is cost effective for us to convert to Access 2003 because we woul
d
>have to purchase 12+ liscenses and we are re-writing the app in ASP.Net aft
er
>we get the backends converted and stable.
>So ... is there any workarounds for this incompatibilities? What are they i
n
>more detail, I am just testing and finding the same issues Dianne is having
>(certain forms will not allow edits, some DOA recordsets will not not add
>records?).
>Thanks ahead of time, Rick
>"Mary Chipman [MSFT]" wrote:
>|||Thanks Sue. Can you elaborate on the lower capability mode? What would we
lose? Is this something you can just switch on and off? How would one go int
o
one of these modes?
"Sue Hoegemeier" wrote:

> From a SQL Server perspective, you can TRY running the SQL
> Server 2005 user database is a lower compatibility mode but
> if you are using a front end that's no longer supported, it
> would probably just minimize some of the issues - if even
> that.
> But you'd probably find more information on working around
> the Access 97 issues in one of the Microsoft Access
> newsgroups.
> -Sue
> On Fri, 29 Sep 2006 14:12:01 -0700, Rick Vooys
> <RickVooys@.discussions.microsoft.com> wrote:
>
>|||You'd loose the functionality introduced in the higher
version. You can change between different compatibility
levels and change back to 9.0. To do so, you would executed
sp_dbcmptlevel. You can find a lot of information on this
system stored procedure and the behavioral, functional
differences in books online under sp_dbcmptlevel.
-Sue
On Mon, 2 Oct 2006 09:53:02 -0700, Rick Vooys
<RickVooys@.discussions.microsoft.com> wrote:
[vbcol=seagreen]
>Thanks Sue. Can you elaborate on the lower capability mode? What would we
>lose? Is this something you can just switch on and off? How would one go in
to
>one of these modes?
>"Sue Hoegemeier" wrote:
>