Hi Andrew, > This could cause a backward compatibility issue. Under the current > releases of Base the property textdb.allow_full_path defaults to FALSE. > So, only relative paths are supported.
Yes. > Also, under the current releases attempting to set this property to TRUE > yields a 'Access denied' error. you're right - put onto my "to investigate" list. > So, if an absolute path is used in a > newer database and then this is opened by an older version of Base, the > link will fail. No. The "allow_full_path" option is a per-database option, which is persistent. That is, when a HSQLDB is newly created, this option will be set to TRUE by default, which will also be respected when loaded in older versions. However, this leads to a problem the other way 'round: What if an older version, where this property is still FALSE, is opened in a newer version, and the user attempts to link an absolute table? > In fact, not all relative paths are supported when txtdb.allow_full_path > set to false, only those that are in the same directory as the database > or below it. For example - A path of "..\filename.csv" will cause a > silent error. Under WinXP at least, this will cause a new file to be > created with the name "__filename.csv" in the same directory as the > database, and this will be linked to the text table. I don't know what > would happen under other OS's. Interesting, didn't know, too. Also put onto the list. Thanks for playing with the feature, and sharing your findings! Ciao Frank -- - Frank Schönheit, Software Engineer [EMAIL PROTECTED] - - Sun Microsystems http://www.sun.com/staroffice - - OpenOffice.org Database http://dba.openoffice.org - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
