Ed Leafe wrote: > On Mar 12, 2008, at 9:42 AM, David Crooks wrote: > >> I have always thought it was because FoxPro could _not_ tell if you >> made >> any changes to the memo fields. So, they just wrote it to prompt to >> save >> just in case something was done menu builder. > > > I doubt that, since Fox can tell that with other DBF/memo based > tools. I think that this is simply a bug that wasn't serious enough to > fix.
My work on scX brought to light several warts in not just the menu builder but all of the visual tools, including the class designer. Every time a vcx, scx, or mnx is opened, the timestamp changes. In the case of vcx and scx, some records can even be deleted and readded in a different order. All without ever saying 'save'. I guess with the class designer they made it save those types of changes with no prompting, which does a good job of hiding the underlying problem 80% of the time. The report designer doesn't appear to suffer from this - when you open a report and then close it without saving, the report file is no different on disk than it was before. 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 Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/[EMAIL PROTECTED] ** 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.
