<div dir="ltr">Hi Jeremy,<div><br></div><div>In the end, it is your baby :-)</div><div><br></div><div>Regards</div><div>Leigh</div></div><div class="gmail_extra"><br><div class="gmail_quote">On 9 July 2015 at 09:22, Jeremy Coulter <span dir="ltr"><<a href="mailto:jscoulter@gmail.com" target="_blank">jscoulter@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div>a mere 20 years Leigh....so your still a newbie then :-) You are correct, but in this case whilst its not the best solution, it will suffice for now and will only require a function to find the correct folder location and then do a copy and replace as apposed to a rather larger potentially code-breaking changes. But I will definitely be changing the way it works.Its a matter of time- as always<span class="HOEnZb"><font color="#888888"><br><br></font></span></div><span class="HOEnZb"><font color="#888888">Jeremy<br></font></span></div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Jul 9, 2015 at 9:13 AM, Leigh Wanstead <span dir="ltr"><<a href="mailto:leigh.wanstead@gmail.com" target="_blank">leigh.wanstead@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Hi Jeremy,<div><br></div><div>You might be spend time to wondering what is going wrong if you deploy the easiest solution to your customer.</div><div><br></div><div>From my 20 years experience, the "easiest" solution might require lots of more time and energy than better way. </div><div><br></div><div>Just my 2 cents</div><div><br></div><div>Regards</div><span><font color="#888888"><div>Leigh</div></font></span></div><div><div><div class="gmail_extra"><br><div class="gmail_quote">On 9 July 2015 at 09:09, Jeremy Coulter <span dir="ltr"><<a href="mailto:jscoulter@gmail.com" target="_blank">jscoulter@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div>I too think it might be the "better" way too Leigh, but the above ideas are the easiest to implement "now" and I can spend the time later to add it to the database.<span><font color="#888888"><br><br></font></span></div><span><font color="#888888">Jeremy<br></font></span></div><div><div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Jul 9, 2015 at 8:59 AM, Leigh Wanstead <span dir="ltr"><<a href="mailto:leigh.wanstead@gmail.com" target="_blank">leigh.wanstead@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Hi Jeremy,<div><br></div><div>I think that your idea about <span style="font-size:12.8000001907349px">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.</span></div><div><span style="font-size:12.8000001907349px"><br></span></div><div><span style="font-size:12.8000001907349px">Regards</span></div><span><font color="#888888"><div><span style="font-size:12.8000001907349px">Leigh</span></div><div><span style="font-size:12.8000001907349px"><br></span></div></font></span></div><div class="gmail_extra"><br><div class="gmail_quote"><span>On 8 July 2015 at 21:58, Jeremy Coulter <span dir="ltr"><<a href="mailto:jscoulter@gmail.com" target="_blank">jscoulter@gmail.com</a>></span> wrote:<br></span><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div><div dir="ltr">Hi All.<div>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.</div><div>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.</div><div>Anyone know how to go about doing this?</div><div>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.</div><div>The reason I want an ini for each computer is about settings. Not all machines have the same settings etc.</div><div><br></div><div>Thanks, Jeremy</div></div>
<br></div></div><span>_______________________________________________<br>
NZ Borland Developers Group - Delphi mailing list<br>
Post: <a href="mailto:delphi@listserver.123.net.nz" target="_blank">delphi@listserver.123.net.nz</a><br>
Admin: <a href="http://delphi.org.nz/mailman/listinfo/delphi" rel="noreferrer" target="_blank">http://delphi.org.nz/mailman/listinfo/delphi</a><br>
Unsubscribe: send an email to <a href="mailto:delphi-request@listserver.123.net.nz" target="_blank">delphi-request@listserver.123.net.nz</a> with Subject: unsubscribe<br></span></blockquote></div><br></div>
<br>_______________________________________________<br>
NZ Borland Developers Group - Delphi mailing list<br>
Post: <a href="mailto:delphi@listserver.123.net.nz" target="_blank">delphi@listserver.123.net.nz</a><br>
Admin: <a href="http://delphi.org.nz/mailman/listinfo/delphi" rel="noreferrer" target="_blank">http://delphi.org.nz/mailman/listinfo/delphi</a><br>
Unsubscribe: send an email to <a href="mailto:delphi-request@listserver.123.net.nz" target="_blank">delphi-request@listserver.123.net.nz</a> with Subject: unsubscribe<br></blockquote></div><br></div>
</div></div><br>_______________________________________________<br>
NZ Borland Developers Group - Delphi mailing list<br>
Post: <a href="mailto:delphi@listserver.123.net.nz" target="_blank">delphi@listserver.123.net.nz</a><br>
Admin: <a href="http://delphi.org.nz/mailman/listinfo/delphi" rel="noreferrer" target="_blank">http://delphi.org.nz/mailman/listinfo/delphi</a><br>
Unsubscribe: send an email to <a href="mailto:delphi-request@listserver.123.net.nz" target="_blank">delphi-request@listserver.123.net.nz</a> with Subject: unsubscribe<br></blockquote></div><br></div>
</div></div><br>_______________________________________________<br>
NZ Borland Developers Group - Delphi mailing list<br>
Post: <a href="mailto:delphi@listserver.123.net.nz" target="_blank">delphi@listserver.123.net.nz</a><br>
Admin: <a href="http://delphi.org.nz/mailman/listinfo/delphi" rel="noreferrer" target="_blank">http://delphi.org.nz/mailman/listinfo/delphi</a><br>
Unsubscribe: send an email to <a href="mailto:delphi-request@listserver.123.net.nz" target="_blank">delphi-request@listserver.123.net.nz</a> with Subject: unsubscribe<br></blockquote></div><br></div>
</div></div><br>_______________________________________________<br>
NZ Borland Developers Group - Delphi mailing list<br>
Post: <a href="mailto:delphi@listserver.123.net.nz">delphi@listserver.123.net.nz</a><br>
Admin: <a href="http://delphi.org.nz/mailman/listinfo/delphi" rel="noreferrer" target="_blank">http://delphi.org.nz/mailman/listinfo/delphi</a><br>
Unsubscribe: send an email to <a href="mailto:delphi-request@listserver.123.net.nz">delphi-request@listserver.123.net.nz</a> with Subject: unsubscribe<br></blockquote></div><br></div>