Porting older localhost IIS web based app to Win7 64-bit

As a prologue, I was basically an Access programmer.
A client has a web-based app backed by an Access DB via IIS using .asp files, which I maintained. The client recently purchased a new box with Win7 64-bit as the OS.
I do not own a Win7 box and really don't know much about 64/32 bit differences and workings.
The original app was installed on a Win XP box several years ago. Then the client moved to a Vista box operating in 32-bit mode. I was successful in porting the app from XP to Vista.
Now I'm attempting to port from Vista box to Win7 box. I was finally able to get "Hello World" to appear via localhost. But when I added the ASP connection string to Hello World, I received an error msg indicating an ADODB Connection error which traced to the fact that the Provider for the DB, Micorsoft.Jet.OLEDB.4.0, cannot be found. And when I try loading the very same file in another browser tab, I get an HTTP 500 error. Yet reloading it in the original tab still shows the Provider error. This really confuses me.

I have set permissions to 'Full Control' for all the files in the wwwroot folder and its subfolder, inventory (containing all that is needed for this app to function), for all entities/groups.

So that leads me to a few questions. Do I need to re-task Win7 to a 32-bit machine? How do I get the Provider to show up in the ODBC setup if Microsoft Office is not installed on the box (and might not be in the foreseeable future)? Does anyone foresee other problems that might crop up during this switchover? (I recognize this is a rather vague question. But hopefully someone has had some experience with this sort of thing and might remember.)

Thanks,
Vic