Hello Neal,
I, for one, purchased and decided to use DXbase because it
allowed me to
modify and update my tables. I never want to rely on the company t
issue an update
to be able to add countries or QSL managers into my database. This
was one of the
most powerful selling points that DXbase had for me. My copy of
DXbase will never
become obsolete, even if I never want to purchase newer releases. I have always
updated to the latest release, but that is because I want to and not
because I have to.
DXbase is a wonderful program and I hate to be locked out of being
able to make my
own table updates. I have used some of Joe's update programs and they
work very well.
I would always like having the choice of running an update or not.
Just my 2 cents worth.
Jim N8JV
At 01:19 PM 10-3-2009, 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 you
>the functionality to modify ref data and those who own a copy of MS Access
>98 (the version that is compatible with the current version of DXBase) can
>do even more creative things with the reference data (add new fields. etc.)
>Thia is a real luxury that no other logging program I am aware offers (since
>most of the data access logic is proprietary or you are never informed what
>system tools you could use to modify things).
>
>As with most things in life, this luxury comes with a cost and a
>responsibility. I am a big believer in making updates an automatic function
>(if you enable the automatic update function in a preference). So, when new
>prefixes, countries, qsl mgrs, program updates, etc.) would be downloaded
>from my server and applied. Hopefully, this sounds good to you! However, the
>only real way to do this without incredible complexity is to backup the old
>data tables, replace them with the new tables then pro grammatically
>re-initialize the new tables. This means that any of you who have manually
>manipulated these tables will lose those changes.
>
>So, what is your feeling about this? How many of you are modifying these
>tables and what is the nature of the changes? How would you feel if we can
>dramatically improve the frequency/turnaround/process of updates at the
>sacrifice of your ability to add new fields, etc (or at a minimum leave it
>to you to figure out how to import that data from the old backup table)?
>
>73
>
>Neal k3nc
>______________________________________________________________
>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
______________________________________________________________
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
