Several years back I have written a home finance software using ZEOS 6.5.1 alpha components. The software worked flawlessly until recently I have updated the ZEOS components to the stable 6.6.5 version. The system compiled correctly without errors and appeared to work ok until I have verified the two relational databases tracking accuracy. Both data tables use RECID field as an index with master table having a unique number while slave table may have several repeatable RECID numbers depending on the number of related records. When scrolling master table downwards the related slave table would show records of RECID+1 and conversely when scrolling upwards it would show RECID+1 effectively making 2 record number offset error.
OK, I admit of not working on programming for several years (and my darn memory is volatile to the extent of losing bad programming habits ...lol) but I didn't make any coding changes and after all relating two data tables is a simple matter. Still scratching my head. Reinstalled old ZEOS 6.5.1. alpha modules and everything is just wonderful. I’m still wandering if the new version needs special coding?
Relational database tables do not track.
Moderators: gto, EgonHugeist
-
mdaems
- Zeos Project Manager
- Posts: 2766
- Joined: 20.09.2005, 15:28
- Location: Brussels, Belgium
- Contact:
Can you repeat this in an easy sample program (including sample database, of course)? It's strange we didn't get a repor on this issue before. Please log it in the bug tracker at http://zeosbugs.firmos.at/
Mark
Mark
Master data table A:
RECID OWNER Field3
1 Smith x
2 Doe x
3 George x
Relational data table B:
RECID CERTNO FININST
1 123456 TDBK
1 234567 TDBK
1 345678 TDBK
2 5432a BM
3 12345q RBC
3 34567q RBC
The above data tables are part of FireBird 2.0 database. The tables are related table "B" datasource table "A" and via RECID field using internal SQL:
select * from B
where RECID = :RECID
The above is an example only. The problem is that when table “A” points to records 1 the Table “B” will be showing records belonging to record 2, and going in reverse when table “A” points to record 3 the table “B” will be showing records 1. This off-set applies to all related records in the table.
Since my first posting I have tried all ZEOS versions starting from alpha release. All release candidate and stable releases DO NOT track. The last version that tracks correctly is ZEOSDBO-6.6.1-beta. I have also tried the various ZEOS releases using different versions of FireBird drivers, no difference noticed.
RECID OWNER Field3
1 Smith x
2 Doe x
3 George x
Relational data table B:
RECID CERTNO FININST
1 123456 TDBK
1 234567 TDBK
1 345678 TDBK
2 5432a BM
3 12345q RBC
3 34567q RBC
The above data tables are part of FireBird 2.0 database. The tables are related table "B" datasource table "A" and via RECID field using internal SQL:
select * from B
where RECID = :RECID
The above is an example only. The problem is that when table “A” points to records 1 the Table “B” will be showing records belonging to record 2, and going in reverse when table “A” points to record 3 the table “B” will be showing records 1. This off-set applies to all related records in the table.
Since my first posting I have tried all ZEOS versions starting from alpha release. All release candidate and stable releases DO NOT track. The last version that tracks correctly is ZEOSDBO-6.6.1-beta. I have also tried the various ZEOS releases using different versions of FireBird drivers, no difference noticed.
-
mdaems
- Zeos Project Manager
- Posts: 2766
- Joined: 20.09.2005, 15:28
- Location: Brussels, Belgium
- Contact:
zygmundg,
Sorry for the delay. I was on holiday.
To reproduce your problem I'll have to sit down, build tables, load data, build a project, ... I can't do this while going through the forum posts.
So, please:
- Build the small project you describe above (I suppose you alreday did).
- Export the tables to a sql script. (I'll test using mysql because I have no fb server running)
- Zip everything together
- Report a bug on zeosbugs.firmos.at, attaching the project.
- Report the link to the bugreport here.
Mark
Sorry for the delay. I was on holiday.
To reproduce your problem I'll have to sit down, build tables, load data, build a project, ... I can't do this while going through the forum posts.
So, please:
- Build the small project you describe above (I suppose you alreday did).
- Export the tables to a sql script. (I'll test using mysql because I have no fb server running)
- Zip everything together
- Report a bug on zeosbugs.firmos.at, attaching the project.
- Report the link to the bugreport here.
Mark