asked on

ADO .Requery

I think I know what .Requery does ... it effectively closes and re-opens the table ... and I believe I know when you have to use it.

If 3 consecutive .Seeks fail, you get this bogus ADO error: "Row handles must all be released before new ones can be obtained." Issuing a .Requery before the .Seek makes this problem go away.

I've probably overkilled the problem by issuing a .Requery before every .Seek. I assume there is a performance penalty for this, but have no idea what it is, if anything.

My question: Other than this rather exotic use ... effectively a kludge to avoid a known ADO bug ... what is the purpose of .Requery? Am I paying much for over-using it?

ramani_gr

You could see this and try.

http://support.microsoft.com/default.aspx?scid=kb;EN-US;q257731

Good luck.

ASKER CERTIFIED SOLUTION

barendb

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

GebhartBob

ASKER

barendb---

Thanks for your input.

I know what "a multi-user system on a persistent connection" is, but don't understand what you mean when you say, "Requery is used to get recordset updates". Can you clarify this for me?

barendb

When a user makes changes, it will be written to the database on the server, but the other users on the system will not automatically see these changes. The other users will only see these changes after doing a requery.

Regards
Barend

GebhartBob

ASKER

You learn something new every day. Thanks very much for taking the time to reply.