Neal, et el. There are certainly pros and cons for either view. Auto update as well as being able to manually change the ref data as the need arises. In essence, duality seems to be the route to go. Make it elective for the individual user which I already think you eluded to. Under the options drop down there could be combo buttons that allow you to select partial auto update (such as DXbase.exe ) incremental updates or full updates including all the liquid files that change on a continual basis due to whatever.
Also, could it not be scripted in the release (ref data for instance) to back up the existing data base to a well-known-name in a folder in the DXbase directory ? Once that is accomplished a reminder to re-initialize tables would finalize it. Similar to the non-DXbase import functionality. This may be an oversimplification but it is a suggestion and feedback as requested. I may be viewing this wrong, but it seems logical to me. Joe Neal Campbell wrote: > I can certainly accept that (its supposed to be another form of > communication, not a means to stop it!) > > I want your feedback on:discuss is the reference data. DXBase uses the Jet > database engine (commonly called Access) for data storage. DXBase gives > ______________________________________________________________ Dxbase mailing list Home: http://mailman.qth.net/mailman/listinfo/dxbase Help: http://mailman.qth.net/mmfaq.htm Post: mailto:[email protected] This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html
