I hope someone can shed light on this weirdness. The actual details would take hours to describe, but the simplest description of this repeatable problem is as follows:
My front end has a link to tblHistory in the back end database.
I double click the link to open it and see that it has 100 columns BUT it is supposed to have 115.
Repairing database and relinking does NOT fix the problem.
Trying again on a different machine with more recent version of Access does NOT fix the problem
Deleting the link and recreating it DOES fix the problem.
I have been using Access for many years, and this just seems wrong to me. I suspect there may be corruption that is not being caught by the repair utility.
Here are some more details.
I have 3 databases on 3 commputers:
my Lenovo laptop with Access 2010 has c:\FEFolder\FE.mdb (A single image of this front end file is copied to every client's c: drive every day.)
my "production machine" has a network share \\wseserver\sharename\BEFolder\BEProd.mdb
my "development machine" Dell Desktop has Access 2007 and c:\myprofile..\documents\BENew.mdb.
The Back Ends both contain tblHistory which has 115 columns. Originally that table only had 100 columns, but a month ago I added 15 columns on both machines.
On Saturday night, I deleted BEProd.mdb then copied BENew to production and renamed it to BEProd.mdb
On Monday morning I opened FE.mdb and noticed that FE.mdb only had 100 columns in tblHistory!
I tried running my relinkEverything macro, but there were still only 100 columns.
I then used linked table manager with "always prompt for new location" to manually relinked tblHistory to BEProd.mdb but I still only had 100 columns.
I then deleted the link and recreated it using Ribbon > External Data > Import and Link > Access > link.
THAT WORKED, all 115 columns were now visible.'
If found this very perplexing, so I restored Monday morning's FE data base and the same thing happened.
I again restored FE and repaired both BEProd and FE. Once again, FE started with 100 columns; relinking did not fix it; deleting and recreating did fix it;
So, I then decided try on an Access 2013 Desktop. Same problem I must delete the tblHistory link and recreate it to get 115 columns.
I am not too worried because everything else seemed OK and there were no error messages on any of the client computers.
But, I cannot easily restore the Back End since users are frequently making updates. But perhaps some experts have seen similar behavior and can reassure me that it is normal??