Hi Marc

>To your question 1, let me tell you that tableupdate is not even necessary with transactions. If you have an error writing something away _during_ the transaction, you ROLLBACK and your db is in the state before you started the transaction.
>
I assume you mean that as I TABLEUPDATE each view, a failure means that there is no need to try to TABLEUPDATE the other views, so just a TABLEREVERT will suffice.

>To your question 2: I dunno. I've never had a problem, and I've had documents with hundreds of lines to be posted against inventory and A/R. You _are_ talking about an order of magnitude more.
>
I have experienced a failure to update with large volumes. When I reduce the volume the updates succeed. But that is not scientific evidence, merely suspicion. It could simply be a matter of contention that went away when I retried regardless of the volume.

I would prefer not to break the batch up into smaller groups of records because I really want a single Journal Entry for each invoicing process.

Thanks,

Ken