Well, that's just as bad. If updated version is distributed to clients, all their button setups will be lost. Unless the 'upgrade' has code to deal with this.
Well, that's just as bad. If updated version is distributed to clients, all their button setups will be lost. Unless the 'upgrade' has code to deal with this.
How to attach file: http://www.accessforums.net/showthread.php?t=70301 To provide db: copy, remove confidential data, run compact & repair, zip w/Windows Compression.
I manage individual client settings by saving a copy of the settings table(s) to a separate configuration database file.
All changes to those settings are automatically backed up to the config file.
When a new version of the FE is distributed to clients, the install procedure automatically recovers client settings from their copy of the config file.
By doing that I can distribute the same application to multiple clients e.g. schools / companies, each of whom has their own 'personalised' settings