It’s not clear to me what you are actually doing. You cannot use File>Import>Import Database to import a Panorama 6 database to Panorama X – the database must already be in Panorama X before this command is used.
The 0.1.025 release notes item you mention surely doesn’t apply to what you are doing. First of all, that would only apply to exporting from Panorama X, and you clearly are not doing that. Also, Panorama 6 also converts carriage returns to vertical tabs when exporting, so this was just a fix to make Panorama X work the same way as Panorama 6 did. In addition to Excel, FileMaker also expects new lines in text files to be represented as vertical tabs, and in fact Panorama (both 6 and X) does also. When importing a text file, Panorama will automatically convert any vertical tabs encountered. So there actually is no way to get a vertical tab into the database via importing.
I don’t know of any situation where line breaks are converted to vertical tabs internally within Panorama. If you can be more specific about what exact steps you are following, perhaps this can be investigated further.
This can be true. In “classic” versions of Mac OS (Mac OS 9 and earlier), the carriage return was used as the line break character. In OS X, linefeed characters are used as the line break character. Panorama X uses carriage returns when possible, but there are some situations where linefeeds get in. If this happens, you can use the lftocr( function to make sure that all line breaks are carriage returns (or the crtolf( function if you would prefer linefeeds). This one line program will make sure all line breaks in the current field are carriage returns.
As I mentioned, I don’t know of any situation where Panorama will generate vertical tabs. However, here is a one line program that will convert all vertical tabs in the current field into carriage returns.