I have been given the task of converting an access database back end to an s
ql server back end and then linking these tables to the access front end.

Exporting the back end tables to SQL server was fine, however there is a pro
blem with the autonumber field on a table. This field was exported correctly
, SQL server has this field as a unique identifier.
However when I link this table to the front end and open the table in design
 view, it sees this field as a number field, not an autonumber field so when
 values are inserted from a form into the table, it doesnt generate a number
 for this field and therefore the insert receives an error along the lines o
f 'cannot insert nulls into this field'

How can I link this table into the access front end so the front end correct
ly recognizes this field as autonumber and performs the insert correctly?

[ Post a follow-up to this message ]

The SQL version of autonumber is IDENTITY not UNIQUE IDENTIFIER.


"Friel" <Friel.1h9b9k@mail.webservertalk.com> wrote in message
news:Friel.1h9b9k@mail.webservertalk.com...
>
> I have been given the task of converting an access database back end to
> an sql server back end and then linking these tables to the access
> front end.
>
> Exporting the back end tables to SQL server was fine, however there is
> a problem with the autonumber field on a table. This field was exported
> correctly, SQL server has this field as a unique identifier.
> However when I link this table to the front end and open the table in
> design view, it sees this field as a number field, not an autonumber
> field so when values are inserted from a form into the table, it doesnt
> generate a number for this field and therefore the insert receives an
> error along the lines of 'cannot insert nulls into this field'
>
> How can I link this table into the access front end so the front end
> correctly recognizes this field as autonumber and performs the insert
> correctly?
>
>
>
> --
> Friel
> ------------------------------------------------------------------------
> Posted via http://www.webservertalk.com
> ------------------------------------------------------------------------
> View this thread: http://www.webservertalk.com/message635787.html
>

[ Post a follow-up to this message ]

The SQL version of autonumber is IDENTITY not UNIQUE IDENTIFIER.


"Friel" <Friel.1h9b9k@mail.webservertalk.com> wrote in message
news:Friel.1h9b9k@mail.webservertalk.com...
>
> I have been given the task of converting an access database back end to
> an sql server back end and then linking these tables to the access
> front end.
>
> Exporting the back end tables to SQL server was fine, however there is
> a problem with the autonumber field on a table. This field was exported
> correctly, SQL server has this field as a unique identifier.
> However when I link this table to the front end and open the table in
> design view, it sees this field as a number field, not an autonumber
> field so when values are inserted from a form into the table, it doesnt
> generate a number for this field and therefore the insert receives an
> error along the lines of 'cannot insert nulls into this field'
>
> How can I link this table into the access front end so the front end
> correctly recognizes this field as autonumber and performs the insert
> correctly?
>
>
>
> --
> Friel
> ------------------------------------------------------------------------
> Posted via http://www.webservertalk.com
> ------------------------------------------------------------------------
> View this thread: http://www.webservertalk.com/message635787.html
>

[ Post a follow-up to this message ]