Re: UpdateBatch - taking a while

Thanks.
The user gets that many changes by running an 'autoallocate' feature which allocates people to groups. This may change everyone in one go (or only a few), yet the user needs to be able to accept / reject the proposed solution before being saved to the database.
I'll have to put up with the speed issue, but do you know of any way to display a progress bar during the batch update?
Cheers,
Andrew

"Del M" <Del.Murray@xxxxxxxxxxxxxx> wrote in message news:42d65b1f$1@xxxxxxxxxxxxxxxxxxxxxxxxx
> That's probably not bad for Access. How does the user get 1154 changes into
> the system without being asked if the "want to save" ? Maybe if they app
> forced them to save more often the time wouldn't seem so long. You can check
> the ado recordset to see how many "changed" records are there and force an
> update ever 100 or so records. If done inside a transaction, you would have
> the opportunity to rollback the whole set ..
>
>
.