trying to use windoze UNC in VBA to reach files in share points?

[MLH]

I tried this in a module...

call lineinputthing("\\MLH\Shared Docs\Leads.txt","26MAY08Garages")

The machine name is MLH. The share name is "Shared Docs". The file
name is Leads.txt. But VBA does not understand
\\MLH\Shared Docs\Leads.txt.

The actual location of the share is
C:\Documents and Settings\All Users\Shared Docs\
but windoze does not let you address it directly within a command
window. You can't even cd to Shared Docs from
C:\Documents and Settings\All Users\

You can do dir Shared Docs from C:\Documents and Settings\All Users\
Yes, that'll give you a DIR listing.

The lineinputthing procedure is a sub expecting 2 string arguments.
And the first of them is a text file. The text file is Leads.txt. If
Leads.txt is saved in c:\mystuf\ - then there is no problem at all.
It's just the UNC that I can't seem to get VBA to understand.

How does one refer to share points using UNC or other name convention?
Ideas? Comments?

[Rick Brandt]

MLH wrote:

I tried this in a module...

call lineinputthing("\\MLH\Shared Docs\Leads.txt","26MAY08Garages")

The machine name is MLH. The share name is "Shared Docs". The file
name is Leads.txt. But VBA does not understand
\\MLH\Shared Docs\Leads.txt.

Since you have spaces in the path you probably need to pass a quoted path to
your function...

Chr(34) & "\\MLH\Shared Docs\Leads.txt" & Chr(34)

--
Rick Brandt, Microsoft Access MVP
Email (as appropriate) to...
RBrandt at Hunter dot com

[MLH]

On Mon, 26 May 2008 07:13:51 -0500, "Rick Brandt"
<ri*********@hotmail.comwrote:

>MLH wrote:

>I tried this in a module...

call lineinputthing("\\MLH\Shared Docs\Leads.txt","26MAY08Garages")

The machine name is MLH. The share name is "Shared Docs". The file
name is Leads.txt. But VBA does not understand
\\MLH\Shared Docs\Leads.txt.

Since you have spaces in the path you probably need to pass a quoted path to
your function...

Chr(34) & "\\MLH\Shared Docs\Leads.txt" & Chr(34)

Unfortunately not. No, it produces a 3078 error ...
The Microsoft Jet database engine cannot find the input table or query
'26MAY08Garages"'

Notice that it thinks the table name is 26MAY08Garages" ==with a dbl
quote at the end.

[Rick Brandt]

MLH wrote:

On Mon, 26 May 2008 07:13:51 -0500, "Rick Brandt"
<ri*********@hotmail.comwrote:

>MLH wrote:

>>I tried this in a module...

call lineinputthing("\\MLH\Shared Docs\Leads.txt","26MAY08Garages")

The machine name is MLH. The share name is "Shared Docs". The file
name is Leads.txt. But VBA does not understand
\\MLH\Shared Docs\Leads.txt.

Since you have spaces in the path you probably need to pass a quoted
path to your function...

Chr(34) & "\\MLH\Shared Docs\Leads.txt" & Chr(34)

Unfortunately not. No, it produces a 3078 error ...
The Microsoft Jet database engine cannot find the input table or query
'26MAY08Garages"'

Notice that it thinks the table name is 26MAY08Garages" ==with a dbl
quote at the end.

I fail to see how what I suggested would have any bearing on how your second
argument is interpretted. I only suggested that the first argument be so
wrapped.

--
Rick Brandt, Microsoft Access MVP
Email (as appropriate) to...
RBrandt at Hunter dot com

[MLH]

On Mon, 26 May 2008 08:44:01 -0500, "Rick Brandt"
<ri*********@hotmail.comwrote:

>MLH wrote:

>On Mon, 26 May 2008 07:13:51 -0500, "Rick Brandt"
<ri*********@hotmail.comwrote:

>>MLH wrote:
I tried this in a module...

call lineinputthing("\\MLH\Shared Docs\Leads.txt","26MAY08Garages")

The machine name is MLH. The share name is "Shared Docs". The file
name is Leads.txt. But VBA does not understand
\\MLH\Shared Docs\Leads.txt.

Since you have spaces in the path you probably need to pass a quoted
path to your function...

Chr(34) & "\\MLH\Shared Docs\Leads.txt" & Chr(34)

Unfortunately not. No, it produces a 3078 error ...
The Microsoft Jet database engine cannot find the input table or query
'26MAY08Garages"'

Notice that it thinks the table name is 26MAY08Garages" ==with a dbl
quote at the end.

I fail to see how what I suggested would have any bearing on how your second
argument is interpretted. I only suggested that the first argument be so
wrapped.

Big oops. My fault. Unfortunately the Chr$(34) wrappers didn't
do the trick - applying them as you suggested this time. Line
that failed: Open MyTextDiskFile For Input As #1

Oh well. I tried. Thx, Rick.