Bill Arnold wrote:
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.
Paul, I think you said you are writing a class to convert the .ini file
to an object. Sorry for not checking, and if this is not the case,
please ignore this.
Yes, that's right. I was looking for an OO approach so that I could
refer to them like oUserSettings.GetVal("FORMPOS","Top")
My thought would be to convert the .ini file internally to a table
instead of an object (refreshing the stored table at each startup). I'm
a big fan of OOP thinking, so it's not that, but that we have more
native tools to handle relational tables then objects, thus using tables
opens the door to possible uses of that information then may be
available in an object format. While objects are great in runtime
memory, tables have a more generic quality.
Your approach is akin to Malcolm's. As to your comments regarding
native tools and relational tables (and tables having a more generic
quality) etc - I'm not sure - I'd like to give that some more thought.
This is loosely related, but I heard someone mention that saving and
restoring objects using an XML format, would allow objects to span
sessions. Sounds sexy on the surface, but objects that contain object
references (etc) may not offer as much or fare as well as their
relational table counterparts.
I did look at using XML to persist objects (somebody did mention that
idea and referred me to Rick Strahl's wwXML class). However one problem
with Rick's class is that it can only deal with nested objects if the
XML excludes a DTD - and in that case the XML has to be used to populate
an existing object with the correct hierarchy of objects and
properties. You can restore XML to a (not currently existing) object if
the XML includes a DTD but you cannot ceate the XML+DTD *and* deal with
nested objects. IOW you can have your cake *or* you can eat it !
Thanks for your input
Paul
_______________________________________________
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.
