Okay, the problem as stated with a DAO write is just like a text file. Sometimes the buffer is not flushed until the file is closed and the same can be said for using the recordset method of updating/inserting into a database with with any of the database technologies (DAO, DAO ODBC Direct, RDO, or ADO), thus the problem with ADO not seeing it right away, but close that recordset and you should have faster results. Better yet, change from using the recordset methods to either update or insert queries, create a public sub that accepts a string arguement, and executes via the public/global ado connection object and your ado rs refresh/open method should be resolved.

On another note, using VB's find and replace function can convert a project from dao to ado in a manner of an hour or so...


Edit: dilettante beat me to it with the documentation...


Good Luck