Having an issue, could use some experienced help.

i don't but everyone i work with does

Hmm. Well, maybe you can bounce the basics off of someone close by and see if they have any immediate insight?

- I am a designer, and although I am skilled in html/xml/css etc, I am not a programmer
- Just changed over my design / development PC to Windows 7 64-bit / IIS 7 / Localhost
- I have to work on a classic ASP site that connects to a MS Access database
- previously, on Windows XP with IIS 5 /6, All I had to do was create a virtual directory for the site in wwwroot and it was good to go
- Now, I am finding that with the same setup on IIS 7 (virtual directory), all the functionality of the ASP code seems to work fine, but, the one page where there is a connection to a MS Access database, I get an error and no page display.
- Question 1: with IIS7, does the site *have* to be an application in order to have a db connect? I was fine with just virtual directories under XP / IIS 5/6
- Question 2: with IIS 7, does the db connect *HAVE* to be in web.config? The programmer (not here anymore) put it in a file called Connections/Schedule_query.asp .

* Note: I have done a lot of googling on Classic ASP with IIS 7 / 64-bit and found information on changing settings for Application Pools (to 32 bit etc), editing permissions for files and folders, etc in order to get MS Access database connectivity to work. I'm pretty sure I have implented all the neccessary changes, but I'm still getting nowhere. So I am wondering if the problem begins with the virtual folder / application question, or the location / implementation of the connection string.

(Thanks, toots - or whoever can offer any advice)

honestly, i usually buy our systems architect a beer and he sets that up for me