That definitely won’t work! If it’s a Panorama 6 file, you want to add .pan. All that does is let Panorama X recognize that it is a Panorama 6 file, because Panorama X doesn’t know anything about the old type/creator file codes that were used on the early MacOS systems. So Panorama X does not know what kind of file it is unless it has an extension.
If you set the extension to .pandb, Panorama X will think it is a Panorama X file. However, the internal structure of the file will be all wrong, so it won’t work, as you discovered.
I can’t force it to single user because it is corrupted.
Actually, you can. I think what you need to do is hold down the option key when you force to single user, but it’s been a LONG time so my memory is a bit hazy. But I know it can be done by holding down a modifier key.
these were shared Pan 6 databases
This really makes no difference.
There were some minor changes to the file format from Panorama 1 to Panorama 6, but emphasis on minor. For example, minor changes from 2 to 3, 3 to 4, and 4 to 5. When you opened an older database in a newer version, it would load the database into memory and then make the adjustments needed.
Converting from Panorama 6 to X doesn’t work that way. The Panorama X format is completely different. So instead of making adjustments, Panorama X creates a brand new database. It then picks out the various items of information in the Panorama 6 database and puts them into the new database. But no structure is kept. So if there was some problem with the Panorama 6 database structure, there is no way that those problems could be transferred over to the new database. They could cause the entire process to fail, but there is no way any structure problems in the old database can persist into the new database. It really is exactly the same as if you manually created a new database and then typed in all of the information from the old database. But the typing is automated.
Of course your new database does keep all of the coding in the old database. For example, if DB2 has a .Initialize procedure, that is going to run when you use openfile. Maybe there is something in the .Initialize procedure that is causing a problem.
One thing you could try would be to open DB2 ahead of time, and then use
instead of openfile. By doing that you eliminate all of the extra stuff going on at this point, synchronization, .Initialize, etc. If that works, then we know exactly where the problem is occurring, and can debug further from there.