Hi Frank,
Section 1.3.1
*
"Store path relative to database"
o
forces the path to the text file to be stored as a relative path
o
Consequently, when moving the database together with the
text file, the database will continue to work when this
option is checked
o
The path is still stored as absolute path when it cannot be
expressed as relative path
+
e.g. 'cause the database document and the linked file
reside on different volumes
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.
Also, under the current releases attempting to set this property to TRUE
yields a 'Access denied' error. 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.
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.
Drew
