Hi all, just got my hosting sorted out with Well Thought Out Hosting and everything seems okay so far. However, I can't get my ASP pages to work. They are tied to a MS Acccess database with navigation keys on the page to scroll between records, or in this case pictures. My host supports an ODBC DSN which, forgive the noob question, is different to an OLEDB one? I'm using the connection string as follows in my connections asp document:

<%
' FileName="Connection_odbc_conn_dsn.htm"
' Type="ADO"
' DesigntimeType="ADO"
' HTTP="false"
' Catalog=""
' Schema=""
Dim MM_con17minutes_STRING
MM_con17minutes_STRING = "Provider=Microsoft.Jet.OLEDB.4.0;Data Source=" & Server.MapPath("Source.mdb")
%>

is this what's causing the errors? My database is located in a db folder on the host server, and is called "Source" (don't tell me that's a reserved name). The other pages and images are located in the root folder.

Thanks, Lol

What is the error message you're receiving?

In the mean time, check the permissions on the folder where your access db is. you need to allow write permissions to that folder.

Hi Dan, got it sorted out by using a simple DSN ODBC. I created one through Control Panel and used it in dreamweaver to create recordsets. i then created one called exactly the same through my user panel at my webhost. I think I just belt and braces everythign and it seems to work!

Cheers, Lol

That's cool, I'm glad to hear you got it sorted. I know some hosting companies are weary of letting users set up DSN's and wasn't sure if they would let you, but that's good.

Be careful with DSNs. They are pretty resource-heavy and shouldn't be used on a site that generates an even half-decent amount of traffic.

Your DSNless connection string looks correct in and of itself, but as Dan said it's hard to tell without the error message.

Yeah, I'm just going to mail the host about trying to set up a DSN-less connection. I don't see it being a problem but best to ask first.

Cheers, Lol

It's actually the opposite of what you think.

All hosts "allow" DSNless connections since nothing has to be done on the server end for it. It's just a line of code.

It's a DSN connection that usually causes problems, since not all hosts allow this. I remember back in March/April 2000 when I was trying desperately to figure this stuff out and needed the DSN connection. The only host that could support a DSN connection was Interland.

Mind you, that was over 6 years ago.