Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion GroupsFormsForms ProgrammingQueriesModules / DAO / VBAReports / PrintingMacrosDatabase DesignSecurityConversionImporting / LinkingSQL Server / ADPMultiuser / NetworkingReplicationSetup / ConfigurationDeveloper ToolkitsActiveX ControlsNew UsersGeneral 1General 2
Access DirectoryToolsTutorialsUser Groups
Related Topics
SQL ServerOther DB ProductsMS OfficeMore Topics ...

MS Access Forum / General 2 / January 2008

Tip: Looking for answers? Try searching our database.

Import New Table; Set Primary Key As AutoNumber

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
ryguy7272 - 15 Jan 2008 22:42 GMT
I've procrastinated long enough; I'm starting to learn Access now.  I know a
little actually, but not much.  Anyway, I'm practicing with the NWind DB.  I
exported each table to an Excel sheet and then tried to import each Excel
sheet to a new DB that I just created.  A bit silly, but it's really helping
me to learn.  I though I had a handle on it, but when I tried to import the
'Orders' table, it comes in kind of weird.  Under Field Name 'OrderID', the
Data Type is Number, but I want it to be AutoNumber so I can create
Relationships.  I can't seem to import this Table as AutoNumber and I can't
copy/paste the data from DataType Number to DataType AutoNumber after I
insert a row in Design View.  Can someone please explain how to get DataType
AutoNumber to override DataType Number

Regards,
Ryan--

Signature

RyGuy

Jeff Boyce - 15 Jan 2008 23:30 GMT
Autonumbers are not required for relationships.  Access Autonumbers are just
one way of coming up with a unique row identifier.  If you have another
table that uses LongInt data to point back at a unique row identifier
(primary key) in a "parent" table, I don't believe it will make any
difference if that unique identifier is a LongInt or an Autonumber data
type.

Now, if you want to be able to ADD new records and have a unique identifier
automatically generated, Autonumber can do the job.  But that's a different
question...

Regards

Jeff Boyce
Microsoft Office/Access MVP

> I've procrastinated long enough; I'm starting to learn Access now.  I know
> a
[quoted text clipped - 17 lines]
> Regards,
> Ryan--
ryguy7272 - 17 Jan 2008 21:25 GMT
There seems to be a problem with the Data Export process.  I click on the
Table (Orders) and then File > Export and choose a destination for the file.  
When I try to import it from the Excel sheet, I can look at the Column
headings and I see they are slightly different.  Also, the data in some of
the columns is VERY different.  Instead of names in the Employee column I
have numbers, and in place of the names in the Ship Via column, again I have
numbers!!  I guess this is preventing me from linking the tables and
establishing the relationships.

Looks like my Excel experience won't help me one bit in the Access world...

Signature

RyGuy

> Autonumbers are not required for relationships.  Access Autonumbers are just
> one way of coming up with a unique row identifier.  If you have another
[quoted text clipped - 33 lines]
> > Regards,
> > Ryan--
ryguy7272 - 17 Jan 2008 21:44 GMT
I just found something called 'Field Size' under design view.  That must be
what you were referring to because I made a few modifications to that
property and then I was able to link all the tables!  I just bought two
Access books from Borders yesterday.  Well, time to start reading.

Thanks for the tip Jeff.

Regards,
Ryan---

Signature

RyGuy

> Autonumbers are not required for relationships.  Access Autonumbers are just
> one way of coming up with a unique row identifier.  If you have another
[quoted text clipped - 33 lines]
> > Regards,
> > Ryan--
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2009 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.