I agree with all of the following, that FileMan functions generally need
to be evaluated in a FileMan context. George Timson recently (in the last
year or so) has provided an enhancement to FileMan's Single Data Retriever
that may have a bearing on this discussion. The field argument (the 3rd
OK. Thanks. It would be cool if there was a bridge
(API call), but no big deal if there is not.
Thanks
Kevi
--- Greg Kreis [EMAIL PROTECTED] wrote:
FM functions are, as the name implies, functions in
the FM domain. M
functions, on the other hand, are applicable in the
M domain. So
control codes to printers. ...tx/t
-Original Message-
From: [EMAIL PROTECTED] [mailto:hardhats-
[EMAIL PROTECTED] On Behalf Of Kevin Toppenberg
Sent: Sunday, May 15, 2005 6:31 PM
To: hardhats-members@lists.sourceforge.net
Subject: RE: [Hardhats-members] How to evoke Fileman functions
The FM functions are evaluated and then used to drive the generation of
code, so there isn't an API available. A classic approach would have
APIs and pass the parameters to them, but back in the day, code that
was executed was many times faster than running a routine, if you could
squeeze it
Even now, it's not uncommon to define small frequently used functions as inline in C/C++. It has the same effect (the code is expanded inline at compile time) as an alternative to allocating a new stack frame and going through the whole call/return process. Regardless of whether or not this was
A function can be used almost anywhere. For instance if you wanted to print
numeric date just use the function with date enclosed in ():
Like:
PRINT NUMDATE(TODAY)
Most functions will give you format and use. Probably my two most common
functions are NUMDATE and SETDATA. Then you can make your
But PRINT NUMDATE(TODAY) would crash if I put this
into a M function (i.e. outside Fileman). So I assume
that a M function can not call these Fileman custom
functions. Correct?
I.e, I can't do the following
MyFunct(Param1)
PRINT NUMDATE(Param1)
quit
Kevin
--- Thurman Pedigo [EMAIL
FM functions are, as the name implies, functions in the FM domain. M
functions, on the other hand, are applicable in the M domain. So
forget about using the FM functions in M code or M routines. But, they
are quite handy in print, sort and input templates and in defining
computed fields (all
