Den er er mystisk

Har du ikke fået en fejl kode

Jooo den fik jeg godt nok - men glemte at notere den ned. Så du får den lige næste gang jeg støder på den.

Fandt lidt på dejanews:

I've seen this when using ODBC (not RDO).  It essentially means that some other statement was opened on that same connection, and the software is too brain-dead to be able to deal with two active statements on the same  connection.  You'll need to either use more than one connection, or make very sure that you "close" your resultsets properly (by setting them to nothing) when you've finished getting the data.

og:

I got the same problem in VB 5 with one RDO connection to SQL 7.0. I can’t create a new RDOQuery with a pending RDOResultset. I solved the problem by
using the MoveLast method on the pending resultset before I move on. This
will ensure your resultset is opulated. Check out the VB5 help file on the CreateQuery method.

Og:

You need to do one of two things, either fully populate the snapshot (by
doing a movelast) before looping through it or get a seperate connection for
the update.

See if this article helps....

http://support.microsoft.com/support/kb/articles/q119/0/23.asp

Jeg håber at du kan få løst dit problem.

- Michael

Vores admin fixede den lige
men den smørre der fortjener sgu point :-))