Access 2007 to SQL 2008 - primary and foreign key types

[JClutter]

I'm populating an Access 2007 DB for our SQL (2008) DB admin. The Project
Manager asked me to find out if our ACCESS 2007 DB has primary and foreign
key types that allow "integer" so when we send them our ACCDB version they
can easily convert to an SQL 2008 DB. Do you know if ACCESS 2007 will handle
integer type data for both primary and foreign keys so our ACCDB can easily
convert to a SQL 2008 DB? Any guidance is appreciated.

 

[Jeff Boyce]

Any field in a table can be defined as "number/integer". "Primary" and
"foreign" key fields have more to do with use than definition.

Regards

Jeff Boyce
Microsoft Office/Access MVP

 

[Douglas J. Steele]

In addition to what Jeff said, I believe that Integer in SQL Server
corresponds to Long Integer in Access. The Integer data type in Access is a
2 byte field, limited to values between -32,768 and 32,767. The Long Integer
data type is 4 bytes, so can hold values between -2,147,483,648 and
2,147,483,647.

 

[Albert D. Kallal]

I'm populating an Access 2007 DB for our SQL (2008) DB admin. The Project
Manager asked me to find out if our ACCESS 2007 DB has primary and foreign
key types that allow "integer" so when we send them our ACCDB version they
can easily convert to an SQL 2008 DB. Do you know if ACCESS 2007 will
handle
integer type data for both primary and foreign keys so our ACCDB can
easily
convert to a SQL 2008 DB? Any guidance is appreciated.

Well, actually you want to CONTINUE to use long integer in ms-access.

When they import this data to sql server it will convert them to sql server
"integer" values.

So, on the ms-access side continue using long integers as you always done.

As Douglas points out...in sql server "integer" means long integer in
ms-access....