I have been looking at the bug-fixes/changes in the bdbpre and bdbpost of the 6.1c.06.0x portingsets and I think the following is usefull to understand the new [good] functionality Baan has implemented in:

The new dump format can be recognized by looking at the first two lines of the dump file:

2000-11-09 09:27:13.368
#$!pre-dump!$#000100v

The first line is a timestamp and should comply to the format
"0000-00-00 00:00:00.000" (the character '0' stands for a digit).

The second line is a "magic" ("#$!pre-dump!$#") followed by the version number of the dump followed by the options that describe the dump.

- The version number is encoded as a 4 digit decimal number ("0001").

- The separator is encoded as a 2 digit hexadecimal number ("00").

- The last character 'v' stands for 'variable format', as opposed to 'f' which stands for 'fixed format' (-x option).


Example: Problems importing dumps

From the headers of some files I saw that we have 0001fff, meaning ff as the code for the separator code and last f as fixed format export.
A check showed that they were using a different separator on the import from the one used in the export? (a hex ff = decimal 255 = character "|" for iso-8859-1).
As aditional note, notice that Baan always suggests to use the NULL character ("\0") as the separator to avoid problems.


NOTES: Baan has fixed problems with compatibility with previous dumps in 6.1c.06.02!