Sender: root@swan.prod.itd.earthlink.net
Message-ID: <388337D5.211247B0@earthlink.net>
Date: Mon, 17 Jan 2000 10:40:05 -0500
From: David Conners <davidthewise@earthlink.net>
MIME-Version: 1.0
To: Constantin Teodorescu <teo@flex.ro>
CC: Ronald Hoellwarth <R.Hoellwarth@t-online.de>,
	pgsql-interfaces@postgreSQL.org
Subject: Re: [INTERFACES] Forms too complex or to large in pgaccess?
References: <387F9541.512D18A7@earthlink.net>
	<20000115224529.A20896@beehive.hoellwarth>
	<388178DD.7AC4DA8E@flex.ro>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Thanks for all of your help!

The method described below addresses my dificulties quite handily.

David Conners
======================================================================

Constantin Teodorescu wrote:
> 
> Ronald Hoellwarth wrote:
> >
> > Am Fri, Jan 14, 2000 at 04:29:37PM -0500 schrieb David Conners:
> >
> > > ANy help or advise is appreciated.
> >
> > Well, I encountered the same problem and found the following solution.
> > I create scripts that do some stuff and then use the following code to
> > source the thinggummy.
> >
> > DataControl(.kz.query)::setSQL "SELECT scriptsource FROM pga_scripts where scriptname = 'kz_bind';"
> > DataControl(.kz.query)::open
> > DataControl(.kz.query)::updateDataSet
> > set scriptcode $DataSet(.kz.query,scriptsource)
> > DataControl(.kz.query)::close
> > eval $scriptcode
> >
> 
> As I see, you choose to create scripts containing big code and call them
> in the form source.
> 
> But, instead of finding them as you show us (with datacontrols) , why
> don't you use this simple variant:
> 
> Scripts::execute "kz_bind"
> 
> Starting with version 0.98, PgAccess defines those namespaces (Forms,
> Scripts, ...) that implement the simple commands "Open", "Execute",
> "Design".
> 
> Please check if it works for you and drop me a note!
> 
> Teo
> 
> ************