C
cverbiest
Guest
Laura Stern , current-changed probably works as expected when you know that buffers aren't really separate when they point to the same record. Most developers don't read the manual up to the notes :-( The problem is that the procedure find_current.p has no knowledge, and should not have any knowledge, of what the procedures it runs do, they are black boxes. In find_current.p I need a reliable way to test if the customer record is still the same compared to the previous find in the find_current.p procedure. In a multi-window event driven gui application a user will open a customer update window , the values are displayed. She/he will then opens an order entry window, creates an order, the code of that window could fetches the customer record displayed on the first window. The user then returns to the customer update window, makes some changes and saves. The customer update window has no way of telling that the order entry window fetched the customer record. The integer field is a good idea but it requires schema changes to our database and it will fail if there are sql updates. I have added the digest check to our framework.
Continue reading...
Continue reading...