Hello... I'm using ADO.Commands in VB to perform 2 massive UPDATEs on a 

table, back to back, and I'm seeing this strangeness with access where the 

first set of updates take a bit time to show up... Too much time, because 

the second update, which relies on the results of the first, aren't 

performed properly. Has anyone else seen this, and if so, do you have any 

suggestions for steps to take in Access or ADO to make things a bit more 

transaction-centric?



Many thanks in advance for any help...