From: | David Conners <davidthewise(at)earthlink(dot)net> |
---|---|
To: | Constantin Teodorescu <teo(at)flex(dot)ro> |
Cc: | Ronald Hoellwarth <R(dot)Hoellwarth(at)t-online(dot)de>, pgsql-interfaces(at)postgreSQL(dot)org |
Subject: | Re: [INTERFACES] Forms too complex or to large in pgaccess? |
Date: | 2000-01-17 15:40:05 |
Message-ID: | 388337D5.211247B0@earthlink.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-interfaces |
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
>
> ************
From | Date | Subject | |
---|---|---|---|
Next Message | Pascal Drouilly | 2000-01-17 15:56:20 | subscribe |
Previous Message | Constantin Teodorescu | 2000-01-17 10:25:47 | PgAccess 0.98.3 released - minor changes |