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 the
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,

Dianne

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:

>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 the
>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,
>
>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:
>
> >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 the
> >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,
> >
> >Dianne
>
>

"Dianne" wrote:

> 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:
> >
> > >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 the
> > >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,
> > >
> > >Dianne
> >
> >