Forum Discussion
Database and DNS
PK Player Without further knowledge of your network and related...i dare to say that something is wrong all along.
Why would you mess with the DNS for a simple Connection change...just replace the linked table path and that's all...IF you fall in the case that you have Linked Tables :
If you hover your mouse over one of the linked table you should see something like
\\Orion\TheShareName\theBE.mdb
On the other hand...you said that the application is from 1998 ...so probably was made in Access 97...now Access normally cannot "link" to such as older version ....(well it can but it involves some trickery...check my Article on EE : https://www.experts-exchange.com/articles/33729/Importing-Tables-from-Older-Unsupported-Access-databases.html ...but in this case you should have probably NO Linked tables and everything is controlled by code).
It seems like an "interesting" ...so if you could upload some screenshots probably i could assist some more.
Probably ...it would it be as easy as using my utility to pull the records to a new database (it does that...just follow my Article) ...and use the New Table Manager to relink your FE to the new BE...
Thank you. I really appreciate your response and on the surface, it looks like it will do what we need. However, none of us is familiar with Access and we do not understand how this might impact the DB. If it was a simple database I would go with it, but if anything happens and it crashes etc., it would be a disaster.
I think I may just create a new Windows 10 client with the name Orion and have done with it. It will split our data over to another machine (which I was hoping to avoid once the original \\Orion was decommissioned) but it may be the best way forward.
Thanks again.
