heya
I am helping my brother transfer files from an old PC to a new one. He is also upgrading from LogbookPro v1.5 to v 1.9.4. Unfortunately, it would seem that the new version of LBP cannot adequately import the old files - it is completely corrupted after importing.
-I made a backup of his database in version 1.5
-I restored this backup into version 1.9.4
-it only offers to upgrade the database and put in new features
-when we open the new database file, nothing is where it should be
...............one thing, he has some custom fields that he has defined. Will these extra fields screw up the import?
so........
I tried to do an import of a CSV file, which worked better but still with a few problems.
One thing I do not understand. You have this great export feature in v1.5, and there seems to be no export feature in v1.9.4? The help files in v1.9.4 even reference an export feature.
What gives? Why is this no longer offered as a feature? I really needed this feature to get even halfway there going from v1.5 to v1.9.4 - what do I do for the future?
-upon doing an import of the CSV file, most everything could be matched up, and successfully imported, save for one thing....the approaches.
in my text file, I have several fields of approaches, but I am not offered the appropriate fields to match them up to on an import into v1.9.4
do I need to set up something like a template?
If the database import is not working and the restore from backup feature is not working, what do I do.
Thanks in advance
cggatlin
I am helping my brother transfer files from an old PC to a new one. He is also upgrading from LogbookPro v1.5 to v 1.9.4. Unfortunately, it would seem that the new version of LBP cannot adequately import the old files - it is completely corrupted after importing.
-I made a backup of his database in version 1.5
-I restored this backup into version 1.9.4
-it only offers to upgrade the database and put in new features
-when we open the new database file, nothing is where it should be
...............one thing, he has some custom fields that he has defined. Will these extra fields screw up the import?
so........
I tried to do an import of a CSV file, which worked better but still with a few problems.
One thing I do not understand. You have this great export feature in v1.5, and there seems to be no export feature in v1.9.4? The help files in v1.9.4 even reference an export feature.
What gives? Why is this no longer offered as a feature? I really needed this feature to get even halfway there going from v1.5 to v1.9.4 - what do I do for the future?
-upon doing an import of the CSV file, most everything could be matched up, and successfully imported, save for one thing....the approaches.
in my text file, I have several fields of approaches, but I am not offered the appropriate fields to match them up to on an import into v1.9.4
do I need to set up something like a template?
If the database import is not working and the restore from backup feature is not working, what do I do.
Thanks in advance
cggatlin