I think you're missing the fact that UNC requires a share on the computer 
that will host your fileDSN.  When refering to a file that exists within a 
share, the UNC path would look something 
like: "\\ServerName\ShareName\path\file.dsn"


Use the ODBC manager to create the fileDSN and store it anywhere on your 
local computer.

Create a share on the server to host your fileDSNs.

Move the file you created locally to somewhere on the share and then refer 
to the server/share/file path in your ASP code using the UNC convention 
shown above.


Have you considered a DSN-less connection to your datasource?  With a DSN-
less connection, you can establish a connection within your ASP code 
directly and not worry about share and file availability (yes, share 
security will be an issue).

It's common practice to establish a DSN-less connection in your global.asa 
and store the connection object as an application variable.  There are 
caveats and acceptions to that as well, but it may be a better solution 
for you to consider.

good luck!
jim@m...


wil> I'm using PWS for development in interdev.
> I'd like to follow the advice to use UNC so that when I go to
> the remote web server, the fileDSN will work. However, I can't even
> get it working for localhost. When I try to create a fileDSN, I am
> required to browse to a file and the result is a full path.
> What is it I'm misunderstanding about UNC. I have no problems with