This is going to be a bit difficult to explain, so please bear with me.
To give a bit of background, I use an update query to import bulk data (originally sourced from an Excel spreadsheet) in to a table called SoftwareKeys
Code:
INSERT INTO SoftwareKeys ( KeyNo, Supplier, PurchaseDate, OrderNo, SoftwareName, OriginalLevel, Notes )
SELECT [_ImportFromExcel].KeyNo, [_ImportFromExcel].Supplier, [_ImportFromExcel].PurchaseDate, [_ImportFromExcel].OrderNo, [_ImportFromExcel].SoftwareName, [_ImportFromExcel].OriginalLevel, [_ImportFromExcel].KeyNoNotes
FROM _ImportFromExcel;
The DB has a form (Software Keys Entry Form) that users then use to assign the KeyNo to a CustomerID. They search for KeyNo and then fill in CustomerID, SoldDate and Notes. Everything else is populated by the update query.
This all worked very well before I split the DB.
After I split the DB I have found that the combo box on the form now does not show the table data of the data field SoftwareName. The update query still works fine as I can see the SoftwareName imported in to the SoftwareKeys table. It's just not showing up on the form.
The combo box SoftwareName is bound to the table SoftwarePackages.
As I said, this all worked perfectly prior to my splitting the DB. I've been tinkering with trying to find a solution, but don't know where the actual problem lies.
I have found that if I change the EXCEL spreadsheet column to reflect the SoftwareNameID, rather than the SoftwareName, then it works OK.
Am I missing something really obvious here? And suggestions would be greatly appreciated.