In a message dated 9/17/99 10:09:14 PM, dereksmi@... writes:

>> I recieved the following error when I tried to demo FB3 for my nephew.
>> 
>> Error: Functions must be defined before using...
>> In file Temp Project at line 87 in MAINACTIONS, Code=129740
>>  FN pGbuild (_HelloWindowWnd)

Maybe I am missing something, but rather than moving FNs (especially PG fns, 
because pg likes to use its own fns), or doing a DEF line, are you sure the 
order of the INCLs could not be more advantageous?  I fixed many of my 
problems by dragging my INCLs around manager.  In other words, put the files 
that use a FN below the incl that has the creation of the fn.  

In this case FN pGbuild is in Runtime.INCL, so drag it up to the top of all 
your includes.  (In fact in my latest effort, I swapped the position of the 
INCLs and FLTRs, putting the filters on top.  Then I threw the runtime in 
with the filters.  I'll see if I get my hand slapped)  FB3 is looking at all 
the fns in all includes and filters but it is not looking ahead and I don't 
think we want to do that, as it requires an extra pass by the compiler and 
that takes time.

If you want the freedom of not worrying about the order of creation then you 
can prototype them.  I have found (in other languages) that this can make for 
a confusing order...maybe just my brain, but I still look above first to find 
a faulty fn that is causing trouble in another fn.  That's when I wish for 
the magic little FN finder in FB II.

Hope this helps,

George