bernaert Posted August 6, 2011 Posted August 6, 2011 Hello, I'm starting a new project with ElevateDb. The first grid I'm creating contains 6 test records. When run in windows mode and click a record, the correct record is selected. Running in web mode, when clicking a record, the record pointer goes back to the first record. How comes? The table has a primary key and an index is selected. With kind greetings, Bernaert Dominique 1
Administrators Farshad Mohajeri Posted August 6, 2011 Administrators Posted August 6, 2011 Hello, I'm starting a new project with ElevateDb. The first grid I'm creating contains 6 test records. When run in windows mode and click a record, the correct record is selected. Running in web mode, when clicking a record, the record pointer goes back to the first record. How comes? The table has a primary key and an index is selected. With kind greetings, Bernaert Dominique This issue is known and will be fixed. Issue: ElevateDB doesn't implement DataSet.RecNo which is used by DB Controls in uniGUI.
bernaert Posted August 6, 2011 Author Posted August 6, 2011 This issue is known and will be fixed. Issue: ElevateDB doesn't implement DataSet.RecNo which is used by DB Controls in uniGUI. Just asking, do you have an estimated idea when this would be? Thx, Bernaert Dominique 1
Administrators Farshad Mohajeri Posted August 6, 2011 Administrators Posted August 6, 2011 İt is a high prority issue and I will try to fix asap.
rsanford Posted August 13, 2011 Posted August 13, 2011 Hi Farshad, Using Firebird with Dbexpress/DataSnap. After editing a record calling "ApplyUpdates", the cursor moves to the next record. I'd like to stay on the same record. Not sure if this is routine record handling or may be the "recno" problem. I guess workaround is to use a query w/parameters allowing only a single record for editing. Robert
Administrators Farshad Mohajeri Posted August 13, 2011 Administrators Posted August 13, 2011 No it is not a recno problem. It happens probably because cursor actually moves to next record. It can be easily verified: Try with a standard DBGrid in VCL mode and observe if behavior is the same.
chefdackel Posted August 23, 2011 Posted August 23, 2011 This issue is known and will be fixed. Issue: ElevateDB doesn't implement DataSet.RecNo which is used by DB Controls in uniGUI. Maybe there is a similar error with DBIsam (4.30 Build 6)? Look at the UniGui demo "SQL Demo" in web mode: 1. start the application 2. start a session in webmode 3. select "items" in the Tables-tree 4. click on "execute SQL" and play with the grid --> all runs fine. 5. changed the SQL to "select * from items where ItemNo =2" 6. click on "execute SQL" 7. look at the grid: there are -8- pages. 8. click on the button on the grid-navigator to go the last page 9. look at the grid: page 8/8. 10. clock on the navigator to go 1 page back 11. look at the grid: page 7/8. 12. click on "OrderNo 1253" 13. look at the grid: page 32/8 (!) 14. click on "PartNo 1390" 15. click on "PartNo 3316" --> the wrong record is selected 16. click on other rows: the wrong records are selected Seems only to happen when the property "RequestLive" of DBIsamQuery is set to true. The same issue as shown above with a DBIsamTable and setting an index and a filter to the table. UniGUI is great, big compliment, I was happy for some days..... but am I right when I say that one don't choose ElevateDB/DBIsam when playing with the actual UniGUI version in web mode?
Administrators Farshad Mohajeri Posted August 23, 2011 Administrators Posted August 23, 2011 Maybe there is a similar error with DBIsam (4.30 Build 6)? Look at the UniGui demo "SQL Demo" in web mode: 1. start the application 2. start a session in webmode 3. select "items" in the Tables-tree 4. click on "execute SQL" and play with the grid --> all runs fine. 5. changed the SQL to "select * from items where ItemNo =2" 6. click on "execute SQL" 7. look at the grid: there are -8- pages. 8. click on the button on the grid-navigator to go the last page 9. look at the grid: page 8/8. 10. clock on the navigator to go 1 page back 11. look at the grid: page 7/8. 12. click on "OrderNo 1253" 13. look at the grid: page 32/8 (!) 14. click on "PartNo 1390" 15. click on "PartNo 3316" --> the wrong record is selected 16. click on other rows: the wrong records are selected Seems only to happen when the property "RequestLive" of DBIsamQuery is set to true. The same issue as shown above with a DBIsamTable and setting an index and a filter to the table. UniGUI is great, big compliment, I was happy for some days..... but am I right when I say that one don't choose ElevateDB/DBIsam when playing with the actual UniGUI version in web mode? Tested with DBISAM 4.30 Build 6, and yes, I can reproduce this problem, but I can swear that this problem wasn't existing in previous builds of DBISAM. What is your DBISAM version? Problem is that RecNo is not sequential when a partial result is returned. Anyway, we will get rid of RecNo soon. It is on top of issue list.
chefdackel Posted August 24, 2011 Posted August 24, 2011 Tested with DBISAM 4.30 Build 6, and yes, I can reproduce this problem, but I can swear that this problem wasn't existing in previous builds of DBISAM. What is your DBISAM version? Problem is that RecNo is not sequential when a partial result is returned. Anyway, we will get rid of RecNo soon. It is on top of issue list. It is an issue with DBIsam 4.30 Build6 and also Build7.
Recommended Posts