Hello to everyone,

I am have a problem programming a Relative Path. I have read everything I could get my hands on. So I know it is what I want.
But there are a few questions that I still have.

1. Does this run in the background or do I have to reference it?

2. Do I need (or should I) program it in a Function?

3. Does anyone have a good example of this?
       All the examples I have found are either hard to follow or do
       not explain themselves very well.

(just a side note)
I need this for a Issue-Traking program. Will have around 20 users of the program. The issues that they enter will be saved in SQL Server 2005. This is of course not on a local machine but on a server (named: ServerSQL). When each of the users log into their workstations, the server (ServerSQL) is not pathed with the same drive letter. Some have it as Q:\, some as X:\...etc.
So this is the reason I need to use in the program a Relative Path.

Thanks in advance for your help!




Rgds
John

A relative path has to be relative to something.

The OS maintains a "current directory" (plain-speak term, not a technical term) for each drive. It also maintains a "Current Drive."

If the current drive is C, and the current directory of C is SomeFldr, the a reference to

     .open "SomeSubFldr\A_Text_Fil.txt"

will open

     C:\SomeFldr\SomeSubFldr\A_Text_Fil.txt


VB 6 has a ChDrive method that changes what the current drive is. Having changed drives this way, CurDir can be used to find out what the current folder is, or to change it.

In DOS we used DIR [Enter] to see what the current drive and directory was, as well as to see all the files in that directory.
C:[Enter] was used to make the C drive the current drive. (So this arrangement dates way back into the earliest of DOS’s.)

I’m absolutely certain that .NET has similar functionality, since it reflects back to the underlying File System functionality.

So it looks as if you are going to have to gain some specific knowledge of the specific machine’s configuration to be able to use relative paths (so that you can set the current drive, you see). I think that if you can gain that information, then there is no benefit to using relative paths at all. You would just concatenate the gleaned information with the predetermined path information, and use an absolute path.