Rohit,

Sorry, but this description/explanation/solution makes ABSOLUTELY no sense for the way IBO works.

What data access components do you use? The Subject of your email even suggests you are using IBX, not IBO !!! Please tell us the class name(s) of the "problem" components (as shown in the object inspector) - that is, the dataset, datasource, connection and transaction classes.

What version of IB Objects (look at the Version property of your connection component)?

Regards,
Helen

At 02:53 PM 03-07-01 +1200, you wrote:

>We have been battling this off an on for months - it being seemingly
>random. The problem manifests as stubborn behaviour on the part
>of the IBO where it either gives phantom records or wont write the
>data you give it.
>
>We finally realised today that it appeared random only because
>30second delay fixes it....
>
>Solution - Please put in a "Prepared := false" in onclose or
>afterclose of the table.... otherwise it uses an obsolete statement
>when it is reopened. This happens when you change the
>transaction it is using for instance.
>
>In our case it was using a handle from a tranaction that was no
>longer in use... as the statement was not reprepared after a new
>transaction was assigned to the table. So it was saving the data
>with the old transaction and then committing it with the new one.
>30 second later it would be ok. :-) Yeah I know OATs
>Regards
>
>Rohit
>
>======================================================================
>CFL - Computer Fanatics Ltd. 21 Barry's Point Road, AKL, New Zealand
>PH (649) 489-2280
>FX (649) 489-2290
>email rohit@... or r.gupta@...
>======================================================================
>
>
>
>
>Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/

All for Open and Open for All
InterBase Developer Initiative · http://www.interbase2000.org
_______________________________________________________