maher_samet
Active Member
Hi List,
When we go to SP17.1 from previous SP15.1, we removed the entries in the F98950 table, because the BLOB format has changed to xml.
I create a new grid format. OK. When I go to P98950, find that GF line, hit Delete, this takes a while to do this suppression.
When I looked to jdedebug.log, I saw that JDE tried to delete the GF from UOSEQ=0 to UOSEQ=18020, so 18021 SQL requests are done and that's why suppress is too long.
When I looked to the B9800950, the system read from record having UOSEQ=0, then, get from the BLOB the number of formats (nNumFormats variable), and loops from 1 to nNumFormat (which is equal to 18020) and execute the Delete for that UOSEQ.
Sure that the storing of nNumFormat in the BLOB is bad or something is going wrong.
Has anyone encounter that problem and what is the solution ?
Other thing: on some machines, in any form having a grid, all users can create new formats (tabs), but some cannot remove nor rename the format. Has anyone got that kind of behaviour ?
Maher SAMET
Config: B733.2/SP17.1 on NT4.0/SP6a and SQL7/SP3.
When we go to SP17.1 from previous SP15.1, we removed the entries in the F98950 table, because the BLOB format has changed to xml.
I create a new grid format. OK. When I go to P98950, find that GF line, hit Delete, this takes a while to do this suppression.
When I looked to jdedebug.log, I saw that JDE tried to delete the GF from UOSEQ=0 to UOSEQ=18020, so 18021 SQL requests are done and that's why suppress is too long.
When I looked to the B9800950, the system read from record having UOSEQ=0, then, get from the BLOB the number of formats (nNumFormats variable), and loops from 1 to nNumFormat (which is equal to 18020) and execute the Delete for that UOSEQ.
Sure that the storing of nNumFormat in the BLOB is bad or something is going wrong.
Has anyone encounter that problem and what is the solution ?
Other thing: on some machines, in any form having a grid, all users can create new formats (tabs), but some cannot remove nor rename the format. Has anyone got that kind of behaviour ?
Maher SAMET
Config: B733.2/SP17.1 on NT4.0/SP6a and SQL7/SP3.