When we deploy to businesses, they typically have a server, and we have either Postgres or the Omnis Databridge installed on that server. Each workstation has a config file that points to the database. We set it up as an INI file, so we can have other parameters including the location of the LANUpdates folder. When they first run the software in their user profile, it will ask them where the LANUpdates folder is. When they locate it, it copies all the other parameters like database connection details etc to the user’s AppData folder. Once they have the connection details, it can then query the database for the latest version and download the updated libs to their profile.
If you don’t have any kind of central server, but you want the software to be same across profiles on the workstation, perhaps you can use a central location such as the “Program Data” folder? The local app data profile still has some Omnis components, but you could have a “startup library” that points to the actual libraries in the Program Data folder, so that all profiles access the same libs.
A man rushed into the doctor’s office and shouted, “Doctor! I think I’m shrinking!”
The doctor calmly responded, “Now, settle down. You’ll just have to be a little patient.”
Paul W. Mulroney
We Don't Do Simple Pty Ltd
ACN 161 009 374
Bentley Western Australia 6102