I have an application (Access 2007) which involves a number of computers accessing a common backend data file via a Windows share. Nearly all of the data is common to all, and is therefore in the backend file.
However, there are a few bits of information which are computer-specific (such as the location of external file paths when exporting data), and I have been storing these in a local table inside the front end.
This is fine, except when it comes to doing an upgrade, when its a real pain. If I distribute a new front-end, the local data is all lost and has to be recreated.
I'm now thinking of changing this so that machine-specific information is stored in a backend table, with one record per machine. I have a function already to look up ComputerName, so was thinking of just using that to index into the table.
I'd need to have code on startup to check to see if this machine already exists in the table, and if not then create a new record with sensible defaults.
Are there any drawbacks I haven't thought of?
Can I rely on Windows (XP, Vista or 7) to insist that every machine has a ComputerName and to flag to users if there is a duplicate on the network? There are several separate installations of this application, and they are all (
AFAIK) running on small "home" networks - no Active Directories anywhere.
Thoughts from an experienced hand would be welcome.
TIA.