At 03:26 PM 07-08-01 +0200, you wrote:

>Helen,
>
> > IB Objects actually includes code to reject the incorrect path string (some sub-release versions ago) so this user must have been using a version of Marathon that was compiled before that.
>
>all right, but let me emphasize that the path string is not incorrect,
>it's just a *relative* path string, and as such conforms to the MS-DOS
>specification.

I'm not sure that's correct. I thought the RPA format was .\ and ..\ in MSDOS.

It's immaterial, anyway, as IB never ran on MSDOS. Whatever is "valid" in MSDOS or Windows, none of these formats is a valid format for connecting to IB. Mapped drives are also not valid. The documentation is quite explicit that the path must be the full physical path to the database file. I don't have a problem with that but I do have a problem with the ambiguity being able to pass across the client threshold.

I haven't heard of symbolic links causing this problem on Linux...but I don't think I've heard of corruption on a Linux database either. It would be worthwhile raising on firebird-devel and/or asking Ann (world-expert database-decorrupter) if she has run across it...

-- helen

All for Open and Open for All
InterBase Developer Initiative · http://www.interbase2000.org
_______________________________________________________