OSFI and long paths

OSFI and long paths

Post by Peter Kenyo » Fri, 25 Jul 2003 18:10:10



Hi,

Is it possible to use long paths with OSFI?

Eg, I would like to:

OPEN 'DOS:C:/Program Files/Some Directory/' TO FILE.FV

This code works with 8.3 paths but not the example above. Is there any way I
can do this?

Thanks,

Peter

 
 
 

OSFI and long paths

Post by Matthew Hartin » Fri, 25 Jul 2003 22:56:34


How about trying

OPEN 'DOS:C:/Progra~1/Some D~1/' TO FILE.FV

that is the old style of converting long names to 8.3 format.

Matt Harting
Progressive Software Solutions


Quote:> Hi,

> Is it possible to use long paths with OSFI?

> Eg, I would like to:

> OPEN 'DOS:C:/Program Files/Some Directory/' TO FILE.FV

> This code works with 8.3 paths but not the example above. Is there any way
I
> can do this?

> Thanks,

> Peter

---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.500 / Virus Database: 298 - Release Date: 7/10/2003

 
 
 

OSFI and long paths

Post by Mark Brow » Sat, 26 Jul 2003 05:40:59


or

OPEN 'dos:c:/"program files"/"Some Directory"/' to FILE.FV

but the spaces will probably be your biggest problem.

Mark Brown


> How about trying

> OPEN 'DOS:C:/Progra~1/Some D~1/' TO FILE.FV

> that is the old style of converting long names to 8.3 format.

> Matt Harting
> Progressive Software Solutions



> > Hi,

> > Is it possible to use long paths with OSFI?

> > Eg, I would like to:

> > OPEN 'DOS:C:/Program Files/Some Directory/' TO FILE.FV

> > This code works with 8.3 paths but not the example above. Is there any
way
> I
> > can do this?

> > Thanks,

> > Peter

> ---
> Outgoing mail is certified Virus Free.
> Checked by AVG anti-virus system (http://www.grisoft.com).
> Version: 6.0.500 / Virus Database: 298 - Release Date: 7/10/2003

 
 
 

OSFI and long paths

Post by Tony Gravagn » Sat, 26 Jul 2003 07:10:43



> OPEN 'DOS:C:/Progra~1/Some D~1/' TO FILE.FV

>OPEN 'dos:c:/"program files"/"Some Directory"/' to FILE.FV
>but the spaces will probably be your biggest problem.

I'll have to try that syntax Mark.  :)

I was thinking along the lines of what Matt wrote.  A while back I
figured out how to use the 'dir' command to return the full path in
8.3 format.  I wrapped that in a call so that I could do something
like this:
  call GetPath(longpath,shortpath)
Inside that routine it just did an execute "!dir -something ":path,
maybe within a loop.

Sorry I don't remember the code but I hope that helps.
Tony

"The advantage of a bad memory is that one enjoys several times the
same good things for the first time."
- Friedrich (Peachy) Nietzsche

 
 
 

OSFI and long paths

Post by Peter Kenyo » Sat, 26 Jul 2003 14:31:38



Quote:> or

> OPEN 'dos:c:/"program files"/"Some Directory"/' to FILE.FV

> but the spaces will probably be your biggest problem.

> Mark Brown

I tried that, but it doesn't seem to work. Perhaps D3 is not "long-filename
aware". Never mind, I may be able to work around the problem.

Peter

 
 
 

OSFI and long paths

Post by Peter Kenyo » Sat, 26 Jul 2003 14:32:40



Quote:> How about trying

> OPEN 'DOS:C:/Progra~1/Some D~1/' TO FILE.FV

> that is the old style of converting long names to 8.3 format.

Yes, that will probably work 98% of the time. However, this is for an
installer so I would prefer not to assume anything!

Thanks,

Peter

 
 
 

1. Getting Long File Path from short Path / File Name

How would I be able to get the Long Path Name from a Short Path Name (which
typically has a '~' as a part of the file name.

I have a DBF file (created by another program ) which has a field called
'directory' within which is stored the Short Path / file name eg:

                                                c:\abcde\fghikl~1.jpg

I have noticed that in my program, VFP will totally ignore any reference to
file names with the '~' in it, and so in my case will not show these
pictures. References to files without the '~' works just fine.

Any advice?

Thanks a lot in advance!

Don Bovell

2. Espia Image Classes in Reports

3. Storing long path names

4. Sounds like you need to set umask

5. BDE can't open tables in folders with long paths

6. SQL Reference material

7. Long path blowing me out of the water

8. VB and MS Access

9. long time for explain plan(execution path)

10. Optimizer taking too long to determine query path

11. ADO Open and long path enviroment

12. Long path blowing me out of the water