Is there something like a connection option "commit_on_close" for ODBC connections?

[reimer_pods]

One of our clients had a program crash while the programm was inserting a bunch of data. Although the programm hadn't run to the point where the commit would have been executed, the data is still there [SA 12.0.1].

So I wonder if there is a connection option triggering a commit it the connection is closed, similar to that option setting in ISQL. I searched the help and checked sa_conn_options, but to no avail. Did I overlook something, or is there another explanation?

[regdomaratzki]

SQL Anywhere shouldn't commit a transaction unless the application tells it to. Have you looked at the transaction log to try and figure out what may have happened?

[Breck_Carter]

If it's a PowerBuilder application the default for CommitOnDisconnect is 'Yes'.

[reimer_pods]

The application has been build with Power++, not PowerBuilder. But the Power++ IDE uses a subset of PowerBuilder 6.5 to create DataWindows and Reports. So there might be a similar property behind the scenes (undocumented).

[reimer_pods]

I don't have access to the log file. But I don't think I could learn much from that: surely there will be a commit, but it's hard to tell where it comes from.

[VolkerBarth]

I'm sure you're running in ODBC's manual-commit mode (and not the default auto-commit mode), right?