I have problems with the driver and ODBCExpress (a Delphi
package to handle ODBC drivers without BDE). I use OEDataSet,
a component from the package with C++Builder.
Sometimes the component shows other field values than the
driver know. One example:
There is a result set showed to the user. The user changes a
record, then the component try to post it to the server. The
server throws an exception, so nothing have done on the server.
The user sees the wrong data. It's OK, he might correct the
error. Then he cancels the edit, so the component should
refresh the field values from the driver. But after refresh
we can see the wrong data, not the original! Manual refresh
won't help.
When I turn the component level caching, the problem disappeared.
So the promlem lies in the communication between the driver and
the component. I posted the problem to the ODBCExpress list, but
they insist the bug shuld be in the driver. I don't know. I
think the driver is quite good :-) I have no source for
ODBCExpress and I don't know the ODBC API. The component caching
is a good workaround, but what if I can't afford the cache?
Have you any comments? Could this problem related to ODBC API
level or any other mysterious levels?
Regards,
Tibor Laszlo
ltibor@mail.tiszanet.hu
