Normal Topic Mass Update on Engine (Read 1497 times)
obfusc88
Full Member
***
Offline


No personal text

Posts: 194
Joined: Dec 17th, 2005
Mass Update on Engine
Mar 1st, 2018 at 7:02am
Print Post Print Post  
OK, now that I have discovered MUD on Engine, that naturally leads to more possible uses.

Is it possible to use MUD on Engine from the program code?  Maybe by calling a Tree Branch command like switching to Add Mode.  So, I would sort the result set, load the MUD Spec, and run MUD on Engine from the Tree?

Just asking, seems like it should be OK. Would have to test for Error somehow, looking for a Return value from the command.

Thanks for listening.
  
Back to top
 
IP Logged
 
Ray the Reaper
Global Moderator
Members
Lantica Support
*****
Offline


The One & The Only

Posts: 2480
Joined: Aug 20th, 2003
Re: Mass Update on Engine
Reply #1 - Mar 5th, 2018 at 2:56pm
Print Post Print Post  
The Tree Paths are
Code
Select All
"Add Data Menu!Results Commands!Mass Update Engine"
"Search Update Menu!Results Commands!Mass Update Engine" 



Return value from @SelectTreeItem() would just be if it was able to find that tree item or not, nothing beyond that. The tree item will behave exactly as if the user clicked on it on the tree. It will pop up the dialog asking if you want to test syntax, run, or cancel.

-Ray
  

Raymond Yoxall Consulting
ray.yoxall@gmail.com
ryoxall@lantica.com
Sesame Applications, Design and Support
Back to top
IP Logged
 
obfusc88
Full Member
***
Offline


No personal text

Posts: 194
Joined: Dec 17th, 2005
Re: Mass Update on Engine
Reply #2 - Mar 12th, 2018 at 5:39pm
Print Post Print Post  
Again, the MUD on Engine is my new best friend.  MUD that took hours, now only take minutes.  But now that I am using it, I am starting to have some new related questions.  Here is the first one that I found, but don't understand.

Why does this Update Spec fail on the Engine MUD?
Code
Select All
Clear(FormOrder)
Clear(Prefix)
Clear(Period)
FormOrder = @Str(OrderNumber)
 



But this one is OK?
Code
Select All
FormOrder=""
Prefix = ""
Period = ""
FormOrder = @Str(OrderNumber) 



Is it because more than one element can be handled by the Clear() command?  Any other similar commands that will not run on the MUD on Engine?
  
Back to top
 
IP Logged
 
Ray the Reaper
Global Moderator
Members
Lantica Support
*****
Offline


The One & The Only

Posts: 2480
Joined: Aug 20th, 2003
Re: Mass Update on Engine
Reply #3 - Mar 12th, 2018 at 5:47pm
Print Post Print Post  
obfusc88 wrote on Mar 12th, 2018 at 5:39pm:
Is it because more than one element can be handled by the Clear() command?


The reason is right there. Clear takes an Element Reference. The engine does not know about Elements, only fields which are completely different.

-Ray
  

Raymond Yoxall Consulting
ray.yoxall@gmail.com
ryoxall@lantica.com
Sesame Applications, Design and Support
Back to top
IP Logged
 
obfusc88
Full Member
***
Offline


No personal text

Posts: 194
Joined: Dec 17th, 2005
Re: Mass Update on Engine
Reply #4 - Mar 12th, 2018 at 6:08pm
Print Post Print Post  
Thanks for the fine line distinction. 

I understood that we had to use the Element Name vs. the Field Name, but I did not pick up on the fact that it had to be a command that worked with elements only.

Will watch for that in the future.  Thanks again for the help.
  
Back to top
 
IP Logged