Icon View Thread

The following is the text of the current message along with any replies.
Messages 11 to 14 of 14 total
Thread script conversion: new lines
Wed, Nov 14 2007 3:31 PMPermanent Link

Tim Young [Elevate Software]

Elevate Software, Inc.

Avatar

Email timyoung@elevatesoft.com

Roy,

<< How near to final is the manual? >>

Minus some minor improvements over time, it is complete.

--
Tim Young
Elevate Software
www.elevatesoft.com

Thu, Nov 15 2007 1:44 PMPermanent Link

Roy Lambert

NLH Associates

Team Elevate Team Elevate

Harry

>A put a TEDBscript component on a form, set the SQL text and then did:
>EDBScript.convertsql(3)
>
>http://www.elevatesoft.com/edb1d6_tedbscript_convertsql.htm
>
>After that you can read the changed SQL.text to see the new script syntax.

Just trying this, and reading the manual - it looks like its a run time operation rather than design time. Is that right? If so TIM CAN WE HAVE IT DESIGN TIME PLEASE?

Roy Lambert
Thu, Nov 15 2007 4:58 PMPermanent Link

Tim Young [Elevate Software]

Elevate Software, Inc.

Avatar

Email timyoung@elevatesoft.com

Roy,

<< Just trying this, and reading the manual - it looks like its a run time
operation rather than design time. Is that right? If so TIM CAN WE HAVE IT
DESIGN TIME PLEASE? >>

That would require a bit of a re-design or the addition of a wizard, which
is doable but will have to wait until after the .NET data provider is done.

--
Tim Young
Elevate Software
www.elevatesoft.com

Fri, Nov 16 2007 2:43 AMPermanent Link

Roy Lambert

NLH Associates

Team Elevate Team Elevate

Tim


Just thinking about it I could write my own to allow me to paste some strings into a memo control, use the runtime stuff and then copy and paste into your component.

The reason for design time rather than run time is convert once rather than every time the script is executed (not sure why anyone would want to do that but I'm sure someone will come up with a reason).

Roy Lambert
« Previous PagePage 2 of 2
Jump to Page:  1 2
Image