<div>
Are you importing into an Existing table? If so, just add an Autonumber field to that table ... if you're not importing to an existing table then you'll have to let us know how you're importing. If you're using the builtin features of Access then I'm not sure you can do this ...
</div>


<div>
Yes the fields in the 2 tables are identical.<br />
<br />
&gt;&gt;If all the fields names in the Excel file match existing fields in your table, then you should have no problems completing the import of the file. <br />
<br />
So that would imply that for the 2nd table to be imported, I would have to have the SalesID field added to the excel file? - for the fields to match??<br />
<br />

</div>


<div>
In reply to LMS consulting<br />
<br />
I am importing the first of the 2 excel worksheets into a new table.<br />
I am using the import wizard within Access.<br />

</div>


<div>
in further reply to expert_mkn<br />
<br />
I tried importing a second table but it does not give the option to import into an existing table.<br />
I have not added an extra field to the excel table (the field that now exists in Access as the primary key SalesID autonumber).<br />

</div>


<div>
rutlandict,<br />
<br />
You don't have to add the SalesID field to the 2nd Excel file. &nbsp;Just proceed to import the file, as long as the fields match the first Excel file.<br />
<br />
Did the field names make it into the table upon import of the first Excel file? &nbsp;Does the table have the same fields as the Excel files (with the exception of the SalesID)?<br />
<br />
If so, when you go to import the second (and subsequent) Excel files, you should be able to import to the existing table. &nbsp;Make sure you check the option that says &quot;First Row Contains Column Headings&quot;. &nbsp;You should have used this option to import the first Excel file - so that the column headings are imported from Excel to the Access table.<br />
<br />
Mike
</div>


<div>
Ok I will try that tomorrow. I think I went for column headings but not sure!<br />
<br />
Yes the field names made it into the Access table - and are the same as the excel file. SalesID got added ok as autonumber.<br />
<br />
There is one problem with respect to one filed getting converted from a number to something like 5.0114583+E12<br />
They are bar codes. But I'll come back to that or raise another question.<br />
<br />
thanks for your help so far.
</div>


<div>
No it will not import the file. I have even simplified the excel file down to less than 200 rows and still get an error importing.<br />

</div>


<div>
rutlandict,<br />
<br />
i saw that you accepted my solution. &nbsp;did it finally work out for you?<br />
<br />
btw-- is rutlandict related to rutland, VT?<br />
<br />
mike<br />

</div>


<div>
<div class="content wysiwyg-content">
I have data in Excel, in 2 tables of about 40,000 and 50,000 rows (due to row limit size). I want these to be transferred to access in 1 table.<br />
<br />
I also want the primary key of the new Access table to be an autonumber field starting at 1 (called &quot;Sales ID&quot;)<br />
I tried to create a Sales ID field in excel before bringing ht edata in but then found I could not convert the field to autonumber.<br />
<br />
In future, more data (about 100-200 new rows each week) will need to be imported.<br />
not sure if this requirement has any bearing on the solution requested above (I cant see how you can import multiple rows from Excel into an existing table and cause the primary key autonumber field to get populated automatically).<br />
<br />
The data supplied weekly in excel format will not have the primary key sales ID field in it.<br />
<br />

</div>
</div>


I have data in Excel, in 2 tables of about 40,000 and 50,000 rows (due to row limit size). I want these to be transferred to access in 1 table.

I also want the primary key of the new Access table to be an autonumber field starting at 1 (called "Sales ID")
I tried to create a Sales ID field in excel before bringing ht edata in but then found I could not convert the field to autonumber.

In future, more data (about 100-200 new rows each week) will need to be imported.
not sure if this requirement has any bearing on the solution requested above (I cant see how you can import multiple rows from Excel into an existing table and cause the primary key autonumber field to get populated automatically).

The data supplied weekly in excel format will not have the primary key sales ID field in it.



Import data from excel then add autonumber field: 90000 rows

Microsoft Access is a rapid application development (RAD) relational database tool. Access can be used for both desktop and web-based applications, and uses VBA (Visual Basic for Applications) as its coding language.