rclerk @once

[Scott Walker]

Brian,

According to Laura's Quick Reference Guide for filePro version 5.0 2nd
edition

@ONCE processing does come before @MENU and @UPDATE

She has a great Inquire/Update/Add flowchart showing the order of things
getting executed.

If Laura gives me permission I would be glad to scan it and post it here,
but I would need her permission.

Her Quick Reference Guide is worth is weight in gold.


By the way,  thanks so much for your post about the libtermcap.so.2 you use.
It very much helped me today.



Regards,
Scott Walker
scottwalker1956 at gmail.com



-----Original Message-----
From: Filepro-list
[mailto:filepro-list-bounces+scottwalker1956=gmail.com at lists.celestial.com]
On Behalf Of Brian K. White via Filepro-list
Sent: Thursday, July 20, 2017 3:05 PM
To: filePro Mailing List <filepro-list at lists.celestial.com>
Subject: rclerk @once


5.0.14
Is it clearly described anywhere exactly what order the various @once @menu
@update etc happen?

All these years I have been working on the assumption that I could trust
that no matter what else happens, @once absolutely always happens, and
always happens first.

I use it to initialize variables and rand("-1")

Today I discover that isn't guaranteed after all.

I have a table (someone else wrote) that runs in rclerk, non-interactively
in a cgi.

The table had both @menu and @update, and I just tried add an @once, and
discover that the @once is not being executed.

The @menu contains a "lookup -" followed by pushkey "U"

The bulk of the table is actually all IN the @update

Is it just that @menu or @update or both come before @once?

--
bkw
_______________________________________________
Filepro-list mailing list
Filepro-list at lists.celestial.com
Subscribe/Unsubscribe/Subscription Changes
http://mailman.celestial.com/mailman/listinfo/filepro-list