That isn't enough information to really figure out what the problem is. Between IIS and Access there are just too many things that might be going wrong. The first thing I would like to see is the ASP code this person is trying to run.

One possibility is that they are using a recordset.AddNew to create the new record and need to put a recordset.Update to finish the transaction. I know this can trick people because depending on how you use AddNew it may or may not need an Update afterwards. It seems likely to me because it would cause the page to open a transaction for the AddNew and never close it, which I think would cause exactly the problem they report.

Jay

I think you would be surprised just how much of that crud there is. I know a lot of people jumped from doing Access applications to coding ASP VB Script during the Internet boom, without really considering how the platforms are different.

This produced some of the worst code I have ever seen. Code that was both nearly unreadable and performed horribly, running web sites that where tied to various IE extensions and depended on IE HTML bugs to display correctly.

There where several cases where I fixed performance problems in our application by doing nothing but throw out unneccisary temp tables. People too used to using Access's ability to base a query on query would do the same thing in SQL by dumping the result of one query into a temp table then doing a query on the temp table that dumped it's result in another temp table and so on.

I ran across one git that used Word's export to HTML function to do his basic page layout and then hacked up the Word output with bad recordset code to create an intranet application.

Jay