CISAM and incomplete transaction caused by system crashes

When using isbegin() and iscomit() to bracket transaction it is not clear from the manual what happens if the system should crash before the call to iscommit(). Is isrecover() smart enough to recognise that there is an uncompleted transaction. Or more likely is it the case that the transaction isn't logged until it is completed? I assume that this *is* handled correctly but I have been burned before by assuming that other people's programs do the sensible thing. (Mine alway do, of course! :-). Thanks, Russell. -- Russell Fulton, Computer Center, University of Auckland, New Zealand. <rj_fulton@aukuni.ac.nz>