Hi,

>>Other wise what would be the use in making a cursor transactable? when this does not defaults to 5 and should always be set manually.

I mean is by making the cursor transactable U have opened a lot new ways to do in a transaction.
We all use buffering(Then why not provide one?) with/for transactions. AFAIK there are only two ways of creating and using ( no way of using the use command but it happens ?? when create is called) a cursor. (How to USE a cursor without using again ?? whereas tables can be opened with/out the use of again)

1) Create Cursor abcd (f1 I)
2) select - command (readwrite)
both return with buffering 1

Agreed(Infact very happy that the cursors now can be included in transactions) that U have offered the cursor to be transactable when its buffering status is 1in contrast to other table/view/spt cursors where it is 5.

The table/views have an optional use command when done would follow the cursorsetprop properties.
But there is no use command with cursors.

To use cursors it would be the way round like use dbf('').. again... which opens respecting cursorsetproperties.

So

create cursor abcd(abc C(10))
use dbf('abcd') in 0 again alias abcd1


now to make the abcd cursor transactable would require abcd1 to be set to buffering 1
So all those cursors opened again with the use would require buffering 1 (what if they have pending changes as buffering is respected ?)

Otherwise making the cursor transactable first and then to re-USE it would do.
If second is the case then why not make the cursors transactable by default when created ?

I hope U catch my point...

I was not very clear in my earlier statement as I was comunicating over the dialup (from India and had to hurry for my primary profession needs) So what I actually meant was more manual work needs to be done and more code increase inorder to use cursors which could be solved by making the cursors follow the cursorsetproperties. (adding what happens when a Use is issued to create cursor by default.)

Thank You,

Suhas.