By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
424,509 Members | 1,689 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 424,509 IT Pros & Developers. It's quick & easy.

domain name vs public url in connect string

P: n/a
am using win2k adv serv, iis5.0
this works
Driver={Microsoft Access Driver
(*.mdb)};//111.222.333.444/ShareName/PathToDatabase/MyDB.mdb; Uid=;Pwd="
but this does not
Driver={Microsoft Access Driver
(*.mdb)};//domain.name/ShareName/PathToDatabase/MyDB.mdb; Uid=;Pwd="

the share and path somehow need to be different when using domain name vs
public ip, the domain name is ok for web pages, ping, etc
Jul 19 '05 #1
Share this Question
Share on Google+
2 Replies


P: n/a
I'd stay stick with the IP if the IP is reasonably permanent - with the
domain name the machine will need to do occasional DNS lookups - and as
we see from these groups, there are often DNS problems (the SMTP group
is a case study in this, so many questions there are problems with bad
DNS on the server)

of course, having said that, I'd also note that using Access over HTTP
is really not an ideal solution - Access was never built as a database
server.

If you have the budget and in-house skills I'd recommend an immediate
upgrade to SQL Server (or similar network-capable DB server). Whether
you can justify the upgrade or not I can't say from here, but I'd
certainly be looking at a change if I was asked to connect to an Access
DB over HTTP
________________________________________
Atrax. MVP, IIS
http://rtfm.atrax.co.uk/

newsflash : Atrax.Richedit 1.0 now released.
http://rtfm.atrax.co.uk/infinitemonk...trax.RichEdit/

*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!
Jul 19 '05 #2

P: n/a
thanx, for the sql advice this is kinda low volume so maybe mdb will work
but what about the connection string using domain name??
"Atrax" <at***@dontspamatrax.co.uk> wrote in message
news:O0**************@TK2MSFTNGP09.phx.gbl...
I'd stay stick with the IP if the IP is reasonably permanent - with the
domain name the machine will need to do occasional DNS lookups - and as
we see from these groups, there are often DNS problems (the SMTP group
is a case study in this, so many questions there are problems with bad
DNS on the server)

of course, having said that, I'd also note that using Access over HTTP
is really not an ideal solution - Access was never built as a database
server.

If you have the budget and in-house skills I'd recommend an immediate
upgrade to SQL Server (or similar network-capable DB server). Whether
you can justify the upgrade or not I can't say from here, but I'd
certainly be looking at a change if I was asked to connect to an Access
DB over HTTP
________________________________________
Atrax. MVP, IIS
http://rtfm.atrax.co.uk/

newsflash : Atrax.Richedit 1.0 now released.
http://rtfm.atrax.co.uk/infinitemonk...trax.RichEdit/

*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!

Jul 19 '05 #3

This discussion thread is closed

Replies have been disabled for this discussion.