Eric et. al. As a matter of practice (now that I have had a few DBs disintegrate), I normally make a backup copy of the DB before importing it into a new version of PowerSDR. I have recently gotten into the practice of letting new versions make their own shiny new default DBs that have all of the new wiz bang "recommended" default settings. It seems to make things work a little better (less quirky?).
I don't mind going through and resetting the program settings to the way I like them (and to see if mine conflict with the "recommended" default settings). Re-running the calibration routines and setting up CAT and VAC are not too troublesome. As an added bonus it provides me with some sense of added comfort knowing that things are properly calibrated. What is troublesome is that there are two tables from the old DB that I always have to replace into the new DB with Access - BandText and TxProfile. I have made extensive additions to both tables. These are a pain to reproduce manually so I just do the cut-n-paste thing from the old DB into the new one. I can see were Memory and BandStack might want to be preserved as well. I was wondering if there could be a more granular DB import routine that would allow you to copy specific tables from an old DB into the new default DB as long as the data structures didn't change? I'd think you would have to keep track of the table structure changes with some sort of sequence number (another table?), but it seems like a doable thing. I am fortunate to have Access so I can do DB surgery, but I suspect a lot of folks who don't or are not comfortable with performing a DB frontal lobotomy. -Tim --- Tim Ellison <mailto:[EMAIL PROTECTED]> Integrated Technical Services <http://www.itsco.com/> Apex, NC USA 919.674.0044 Ext. 25 / 919.674.0045 (FAX) 919.215.6375 - cell Skype: kg4rzy
