On a related topic, which might be useful here: seems like I’ve always had problems with the special characters Tab and CR in Panorama. On the one hand, it was very convenient to be able to have them embedded into the data, and view that data occasionally in the Data Sheet. The more that I needed to manipulate that data, though, the more problematic it became - particularly when working with arrays. For one, it was tough sometimes to get a quick look at the data in the datasheet, since vertical tabs, horizontal tabs and space runs all look the same. Hidden CRs were also a problem with exports, etc.
In Pan6 I became accustomed to doing virtually all my data manipulation by exporting data into an array first, then working on it for either display or re-import - very powerful, and useful when formatting for lists, matrices and other databases.
Exportline(, ArrayBuild and ArrayFilter and other
array( functions did most of the work. Since I was doing this a lot, I started converting the data before storing in the cell. The character conversion scheme that worked best, for problems with embedded CRs and tabs, was to simply substitute the literal quoted character for the special characters recognized by Panorama. This works as well as any others I’ve seen, with the added bonus of making the text easy to read in the cell. In fact, I wish Panorama could do this automatically, as it makes exports and arrays much easier to handle. Converting text to store in cells would look like this:
I was doing this at the end of most procedures. Databases with text formatted this way can have data imported, exported and otherwise manipulated all day long without a hiccup.
Exportline( works great, as do all the array/build/filter( functions. The text can be restored to it’s original format using the same function, with the parameters inverted:
(for display, or to handle a field like a table in a relational flat file scheme). When used without the quotes, Panorama sees them as tabs or carriage returns. Most of the time, though, you can do everything using the quoted literal separator characters
In your case, bringing in the data through conversion from Pan6 to PanX, then importing into your updated database, sounds like the most reliable solution. However, embedded Tabs & CRs will always be problematic, just waiting to pounce on some innocent exporter, so a dependable conversion protocol might come in handy someday.