Since upgrading to IIS 7 I can no longer update Access through my CMS

[Humble]

I have a website with a custom built CMS system from several years ago. It is hosted on godaddy. Recently a friend talked me into upgrading from IIS 6 to IIS 7 so I could use web.config to block some IP addresses. I did the upgrade and all seemed well until I tried using my CMS to add or edit content, and it no longer works.

I get the following error message:


The update gives the following error:

Operation must use an updateable query. (Microsoft JET Database Engine)

I am a bit of a newbie at this so I am hoping someone can give me a quick fix to solve this problem. HELP!

Thanks

[texxs]

Dude this is a big deal. How did you build a custom CMS when you are a newbie. I'm not sure wat language to use to help you? Do you know what ODBC is for instance and that there are different "flavors"?

I don't know the details and I generally hate when people answer questions from people who need help like this but I'm thinking it's time for to make some big changes.

In the short term you should just go back to using IIS6, which in itself is probably going to be a big deal.

I've worked with MS Access a lot in the past and it's far more powerful than most people realize. When it comes to making the data accessible via a web app, you must realize one thing about it though. It's a sales tool used by Microsoft to get you to buy Windows server licenses, SQL server licenses and Visual Studio Licenses. Every step of the way you will encounter roadblocks that are mostly only hurdled by spending more moeny, and then making big changes and learning new skills. I have made web apps using the MS technologies described above in conjunction with MS Access DB's before and they worked great. Then Microsoft would update something, or release a new version of something... It will never, ever stop.

[Humble]

Dude this is a big deal. How did you build a custom CMS when you are a newbie. I'm not sure wat language to use to help you? Do you know what ODBC is for instance and that there are different "flavors"?

I don't know the details and I generally hate when people answer questions from people who need help like this but I'm thinking it's time for to make some big changes.

In the short term you should just go back to using IIS6, which in itself is probably going to be a big deal.

I've worked with MS Access a lot in the past and it's far more powerful than most people realize. When it comes to making the data accessible via a web app, you must realize one thing about it though. It's a sales tool used by Microsoft to get you to buy Windows server licenses, SQL server licenses and Visual Studio Licenses. Every step of the way you will encounter roadblocks that are mostly only hurdled by spending more moeny, and then making big changes and learning new skills. I have made web apps using the MS technologies described above in conjunction with MS Access DB's before and they worked great. Then Microsoft would update something, or release a new version of something... It will never, ever stop.

I didn't build it, I paid someone to build it for me several years ago. The pages are all .asp.

I appreciate the information about the evil Microsoft, but I sincerely need help with what I have. But thank you for responding.

[SteveGerencser]

When you upgraded the server did you change and server names? This usually happens when ownership permissions get changed. Here is a page with more info for you to look through.

http://databases.aspfaq.com/database...ry-errors.html

If you still need help, let me know, I know some pretty top shelf MS Server / IIS guys. But they aren't free.