Tough problem (after 8 hours research one may say so :) with regard to
SQLrollback.
I add a record in a remote view (optimistic tablebuffering) and do
some editing.
Then I start a manual transaction (SQL-Server).
I check getfldstate(-1). It's all 333443444344etcetera. So it indeed
is recognized as a new record and some fields are updated.
Then I do a tableupdate(). It succeeds.
Then I do SQLrollback.
Then I (again) start a manual transaction.
I check getfldstate(-1). It's all 1111111111etcetera. So it's NO
LONGER recognized as a NEW record!
Then I do a tableupdate(). It SEEMS to succeed.
Then I do SQLcommit().
However, the record is not really committed in SQL-Server.
I've also tried to set the field states to 3/4 with the setfldstate()
function, the 2nd time. However, the function will allow me to set
them to 2, but 3 and 4 are refused.
Who knows what's happening here???
Groeten,
Peter
Groet,
Peter de Valença
Constructive frustration is the breeding ground of genius.
If there’s no willingness to moderate for the sake of good debate, then I have no willingness to debate at all.
Let's develop superb standards that will end the holy wars.
"There are three types of people: Alphas and Betas", said the beta decisively.
If you find this message rude or offensive or stupid, please take a step away from the keyboard and try to think calmly about an eventual a possible alternative explanation of my message.