Does anyone happen to know offhand how to stop an ADODB.Command from 

returning control to the code after it SUBMITS the command? I'd like it

to return control once the command has completed instead... (I'm using 

Jet, running 2 massive update commands one after the other... The results 

of the first aren't showing up in time for the second to be processed 

accurately...) I'm guessing it's probably one of the properties, but I'm 

not sure which ... If anyone happens to know which it is before I go 

trying each one, or how else to accomplish this, I'd appreciate the help 

=) .. 



Thanks...

Hi,



Access has this weird problem of not refreshing the data if you have

inserts/updates running in batch one after another.

What we do is once one of the batch update /insert queries complete , we do

a recordset.requery to refresh the data and then resume with the next

command.



hope this helps.



Best Regards



Parag  Phanasgaonkar

Senior Software Engineer



Improvement is a journey,not a destination.



----- Original Message -----

From: "Doug W." <nnnhack@y...>

To: "ActiveX_Data_Objects" <activex_data_objects@p...>

Sent: Thursday, December 13, 2001 8:04 PM

Subject: [activex_data_objects] How to make an ADODB.Command wait to finish

before exiting?





> Does anyone happen to know offhand how to stop an ADODB.Command from

> returning control to the code after it SUBMITS the command? I'd like it

> to return control once the command has completed instead... (I'm using

> Jet, running 2 massive update commands one after the other... The results

> of the first aren't showing up in time for the second to be processed

> accurately...) I'm guessing it's probably one of the properties, but I'm

> not sure which ... If anyone happens to know which it is before I go

> trying each one, or how else to accomplish this, I'd appreciate the help

> =) ..

>

> Thanks...

>




$subst('Email.Unsub').