ASP Database considerations

[MicahCarrick]

I'm new to ASP and databases, however, I'm experienced with HTML and VB. I've built a website for my friends which is similar to friendster.com or myspace.com. Creates profiles, bulletin, chat, calander, login, etc. I read a little about the databases and chose not to use ODBC with a DSN as I read it would be faster to use a connection string.

I am using code like...

Set DB = Server.CreateObject ("ADODB.Connection")
DB.Open ("Provider=Microsoft.Jet.OLEDB.4.0; DATA SOURCE=" + server.mappath(fName))


Everything was going fine until I woke up one morning and none of my pages can access the database. I copied all files to my hard drive and it works fine. I copied all files to a friends host, works fine, but my hosting seems to not support it all of the sudden.

In looking for support I found my host does not offer support unless you are using ODBC. They really are pushing that. I can't change hosts as this one was donated to me a pre-paid a year in advance...

Here's my question...

What is the ideal database connectivity to use (access DB) with consideration on speed/performance and error handling? It's all very confusing... ODBC, OLE DB, DAO, ADO, etc.

Thank you for your time.

[blindlizard]

I can't imagine that your host can stop you from using a DNS-less connection because all a DNS connection does is add a new layer that in the end just become a connection string. When the request for the connection is made like Conn.Open "DNSNAME" <--the call goes to the connection manager of the OS which returns a connection string.

What sounds like is happening is that your database may be int he wrong folder on your host. The folder you have the database in may not allow read/write access which is causing the error. Look into the error message you are getting back with using that connection string.