Login ProductsSalesSupportDownloadsAbout |
Home » Technical Support » DBISAM Technical Support » Support Forums » DBISAM General » View Thread |
Messages 11 to 11 of 11 total |
error when using StarTransaction with the clientdataset.ApplyUpdates |
Tue, May 6 2008 10:02 AM | Permanent Link |
Nirlan | exactly.
put: Query1.SessionName: = DM.Database1.SessionName; worked perfectly. Thank you all for help. "Tim Young [Elevate Software]" <timyoung@elevatesoft.com> wrote: Nirlan, << yes, the database and the session are in the datamodule. the query, the clientdataset and provider are in the form. >> That was the cause - the query was probably not being assigned the same SessionName property when AutoSessionName was set to True. << Before commit I want to know what was the last number generated within the transaction (code below), but the query is returning the previous number. >> As Fernando indicated - are you querying the correct table ? Also, is the query component being used assigned to the same session via its SessionName property ? Transactions are separated by session, so a different session wouldn't "see" the new record until after the commit. -- Tim Young Elevate Software www.elevatesoft.com |
« Previous Page | Page 2 of 2 | |
Jump to Page: 1 2 |
This web page was last updated on Tuesday, April 30, 2024 at 03:55 PM | Privacy PolicySite Map © 2024 Elevate Software, Inc. All Rights Reserved Questions or comments ? E-mail us at info@elevatesoft.com |