There is storage allocated for up to 200 declarations. So really, you can,
if you desire, put all your declarations in your startup form and be done
with it.
----- Original Message -----
From: "Lawrence Lustig" <[email protected]>
To: "RBASE-L Mailing List" <[email protected]>
Sent: Tuesday, March 24, 2009 3:35 PM
Subject: [RBASE-L] - RE: 3 Button Pause/Dialog?
<<
I would, as a matter of practice use STDCALL in the forms onBefore, using
the RBase ChkFunc fucntion to qualify if the Declaration has already been
made elsewhere.
My goal is to encapsulate the whole thing inside a Stored Procedure so I
don't have to repeat the STDCALL logic in every form in which I want to
change the width of drop down lists (which, now that I'm beginning to get
used to having the ability, is all of them). So every time my Stored
Procedure is called it does a CHKFUNC and loads the DLL if necessary.
Placing the Stored Procedure call into an assignment is an easy work around
for my problem. Now I can simply put:
SET VAR vJunk = (CALL SetDropdownWidth('ComponentID', WidthInPixels))
in my AFTER START EEP and know that my combo box will drop down with the
width I'm looking for.
Is there any particular reason why STDCALL is more appropriately used in the
forms ON BEFORE START rather than the ON AFTER START EEP?
--
Larry
