problem accessing mdb via asp/js on new server

Assuming that ConnectionStr defined outside of the function, what does it
contain?

"bill" <bdraucker@dataservicesinc.com> wrote in message
news:3d888727$1@10.1.10.29...
>
> had a web application accessing a .mdb on one server (running 2000) that
works
> fine...set up a new server and moved the .mdb there, reconfigured the DSN,
> but things are dead.
>
> The code where its dying, the Connection.Open statement:
> FUNCTION IsAdministrator()
> DIM Connection
> DIM sqlAdmin, RsAdmin
>
> set Connection = Server.CreateObject("ADODB.Connection")
> Connection.Open ConnectionStr
>
> sqlAdmin = "Select [Client_Name] From [Client] Where " & mClient_num & "
> = [Client_num]"
> set RsAdmin = Connection.Execute(sqlAdmin)
>
> IF RsAdmin("Client_Name") = "ADMIN" THEN
> IsAdministrator = "TRUE"
> ELSE
> IsAdministrator = "FALSE"
> END IF
>
> Connection.Close
> SET Connection = NOTHING
> END FUNCTION
>
> The Error message:
> Error Type:
> Microsoft OLE DB Provider for ODBC Drivers (0x80004005)
> [Microsoft][ODBC Microsoft Access Driver] '(unknown)' is not a valid path.
> Make sure that the path name is spelled correctly and that you are
connected
> to the server on which the file resides.
> /eTRACK/SelectFile.asp, line 109
>
>

the DSN's we are using for the Web Page are all defined on the Web Server.
some of the .mdb's are on that machine, a couple are on another server, and
are accessed via the logical drive mappings (in the case of the working version,
on server #1)...a logical drive and DSN was created to point to server #8,
and the .mdb from #1 was copied and put out on #8...the web pages that successfully
access the .mdb on #1 now gives the message we see below.
Note: we had this problem initially whe n we upgraded from NT to 2000...none
of the "links" worked...one of my "illustrious" collegues (the NA)must have
fiddled until he got it to work, but failed to document (or remember) what
magic he performmed (imagine that!).
I initially set up the web pages & DSN's (back on NT) but have no experience
on 2000...and of course, things are somewhat different.
"Larry Triezenberg" <ltriezenberg@pathsys.com> wrote:
>Is that DSN defined correctly on your new server?
>
>"bill" <bdraucker@dataservicesinc.com> wrote in message
>news:3d8890ef@10.1.10.29...
>>
>> ConnectionStr is defined in a common.asp file ("included" statement in
>this
>> program file)that contains the "pointer" to the DSN name signifying the
>..mdb
>> db
>>
>> "Larry Triezenberg" <ltriezenberg@pathsys.com> wrote:
>> >Assuming that ConnectionStr defined outside of the function, what does
it
>> >contain?
>> >
>> >"bill" <bdraucker@dataservicesinc.com> wrote in message
>> >news:3d888727$1@10.1.10.29...
>> >> Microsoft OLE DB Provider for ODBC Drivers (0x80004005)
>> >> [Microsoft][ODBC Microsoft Access Driver] '(unknown)' is not a valid
>path.
>> >> Make sure that the path name is spelled correctly and that you are
>> >connected
>> >> to the server on which the file resides.
>> >> /eTRACK/SelectFile.asp, line 109
>
>

I have compared the setting between #1 & #8 from the volume level thru the
directory level to the file level and all settings are the same...volumes
are sharable..permissions set to full cotrol for everyone.

"Larry Triezenberg" <ltriezenberg@pathsys.com> wrote:
>Permissions on #8?
>
>"bill" <bdraucker@dataservicesinc.com> wrote in message
>news:3d88ac6c$1@10.1.10.29...
>>
>> the DSN's we are using for the Web Page are all defined on the Web Server.
>> some of the .mdb's are on that machine, a couple are on another server,
>and
>> are accessed via the logical drive mappings (in the case of the working
>version,
>> on server #1)...a logical drive and DSN was created to point to server
#8,
>> and the .mdb from #1 was copied and put out on #8...the web pages that
>successfully
>> access the .mdb on #1 now gives the message we see below.
>> Note: we had this problem initially whe n we upgraded from NT to
>2000...none
>> of the "links" worked...one of my "illustrious" collegues (the NA)must
>have
>> fiddled until he got it to work, but failed to document (or remember)
what
>> magic he performmed (imagine that!).
>> I initially set up the web pages & DSN's (back on NT) but have no
>experience
>> on 2000...and of course, things are somewhat different.
>
>