Log, transactions and ESQL/C

I have an SE database without transaction log (in fact when i make the query of dirpath on systables i find anything). This supposes that any transaction can't be done. But i have in many ESQL/C programs BEGIN WORK, COMMIT WORK AND ROLLBACK WORK constructs and they work very well! How can it be? Thanx, Guido

Guido Cirilli wrote: > I have an SE database without transaction log (in fact when i make the > query of dirpath on systables i find anything). > This supposes that any transaction can't be done. I agree > > But i have in many ESQL/C programs BEGIN WORK, COMMIT WORK AND ROLLBACK > WORK constructs and they work very well! Double check whether its really working - it's probably not. Are you checking sqlca.sqlcode after *every* SQL statement, including begin work, commit work and rollback work?? If not, suggest you do it. If so, is the sqlcode really 0 after the transaction statement?? > > How can it be? > Thanx, Guido