From: | Constantin Teodorescu <teo(at)flex(dot)ro> |
---|---|
To: | Ronald Hoellwarth <R(dot)Hoellwarth(at)t-online(dot)de> |
Cc: | pgsql-interfaces(at)postgresql(dot)org, David Conners <davidthewise(at)earthlink(dot)net> |
Subject: | Re: [INTERFACES] Forms too complex or to large in pgaccess? |
Date: | 2000-01-16 07:53:01 |
Message-ID: | 388178DD.7AC4DA8E@flex.ro |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-interfaces |
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 | Ronald Hoellwarth | 2000-01-16 11:26:14 | Re: [INTERFACES] Forms too complex or to large in pgaccess? |
Previous Message | Tom Lane | 2000-01-16 05:24:45 | Re: [INTERFACES] Slow down on Import |