As Woody said, this may or may not be the problem you are having but juding from the description you gave me, it was the best suited fix. (I would suggest also adding the JET driver as it *should* give you a more descriptive error if this happens in the future)

In any case you dont need a second recordset to execute an insert statement you can do:

conn.open
conn.execute([Your insert statement])


-------------------------
I will only tell you how to do it, not do it for you.
Unless, of course, you want to hire me to do work for you.

^^Thats my signature

A couple of observations:

1 - You might want to verify that your environment is up to date: What version of IIS, what operating system, what version of Access, and what version of the ODBC driver you are using. If you are using a current operating system and IIS, and the Microsoft.Jet.OLEDB.4.0 provider, I am doubtful that your problems have to do with using the same connection to do several database actions.

2 - The issue of the connections remaining open most likely is not due to "re-using" the same connection, but perhaps that you are not using explicitly created connections. If you are passing a connection string in to the recordset.open method you are implicitly creating a connection. Eventually the connection will time out, but if you have a high volumn site it is possible that these timeouts aren't happening quickly enough and you run out of available resources. The Jet database provider and ODBC drivers do not support connection pooling, by the way, so as far as I understand there is not going to be any recycling of the connections.

I advise making sure you are using the Microsoft.Jet.OLEDB.4.0 provider, and then always use an explicit connection that you close when you are done using it.


Woody Z http://www.learntoprogramnow.com

Its unlikely that he does not have the JET 4.0 as this shipped as early as Access 2000 but to verify check that the dll: MSJET40.DLL exists on your system


-------------------------
I will only tell you how to do it, not do it for you.
Unless, of course, you want to hire me to do work for you.

^^Thats my signature

I am not suggesting that Jet 4.0 isn't on the system. I am saying that the connection string should be using the Jet 4.0 provider rather than the ODBC provider. ADO will use whatever driver or provider you specify, assuming it is available. Of course, if it isn't available you'll get an error stating that.

Again... I believe there are other issues at play here, and it is useful to be using the latest provider, and an OleDb provider at that rather than the antique ODBC driver, which should only be used if you have a very specific reason for using. Things have come a long way since then.

Woody Z http://www.learntoprogramnow.com

Anyway...

I have msjet40.dll in the \windows\system32 directory with date of 25/03/2005.
We have Windows Server 2003 Standard edition with all the lates SP, and also SQl Server V8.0

I have removed a page which I created this week, which uses an INSERT after an SELECT. And now everything is working fine again.
Just to be sure I will implement the ideas of you and Woodyz.

Many thx again for the time and effort (both of you!)

Johny