obfusc88 wrote on Feb 21
st, 2018 at 9:56pm:
Ray - What do you mean by "use Mass Update on Engine"?
Do you mean on a stand alone PC, or on the Server vs. a work station? Something else?
I mean Mass Update on Engine. It was introduced in version 2.0.5 back in 2008. Page 15-16 of the Errata
http://www.lantica.com/Files/errata.pdf Quote:I thought some code would run during Mass Update, even if just to make fields visible, change fonts, etc?
If no code is running, then why would a simple Mass Update take such a long time to process.
No, I just verified this with 2.6.4. Even the universal event(Which pretty much always runs and should never be used unless you are building a game) doesn't run when a Mass Update is running.
It's slow because you are pulling every parent record and it's child records from the Server to the Client machine. The forms still format and display the data. Then the update happens. Then the Parent and it's Child records are sent back to the server, and the next one is passed over. Mass Update on the Engine eliminates a lot of this as it runs on the Sesame server working directly on the database itself which is why you have to use Field names and not Element names when using it. This eliminates having to send every record(and the child records) back and forth from the Server to the Client. So it eliminates the network, child records, element formatting, drawing the record on screen, and probably something else that I can't recall at the moment, so it is much much much faster.
-Ray