cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

Nested datawindows being broken.

Former Member
0 Likes
372

after migrating from 12.5 to 12.6, my users immediately noticed that nested datawindows were pulling out wrong data.

running an odbc debug. I notice that (as you can see in the 2nd screenshot).

the invoiceno in the parent datawindow as retrieved from the database is 2003001526

the invoiceno PASSED from the parent datawindow, to the nested datawindow is 2003001472

ie: the odbc log shows the wrong value is passed to nested datawindow, yet it is the correct value as retrieved from the database.

the parent datawindow has the syntax of

select invoiceno from tblinvoice where jobreferenceno = :as_jobrefno and casefeeno = :al_casefeeno

the nested datawindow has the syntax of

select invoiceno,blah, blah2 from tblinvoiceassign where invoiceno = :al_invoiceno

I've made a test db and test datawindows containing of 2 rows in each table (ie by culling all data except those where related to invoiceno = 2003001526,2003001472), so its reproducible.

anyone has any clues? its affecting all os (win7 , win 8.1 , 32bit or 64 bit). database is sql server 2008 r2

I'm currently reinstalling 12.5 + ebfs.

View Entire Topic
Former Member
0 Likes

in this case, the problem is both the parent window and child datawindow are brand new created  after i noticed the problem in my original application. the screenshots provided are from a custom build bug reproduction application.

invoiceno is not a compute, its the result of select invoiceno from tblinvoice where ...

it is passed to the nested datawindow as a retrieval argument. (both are numbers fields and sql server INT )