[Reply] HI All,
This thread reminded me of an architecture we developed (hey thanks Wade) where a stub.exe that never, well hardly ever, changed, was run locally and would check the server if there was an update for the main executable stored on the server. If there was a new version available, the stub would download it and then run it from a local location. If no update was available, the latest version downloaded was used. In one version the executable was actually stored in a table in the DB, with rights given to the stub to access just that table. Locally an ini file just gave enough information to locate the DB. All user settings were stored in the DB. Thanks for the memories. Gary At 20:37 on 9/07/2015 you wrote >This is a multi-part message in MIME format. > > > > >Also it doesn't matter where the configuration files are - you can put them on >the client PC, or you can put them on the server, and keyed by either the >login name or the computername (or even both). > >On reading what you are doing I realised that one of my configurations >actually does it back to front from what you described: > >Programs are stored and run from the client PC, but settings are stored on the >server, in inifiles with the individual employees details in the name of the >ini file. > >Reasons are: > >- programs are updated from central folder but run updated automatically to >local pc and run locally for performance reasons and so the central programs >can be updated with no issues. > >- settings stored on server so they can be backed up and administered from >server. Also as well as multiple employee settings all stored together, the >setup is multi-company so that different organisations can share the same >server - ie the name of all files differs for type of >settings/employee/company or organisation/ > >- also allows me to copy whole client configuration onto my system so can >troubleshoot and run exact clients setup without overwriting my setup. > >From: Jeremy Coulter >Sent: Wednesday, July 8, 2015 9:58 PM >To: NZ Borland Developers Group - Delphi List >Subject: [DUG] Question about >running an app. across a network > >Hi All. >I have an app that I will be running from a server location. However, >I want the app. to read an ini file that is located in a folder on a client >machine. >A Shortcut to the app on the server and the ini file will live in a folder on >the client machine, but I cant work out how to get the app, when its run via >the shortcut, to read the ini file on the client machine. >Anyone know how to go about doing this? >I have thought about dropping the INI and transferring the settings to a >database with a row for each machine that connects, but before I get that >carried away, I just wanted to see if someone had any ideas to do the above >with the ini file. >The reason I want an ini for each computer is about settings. Not all machines >have the same settings etc. > >Thanks, Jeremy > > >-------------------------------------------------------------------------------- >_______________________________________________ >NZ Borland Developers Group - Delphi mailing list >Post: [email protected] >Admin: http://delphi.org.nz/mailman/listinfo/delphi >Unsubscribe: send an email to [email protected] with >Subject: unsubscribe > > >_______________________________________________ >NZ Borland Developers Group - Delphi mailing list >Post: [email protected] >Admin: http://delphi.org.nz/mailman/listinfo/delphi >Unsubscribe: send an email to [email protected] with >Subject: unsubscribe Ref#: 41006
_______________________________________________ NZ Borland Developers Group - Delphi mailing list Post: [email protected] Admin: http://delphi.org.nz/mailman/listinfo/delphi Unsubscribe: send an email to [email protected] with Subject: unsubscribe
