Very Computer

> Hi,

> I'm not sure I understand the Fullpath() command, as I get unexpected
> results when trying to use it.  Perhaps it's best to state what I
> need, and explore if Fullpath is the right way to go.

> I have written many small progs in FoxPro2.5a for Windows.  Originally
> for a stand alone machine, they are now accessible over a small (3 pc)
> network in my office.  Originally, most directories were hard coded
> into my apps, but now I would like to run these apps from any of the 3
> pc's on the network.  Since FoxPro2.5 doesn't support the
> \\computername\\drive\\directory\\ naming convention, I am forced to
> use drive letters to designate files.  Dive letter mapping works;
> however, the server's "C:\" drive is mapped as the "G:\" drive on the
> 2 workstations so when the apps are run from the server they
> (accurately)
> look for files on drive "C" but when run on the workstations, they
> NEED to look on drive "G", but of course don't.

> How can I tell my apps "when you're on the workstations, use drive G:"
> ??  Or (probably better) find the exact path of a file in realtime
> relative to the machine requesting it, and call it that way?

> I thought using fullpath would help me determine the path of a file to
> be retrieved, and I could somehow test which machine is running, and
> prepend the respective drive letter, but fullpath has me all turned
> around.  I do not understand the concept or the results I am getting.
> MS documentation on this command is poor.

> What is the purpose of having to specify the second argument in
> fullpath?  If you know the path relative to the first argument, why
> not just use it?  Fullpath keeps returning the name of the file
> specified in argument 1 as being in the directory from argument 2.
> i.e. fullpath("\sometable.dbf", "C:\foxpro\new") returns
> c:\foxpro\new\sometable.dbf when in actuality it is not located in the
> "new" directory, but in the "foxpro" directory.  I don't get it.  It
> just appears to be stringing the two together.  Is this even the way I
> should be approaching my problem?

> Any insight would very helpful.  I have been using FoxPro since 1994,
> but I'm only an intermediate level user.  I have never written stand
> alone apps, but I'm not totally a novice either.  I'm just stuck in
> the middle.

> Thanks,
> Jim

> Hi Steve,

> Thank you for the great suggestions.  I'm glad you cleared up matters
> on fullpath returning the path as if the file were in the default
> directory when it can't be found - that explains some of the results I
> had been getting.

> > I suggest you solve your problem by creating a small table on each
> > machine.  In that table have a field for the drive designation or even a
> > complete path.  Here's an example of how to do it:

> Not a bad idea.  It may require more re-programming than I feel like
> doing at the moment, but it seems thorough.  I'm not sure I like the 3
> separate tables in on 3 separate machines.  I might try one table with
> all the paths combined with the environment variable idea below.  Oh
> well, either way I knew it wouldn't be fun.

> >   CREATE TABLE MyPath ( PathToStuf C(40) )

> > On main machine, MyPath.PathToStuf could be populated with "C:\FOXDATA\"
> > while on the other two machines it would be "G:\FOXDATA\" (or however
> > you name your directories).  Inside the app, instead of

> >   USE c:\foxdata\thisfile

> > you would

> >   USE ( TRIM( MyPath.PathToStuf ) + "thisfile" )

> > we do this and it works very well.  You can just as easily put the path
> > into a PUBLIC memory variable if you prefer.

> > Another approach is to set a DOS environmental variable on each machine,
> > retrieve that value with GETENV(), then use that inside your program in
> > a manner similar to what I've described above.

> This is very close to what I had planned on doing if I found out
> fullpath wasn't going to give me what I wanted -- which it isn't.  I
> haven't thought it completely through, but on the surface it seems
> like it would require a little less programming.

> > FULLPATH("") will return the current drive and directory.  I use this
> > all the time to save the current path, e.g.,

> >   cCurPath = FULLPATH("")

> >   SET DEFAULT TO SomethingNew
> >   DO something in SomethingNew

> >   SET DEFAULT TO &cCurPath

> > If FULLPATH() can find what you're looking for, it will return the path
> > to the file, but if it can't, it will act as if the file you want is in
> > the current drive/directory.  FULLPATH() is, therefore, pretty useless
> > at finding a file unless you're sure it's in the current directory or on
> > the FoxPro search path.   You could always:

> >   IF FILE( FULLPATH( "myfile" ) )
> >       * We know it's really there
> >   ELSE
> >       * It can't be found
> >   ENDIF

> > -=S=-

> Thanks again,

> Jim

> Hi Steve,

> Thank you for the great suggestions.  I'm glad you cleared up matters
> on fullpath returning the path as if the file were in the default
> directory when it can't be found - that explains some of the results I
> had been getting.

> > I suggest you solve your problem by creating a small table on each
> > machine.  In that table have a field for the drive designation or even a
> > complete path.  Here's an example of how to do it:

> Not a bad idea.  It may require more re-programming than I feel like
> doing at the moment, but it seems thorough.  I'm not sure I like the 3
> separate tables in on 3 separate machines.  I might try one table with
> all the paths combined with the environment variable idea below.  Oh
> well, either way I knew it wouldn't be fun.

> >   CREATE TABLE MyPath ( PathToStuf C(40) )

> > On main machine, MyPath.PathToStuf could be populated with "C:\FOXDATA\"
> > while on the other two machines it would be "G:\FOXDATA\" (or however
> > you name your directories).  Inside the app, instead of

> >   USE c:\foxdata\thisfile

> > you would

> >   USE ( TRIM( MyPath.PathToStuf ) + "thisfile" )

> > we do this and it works very well.  You can just as easily put the path
> > into a PUBLIC memory variable if you prefer.

> > Another approach is to set a DOS environmental variable on each machine,
> > retrieve that value with GETENV(), then use that inside your program in
> > a manner similar to what I've described above.

> This is very close to what I had planned on doing if I found out
> fullpath wasn't going to give me what I wanted -- which it isn't.  I
> haven't thought it completely through, but on the surface it seems
> like it would require a little less programming.

> > FULLPATH("") will return the current drive and directory.  I use this
> > all the time to save the current path, e.g.,

> >   cCurPath = FULLPATH("")

> >   SET DEFAULT TO SomethingNew
> >   DO something in SomethingNew

> >   SET DEFAULT TO &cCurPath

> > If FULLPATH() can find what you're looking for, it will return the path
> > to the file, but if it can't, it will act as if the file you want is in
> > the current drive/directory.  FULLPATH() is, therefore, pretty useless
> > at finding a file unless you're sure it's in the current directory or on
> > the FoxPro search path.   You could always:

> >   IF FILE( FULLPATH( "myfile" ) )
> >       * We know it's really there
> >   ELSE
> >       * It can't be found
> >   ENDIF

> > -=S=-

> Thanks again,

> Jim