> Since the 'updates' are actually changed, real world data, there is no > reason why anyone who wished could click on an 'update' button on the dxbase > website and update that file. Certainly the same information will be in the > base ref. file when the new release hits the streets. > > And it should be smart enough to not touch any changed info the user > entered. In the case of user entered data that would be overwritten a simple > 'choose which one you want to keep' dialog box would suffice. >
sorry, I don't buy it. People at DXB put up an update on Monday, I see that Joe Acure changed his address and added a few new qsl clients on Tuesday morning. How is the new 'update' going to know which is correct without asking me for verification on every single issue. That alone would take more time than it would take to make the addition/correction. As for software should be smart enough not to change data... Just how is it going to know what's changed and what's incorrect? Just go to the WINXP newsgroup or any of the Video card newsgroups to see how that works. Now I wouldn't object to a .txt file of data that the user can add or change as they want. (Which by the way Joe does frequently for those that want/need the info.) And there is one more issue no one has mentioned. Not all reflector readers are using the latest version. Boy could that be a data disaster. Or should the DXB staff put out multiple version dependent files? Just my opinion that one size fits all....rarely does.
