Login ProductsSalesSupportDownloadsAbout |
Home » Technical Support » ElevateDB Technical Support » Support Forums » ElevateDB General » View Thread |
Messages 1 to 4 of 4 total |
Post problem |
Sun, May 22 2011 1:32 AM | Permanent Link |
Bill Z ZED Data Solutions | Hi
Using Version 2.05 Build 6 with Lazarus Version 0.9.30 for Win CE project. Is data committed to the database when the Post method is called? Application compiled for Win CE on previous version of ElevateDB...when run on a PDA, saved the data and would display as required on the various screens. Since the new version of ElevateDb (2.05 Build 6) I have to back out of the application and restart to see the saved data. What has changed?? Thanks in advance |
Mon, May 23 2011 9:23 AM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com | Bill,
<< Using Version 2.05 Build 6 with Lazarus Version 0.9.30 for Win CE project. Is data committed to the database when the Post method is called? >> Yes, absolutely. << Application compiled for Win CE on previous version of ElevateDB...when run on a PDA, saved the data and would display as required on the various screens. Since the new version of ElevateDb (2.05 Build 6) I have to back out of the application and restart to see the saved data. >> Did anything else (Lazarus version, etc.) change in addition to your version of ElevateDB ? If the data is there when you restart the application, then EDB is definitely writing it to the OS and, subsequently, to the "disk". Of course, it should show up in memory right away also. -- Tim Young Elevate Software www.elevatesoft.com |
Mon, May 23 2011 9:05 PM | Permanent Link |
Bill Z ZED Data Solutions | Tim,
>Did anything else (Lazarus version, etc.) change in addition to your version >of ElevateDB ? Yes. Yesterday I noticed that the SessionName property has changed in the datamodule only. Components on other forms still referred to the original SessionName that I had set when I started this project. Original SessionName was 'Snacking'.......seems that since the update (both Lazarus and ElevateDB) it is now 'PDASession_1'. I have now ensured all components (where required) have the same SessionName. Will have a chance to test properly tonight but could this have been the reason? Bill |
Tue, May 24 2011 12:31 PM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com | Bill,
<< Yes. Yesterday I noticed that the SessionName property has changed in the datamodule only. Components on other forms still referred to the original SessionName that I had set when I started this project. Original SessionName was 'Snacking'.......seems that since the update (both Lazarus and ElevateDB) it is now 'PDASession_1'. I have now ensured all components (where required) have the same SessionName. Will have a chance to test properly tonight but could this have been the reason? >> If the dataset components used to read the data were using a different session, then yes, this could have caused the writes to occur as normal, but make it appear to the other session that they weren't there (without an explicit Refresh call). -- Tim Young Elevate Software www.elevatesoft.com |
This web page was last updated on Saturday, April 27, 2024 at 08:52 PM | Privacy PolicySite Map © 2024 Elevate Software, Inc. All Rights Reserved Questions or comments ? E-mail us at info@elevatesoft.com |