Ken
Active Member
I'm working on a custom program originally created by a consultant. I've gotten complaints from the end user that a Grid on one of the rows won't update. The form that doesn't update is a carbon copy of a form that is updating without a problem.
When I run the debug log I can see why the grid isn't updating, the Update line follows:
UPDATE TESTDTA/F59100EX SET EX@FRID=4190.000000,EXSEQ#=1.750000,...(removed for easier reading)... WHERE ( EX@FRID = 4190.000000 AND EXSEQ# = 0.000000 )
The EXSEQ# is always 0.0000 instead of being the actual value of EXSEQ#, in this case 1.750000.
I've regenerated the index, I've regenerated the table. I've created a duplicate form with the same logic (and the same logic as the form that is working correctly). I've made sure that the SQL packages have been rebuilt. And it still fails.
Is there anyway I can debug Edwards logic to see why it's not picking up the correct number? Or has anyone seen this before?
Thanks!
When I run the debug log I can see why the grid isn't updating, the Update line follows:
UPDATE TESTDTA/F59100EX SET EX@FRID=4190.000000,EXSEQ#=1.750000,...(removed for easier reading)... WHERE ( EX@FRID = 4190.000000 AND EXSEQ# = 0.000000 )
The EXSEQ# is always 0.0000 instead of being the actual value of EXSEQ#, in this case 1.750000.
I've regenerated the index, I've regenerated the table. I've created a duplicate form with the same logic (and the same logic as the form that is working correctly). I've made sure that the SQL packages have been rebuilt. And it still fails.
Is there anyway I can debug Edwards logic to see why it's not picking up the correct number? Or has anyone seen this before?
Thanks!