cati
Active Member
Hi All,
I have a big problem with an application.It runs fine on LocalMachine but on Web the application run in a different mode -> first update on table is ok but the second no
I activated Log on server and I saw that the problem is that all the Operations (Insert - Update) on Db are done after the end of the elaboration. So before the second update there is an if -> if the first update table is OK, so performe second update. But on Web when the First Update is done, there is no commit, so the second update doesn't perform. On Client everythink is ok. Any suggest?
There is some parameter on jas.ini to performe Table IO on cache without commit?
I have a big problem with an application.It runs fine on LocalMachine but on Web the application run in a different mode -> first update on table is ok but the second no
I activated Log on server and I saw that the problem is that all the Operations (Insert - Update) on Db are done after the end of the elaboration. So before the second update there is an if -> if the first update table is OK, so performe second update. But on Web when the First Update is done, there is no commit, so the second update doesn't perform. On Client everythink is ok. Any suggest?
There is some parameter on jas.ini to performe Table IO on cache without commit?
