Good morning Jolyon, I guess everyone has a view about what is the right/best way. Not everyone is selling something. :-)
May I ask what is your right/best way? Regards Leigh On 9 July 2015 at 09:21, Jolyon Smith <[email protected]> wrote: > What data is in the INI ? How much data ? What type of data ? How is it > used ? How would machines be identified in a database solution ? By name > or network ID ? If by name, what happens if a machine name is changed ? > > "Database" or "file" are simply different technologies that could be used > in an implementation. But technology alone rarely identifies the right (or > "best") way. Anyone that says otherwise is selling something. ;) > > imho > > On 9 July 2015 at 08:59, Leigh Wanstead <[email protected]> wrote: > >> Hi Jeremy, >> >> I think that your idea about dropping the INI and transferring the >> settings to a database with a row for each machine that connects is the >> correct way to do that. >> >> Regards >> Leigh >> >> >> On 8 July 2015 at 21:58, Jeremy Coulter <[email protected]> wrote: >> >>> 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 >> > > > _______________________________________________ > 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
