Subject | Re: [ib-support] Re: --* Please Help*--- Database corruption and cannot backup & restore |
---|---|
Author | Woody |
Post date | 2001-08-08T18:56:16Z |
From: "Ivan Prenosil" <prenosil@...>
Sent: Wednesday, August 08, 2001 1:10 PM
or may not be \windows\system32\. It is whatever the last path was that was
set using that drive.
like in the previous example. The only way to tell Windows to use the root
as the relative path is to actually put the slash in after the drive letter.
may or may not be C:. It could just as well be D: or E: or a mapped network
drive.
would consider it fixed unless someone else with more knowledge about the
internals of IB says otherwise.
Woody
Sent: Wednesday, August 08, 2001 1:10 PM
> when you specifyWindows will use whatever the "currrent" directory is for that drive. It may
> C:db.gdb
> Windows will usually use
> C:\windows\system32\db.gdb
or may not be \windows\system32\. It is whatever the last path was that was
set using that drive.
>No, Windows will use the path as relative to it's current setting again just
> when you specify
> D:ibdir\db.gdb
> Windows will usually use
> D:\ibdir\db.gdb
like in the previous example. The only way to tell Windows to use the root
as the relative path is to actually put the slash in after the drive letter.
>Here, Windows will use whatever the current drive selection is. Again, that
> when you specify
> \db.gdb
> Windows will usually use
> C:\db.gdb
may or may not be C:. It could just as well be D: or E: or a mapped network
drive.
>I assume you mean in IB6 and not in previous versions? If that's the case, I
> There is Windows API function GetFullPathName() that can be used
> to do it. And scan of IB-source directory revealed that GetFullPathName()
> is indeed used in "isc_file.c" file.
would consider it fixed unless someone else with more knowledge about the
internals of IB says otherwise.
Woody