No, that isn't how I want it to behave.
What I want is for the statement to default to blanks and the connection to
default to the desired macro chars. Then, when the statement operates it
will resolve to use its own macro values if they are there. If its values
are blank then it will make use of those at the connection level. If the
connection reference does not exist then there will already be an exception
because you cannot prepare without a connection reference.

Jason Wharton
CPS - Mesa AZ
http://www.ibobjects.com

----- Original Message -----
From: "Don Schoeman" <ds@...>
To: <IBObjects@yahoogroups.com>
Sent: Friday, July 20, 2001 5:39 AM
Subject: RE: [IBO] TIB_Script macros


> Hi Jason,
>
> Sorry for me being so irritating, but I'd rather ask many questions and
know
> I'm on the right track than having you or me have to redo stuff later.
>
> 1) To make sure we are thinking along the same lines, I assume that you
want
> me to add the MacroBegin and MacroEnd properties to the TIB_Connection
> component (or one of it's base classes). Then when you connect a
TIB_Script
> component to the TIB_Connection, it must set it's own MacroBegin and
> MacroEnd properties equal to that of the TIB_Connection.
>
> 2) If the above statement is what you want, do you want me to add another
> boolean property to TIB_Script like "ParentMacro" which tell's the control
> to always use the TIB_Connection's macro properties.
>
> 3) If the above statement is also true, the TIB_Connection component will
> have to send a windows message which all the TIB_Script components will
have
> to catch in order to update their own properties.
>
>
> Thanks for all your patience.
>
> -Don
>
>
> -----Original Message-----
> From: Jason Wharton [mailto:jwharton@...]
> Sent: 20 July 2001 12:59
> To: IBObjects@yahoogroups.com
> Subject: Re: [IBO] TIB_Script macros
>
>
> Rather than at the session level I would prefer they be on the connection
> level.
> This should make your job a little easier. Keep in mind this is the
default
> and that the script or statement component will still be able to override
> the default set on the connection.
>
> The reason you put a IsStored function in the stored clause of a property
> declaration is so that you can suppress the default condition from being
> written into the DFM. This not only save on EXE size but it also increases
> form load time.
>
> Being a component developer entails thinking of things from a lot of
> different angles...
>
> Jason Wharton
> CPS - Mesa AZ
> http://www.ibobjects.com
>
>
>
>
>
> Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
>
>