Subject | Re: [IBO] "Failed to post all datasets" error |
---|---|
Author | Helen Borrie |
Post date | 2003-08-26T08:10:34Z |
At 07:09 AM 26/08/2003 +0000, you wrote:
IncludeCachedUpdates: boolean );
Do you perhaps have one or more datasets using CachedUpdates, where
you're forgetting to call ApplyUpdates before trying to commit? AFAICT,
if you call Commit on the transaction without calling Post, and you don't
have CachedUpdates, the transaction will post for you; but not for cached
updates. So, by scrolling off a cached row, you cause Post to occur
(normal behaviour) - hence the Commit works next time without an
exception. As I said - AFAICT....
Helen
>Hi there,It is thrown in the procedure TIB_Transaction.SysPostAll(
>
>I have a strange problem that has just recently popped up.
>
>I have a master/detail form. When I edit a record then click the
>post button on the UpdateBar, nothing happens.
>It remains in edit mode, but reports nothing.
>If I click the Commit button on the TransactionBar, I get the error:
>"Failed to post all datasets" and remains in edit mode.
>
>Now, if I scroll off that record, and scroll back, the dataset is
>now posted, and when I click Commit, all is fine and committed.
>
>Also, If I insert a new record, when I click post, the form goes
>from dssInsert to dssEdit (green to yellow)
>but, like above, if I scroll away, then back, all is posted and I
>can now commit
>
>I have seen that this error is in the IB_Constants.pas file, but
>when I search for "E_Failed_To_Post_Datasets" (the constant) to try
>to locate this so I can try to figure out why this is happening, I
>only find the entries in the international Constants files, but do
>not see this constant anywhere else.
>
>Does anybody know why this may be happaning, or where I can begin to
>figure out why?
>
>This was working only until recently, and I cannot see what I have
>changed, but I obviously have done something.
>
>I'm pulling my hair out about this one, so help would be GREATLY
>appreciated!
IncludeCachedUpdates: boolean );
Do you perhaps have one or more datasets using CachedUpdates, where
you're forgetting to call ApplyUpdates before trying to commit? AFAICT,
if you call Commit on the transaction without calling Post, and you don't
have CachedUpdates, the transaction will post for you; but not for cached
updates. So, by scrolling off a cached row, you cause Post to occur
(normal behaviour) - hence the Commit works next time without an
exception. As I said - AFAICT....
Helen