Transferdatabase and UNC

Re: Transferdatabas e and UNC

Thanks Rich,
I guess you're right, but it seems odd that Access accepts the UNC as a link
connection but won't in other areas.
Do you know if there's a way to convert the UNC back to a file based format?
Thanks again for your response.

--
Bob Darlington
Brisbane


"Rich P" <rpng123@aol.co mwrote in message
news:1203465884 _10684@news.new sfeeds.com...

>>>

"M:\DataDir\Dat aFile.mdb" works.
but "\\server\DataF ile.mdb" doesn't.
<<
>
Since Access is a file based RDBMS, as opposed to a service based RDBMS
like Orcale, Sql Server...,
>
>
using \\server\DataFi le.mdb won't work. You have to use the file based
format
M:\DataDir\Data File.mdb
>
>
Rich
>
*** Sent via Developersdex http://www.developersdex.com ***

Re: Transferdatabas e and UNC

You are correct of course, but the quote was for illustration purposes only.
I'll take more care next time.

--
Bob Darlington
Brisbane
"Marco Pagliero" <martesi@web.de wrote in message
news:aed6bab2-a719-4041-ac21-570616265c7b@s3 7g2000prg.googl egroups.com...

On 20 Feb., 00:50, "Bob Darlington" <b...@dpcmanAX. com.auwrote:

>I'm trying to copy a table using Transferdatabas e.
>It works fine in my test environment, but on the client's server (Server
>2003), it only works if the destination file is in the full path syntax.
>ie "M:\DataDir\Dat aFile.mdb" works.
>but "\\server\DataF ile.mdb" doesn't. (sorry, I can't get rid of the URL
>formatting)
>I get an error 31541 "Cannot open this file".
>Both client and myself are using Access 2002
>The same UNC is used for all back end connections.
>Is this a known limitation or am I missing something obvious (again)?

>
"M:\DataDir\Dat aFile.mdb" cannot translate to "\\server\DataF ile.mdb".
It could translate to "\\server\Share Name\DataDir\Da taFile.mdb" or
possibly to "\\server\DataD ir\DataFile.mdb "
>
Methink
>
Marco P

Re: Transferdatabas e and UNC

>>
"M:\DataDir\Dat aFile.mdb" works.
but "\\server\DataF ile.mdb" doesn't.
<<

Since Access is a file based RDBMS, as opposed to a service based RDBMS
like Orcale, Sql Server...,


using \\server\DataFi le.mdb won't work. You have to use the file based
format
M:\DataDir\Data File.mdb


Rich

*** Sent via Developersdex http://www.developersdex.com ***

Re: Transferdatabas e and UNC

On 20 Feb., 00:50, "Bob Darlington" <b...@dpcmanAX. com.auwrote:

I'm trying to copy a table using Transferdatabas e.
It works fine in my test environment, but on the client's server (Server
2003), it only works if the destination file is in the full path syntax.
ie "M:\DataDir\Dat aFile.mdb" works.
but "\\server\DataF ile.mdb" doesn't. (sorry, I can't get rid of the URL
formatting)
I get an error 31541 "Cannot open this file".
Both client and myself are using Access 2002
The same UNC is used for all back end connections.
Is this a known limitation or am I missing something obvious (again)?

"M:\DataDir\Dat aFile.mdb" cannot translate to "\\server\DataF ile.mdb".
It could translate to "\\server\Share Name\DataDir\Da taFile.mdb" or
possibly to "\\server\DataD ir\DataFile.mdb "

Methink

Marco P

I'm trying to copy a table using Transferdatabas e.
It works fine in my test environment, but on the client's server (Server
2003), it only works if the destination file is in the full path syntax.
ie "M:\DataDir\Dat aFile.mdb" works.
but "\\server\DataF ile.mdb" doesn't. (sorry, I can't get rid of the URL
formatting)
I get an error 31541 "Cannot open this file".
Both client and myself are using Access 2002
The same UNC is used for all back end connections.
Is this a known limitation or am I missing something obvious (again)?

--
Bob Darlington
Brisbane