Through a fiasco today with one of the developers, it has become apparent that we need to address a subtle difference between two similar activities that give very different results. These activities are importing the PowerSDR database (from a previous version, normally) or simply copying the database file from the old directory to the new one.
While copying the file will work in most circumstances, using this method will cause problems when we are forced to change the database design (which we have been in v1.4.5 (compared to v1.4.4). Simply copying the database file may keep the new keyer from working or cause crashing with messages about the database. Some neat technology used to dynamically create missing tables may bail you out in some circumstances, but there is no guarantee that this will work. In the familiar words of N4HY, "Just say no." Importing the database is the only sure-fire way to make sure that previous settings will be preserved -AND- that necessary database design changes have been made. We try to make this process as simple as possible by making this the first thing that comes up on the startup wizard. If you have trouble importing a database from a previous version, please let me know so I can troubleshoot the issue. Thanks. Eric Wachsmann FlexRadio Systems PS. Similar info will be added to the operating manual.

