Hey we've all been tempted to do something like this in a pinch (ok maybe just me and you). In my limited experience this quicky solution tends to cause big headaches as the program gets larger. For example I generally hard code in my databases (instead of using the IDE) so that if it gets deleted by a user I can check for its existence and create a new one if necessary. So I would also have to hard code in the preferences which means my database code and preference code resides in the same place (unless I devise another "clever" solution). Also if you change your preferences you will have to access the database code which is somewhat related to the issue I just raised.
Honestly, it isn't the problems that I *can* think of that would scare me aware from such a "solution" - it's the problems that I *can't* think of that might come along to bite me in the future. ~joe -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jeff Justice Sent: Friday, July 21, 2006 2:24 PM To: REALbasic Network Users Group Subject: Prefs vs. DB I have written an app that uses the built-in database. What are the pros and cons of using this for storage of prefs vs. a prefs file? Jeff J. _______________________________________________ Unsubscribe or switch delivery mode: <http://www.realsoftware.com/support/listmanager/> Search the archives of this list here: <http://support.realsoftware.com/listarchives/lists.html> _______________________________________________ Unsubscribe or switch delivery mode: <http://www.realsoftware.com/support/listmanager/> Search the archives of this list here: <http://support.realsoftware.com/listarchives/lists.html>
