vbNullChar should be a string that contains a CHR$(0)... Should be fixed by OOo 2.0 release
http://www.openoffice.org/issues/show_bug.cgi?id=42467
I got those values from the current development CVS, so it seems to have already been fixed.
Setting "Option Compatible" appears to primarily set compile time items such as allowing an expanded character set or enabling the vb strings. Setting compatibility mode to true enables the keyword Private to work, which in turn allows Dim to properly declare variables Private as it should. I do not remember off hand if I need to explicitly call CompatibilityMode(True) for RmDir(path$) to change the behavior of RmDir(). Ugggg!
I must admit, however, it is probably not that big of a deal....
The "Option Compatible" sets both the compile bCompatible and runtime bCompatibility flags, while the CompatibleMode() RTL function only sets the runtime. There quite a number of VB compatibility patches related to compile time syntax and Find operations, and runtime RTL functions, filesystem, and string operations. I'm not yet far enough through the step code and RTL to map them all, but I intend to include them all in the final document.
-- -------------------------------------------------------- The Snake Pit - Development www.TheSnakePitDev.com Curtis Clauson [EMAIL PROTECTED] Proprietor
"Any sufficiently over-complicated magic is indistinguishable from technology." -- Llelan D.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
