>Alan
>
>Row buffered is STILL buffered. You need no buffering - 0 - in order to zap- AFAIK
>
>Terry
>
>>In my foundation classes I have a routine that zaps all child-cursors when a new parent record is added. As the child-cursors are usually tablebuffered I issue CURSORSETPROP('BUFFERING',3) so that the ZAP command will work correctly, then set it back to 5 afterwards.
>>
>>There is one particular cursor (a remote view derived from SQL-server backend), that when the ZAP command is issued, brings-up error 1579 "Command cannot be issued on a table with cursors in tablebuffering mode". But I have purposely set the buffering to row-buffered!
>>
>>Has anyone any idea what might be going on here? It occurred to me that there is another cursor in the same DE that is also selected from the same back-end table, but I cannot think how that has anything to do with it - could it?
>>
>>DELETE ALL may be a workaround for now, but I would like to start-off a new record with totally 'clean' child cursors, and would still like to know why ZAP produces an error.
>>
>>Any help would be appreciated.
>>
>>Alan