Upsizing issues from MS Access to SQL2000

[Kumba1]

I exported a table from MS Access as an Excel file, imported it as a temp-table into SQL2000, however, when I run the query to append the data to the proper fields in the Final Table, it only does the first 10,000-records... I know I hafta be missing something here, any ideas? The 10-K records that it does append to the table work like a charm tho... I verified that all 24,000 records we're imported into SQL (atleast when I open the temp-table in the ADP, and tell it to return all records, it says all 24K records are there)... Any ideas? Below is the SQL that i'm using to move the tables... tblItemParts and tblBuildParts are the two tables that i'm trying to move... tblItemParts is the final table, and tblBuildParts is a copy of the old table...
The other table tblItem represent the parent table (basically, the part # information, and tblItemParts is all the parts information, and tblBuilds is the old parent table to tblBuildParts)... basically, I re-structured it a lil, and need to re-do the keys... but it's only appending the first 10,000 records from tblBuildParts into tblItemParts... thanks



INSERT INTO dbo.tblItemParts
(StockNumber, Description, VendorNumber, Vendor, Quantity, Price, Expedite, Pick, Ordered, Arrive, PickDate, OrderedDate, ArriveDate, PORequest,
tblItemPrimaryKey)
SELECT dbo.tblBuildParts.StockNumber, dbo.tblBuildParts.Description, dbo.tblBuildParts.VendorNumber, dbo.tblBuildParts.Vendor, dbo.tblBuildParts.Quantity,
dbo.tblBuildParts.Price, dbo.tblBuildParts.expedite, dbo.tblBuildParts.Picked, dbo.tblBuildParts.Ordered, dbo.tblBuildParts.Arrived,
dbo.tblBuildParts.pickdate, dbo.tblBuildParts.orderdate, dbo.tblBuildParts.etadate, dbo.tblBuildParts.poreq, dbo.tblItem.PrimaryKey
FROM dbo.tblItem INNER JOIN
dbo.tblBuilds ON dbo.tblItem.TrackingNumber = dbo.tblBuilds.TrackingNumber INNER JOIN
dbo.tblBuildParts ON dbo.tblBuilds.[Index] = dbo.tblBuildParts.BuildKey
WHERE (NOT (dbo.tblBuildParts.StockNumber IS NULL))

 

[Kumba1]

Another issue I have is in the Non-ADP version of my database, the clients had a local temp table called "tblTemp" that I used for all the forms so they can edit/hack/screw-up all the data locally before I save it to the server... is it a good idea to do something similar with SQL? and what ways would I go about doing it? I know I can create #-connection-specific-temp-tables that are deleted when the connection dies... but how do I see/reference them? just keep a piece of paper with all the fields on it, and hope I dont get confused? Any help would be much appreciated... and if anyone has any good books i'd appreciate that too