Bill Arnold wrote:
I use a MySQL table that has the structure cKeyField, cKeyValue,
cKeyType when creating the oSettings object. I prefer that
over the INI idea, as it's much easier, imo.
Ditto that, except I use plain VFP tables. Unless the requirement is
to give users text format access to the controls, then why not take
advantage of built-in capabilities?
Bill
Michael J. Babcock, MCP
Bill, yes one of the reasons to use INI files is because they can be
very simply modified using something like Notepad. Also I have one
situation where my app is co-existing with another app whose INI
settings I can make use of.
Paul, tables can be shared as well. But I understand your requirement.
All I can think to say is that it might be good to put a comment at the
top of the .ini files reminding users of the importance of reading the
doc carefully before making any changes, and saving a copy of the .ini
file before changing it so they can fall back.
Bill
Bill, in this case the co-existing app would not be able to access
settings in a Fox table. However the advice about reminding users is
excellent and I will incorporate that in the INI file. Thanks. BTW I
had not thought about comments so I will now modify the class to take
them into account.
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://leafe.com/mailman/listinfo/profox
OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech
** All postings, unless explicitly stated otherwise, are the opinions of the
author, and do not constitute legal or medical advice. This statement is added
to the messages for those lawyers who are too stupid to see the obvious.
