> >
> > Transactions on an buffered tables? Do tell.
> >
> > Ken
> > You shall know the truth - and the truth shall set you free. (John 8:33)
>
> I'm not sure I understood:) I mean transactions are independant from buffering:
>
>

USE (_samples+'data\customer')
> BEGIN TRANSACTION
> replace ALL region WITH TRIM(region)+'_Updated'
> DELETE FOR country = 'USA'
> SET DELETED OFF
> BROWSE TITLE 'In transaction-deleted' for DELETED()
> BROWSE TITLE 'In transaction-updated' FIELDS region,country
> ROLLBACK
> 
> BROWSE TITLE 'After rollback-deleted' for DELETED()
> BROWSE TITLE 'After rollback-updated' FIELDS region,country
> 
> USE

>
> Cetin Basoz

Cetin

I had no idea that you could do this. I would normally use table buffering as my first "level" of buffering and I would use transactions only when I need to co-ordinate the updates of multiple tables. If one update fails they all fail - that sort of thing. It never occurred to me to try using transactions without buffering. My rating to you.

Ken
You shall know the truth - and the truth shall set you free. (John 8:33)