Can UNC path be used as Data Source argument in OLE DB connection string?

[GY2]

I'm having some trouble getting this to work and can't find any reference to
whether or not it's okay. It must be legal I'm betting.

 

[Val Mazur \(MVP\)]

Hi,

What kind of connection are you trying to establish?

 

[Cor Ligthert [MVP]]

GY2,

Depends if it is a database server as a SQL Server or just a kind of file
server as JET (Access) (in the last it is not possible).

I hope this helps,

Cor

 

[GY2]

Thanks for helping. I working with an Ole DB connection to an Access .mdb
file on a network file server.

 

[GY2]

Thanks for the info.

I'm trying to develop a solution which will connect with JET on a network
file server. I would like to have the code 'see' on what machine it is
running and use one data souce when it is on my development machine and
another one (the UNC name) when it is deployed to my users.

 

[Paul Clement]

¤ Thanks for the info.
¤
¤ I'm trying to develop a solution which will connect with JET on a network
¤ file server. I would like to have the code 'see' on what machine it is
¤ running and use one data souce when it is on my development machine and
¤ another one (the UNC name) when it is deployed to my users.

Below is an example connection string:

"Provider=Microsoft.Jet.OLEDB.4.0;Data Source=\\machinename\sharename\folder\file.mdb;"


Paul
~~~~
Microsoft MVP (Visual Basic)

 

[GY2]

So you are saying that I CAN use a UNC path for an Access db? I will try it
and let you know what happens. Thanks a lot.

 

[GY2]

Damn! It works great! And I see that it doesn't matter whether the UNC data
source string is inclosed in quotes or not. Thanks a lot!