Date: Sat, 15 Jan 2000 22:45:30 +0100
From: R.Hoellwarth@t-online.de (Ronald Hoellwarth)
To: pgsql-interfaces@postgresql.org
Subject: Re: [INTERFACES] Forms too complex or to large in pgaccess?
Message-ID: <20000115224529.A20896@beehive.hoellwarth>
Mail-Followup-To: pgsql-interfaces@postgreSQL.org
References: <387F9541.512D18A7@earthlink.net>
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-md5;
	protocol="application/pgp-signature"; boundary="VbJkn9YxBvnuCH5J"
In-Reply-To: <387F9541.512D18A7@earthlink.net>


--VbJkn9YxBvnuCH5J
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable

Am Fri, Jan 14, 2000 at 04:29:37PM -0500 schrieb David Conners:

> ANy help or advise is appreciated.=20

Well, I encountered the same problem and found the following solution.=20
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 =3D 'kz_bind';"
DataControl(.kz.query)::open
DataControl(.kz.query)::updateDataSet
set scriptcode $DataSet(.kz.query,scriptsource)
DataControl(.kz.query)::close
eval $scriptcode

> Thanks,

I hope it could solve the Problem.=20

=2E..

Ahm. While dealing with this Problem I learned that long variable names are
good to read and understand their purpose, but on the other side they need
much of the precious space!! So - "as short as possible but as long as
needed" might get a well to remember sentence.


greetings from Crailsheim, Germany
ronald hoellwarth

--=20
Ronald H=F6llwarth	Registrierter Linux User #132865
<hoellwarth@yahoo.com>	GPG - SchluesselID 0x2F7A041A


--VbJkn9YxBvnuCH5J
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.0d (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE4gOp5UlVI6i96BBoRAeeXAKDTV33vdb0wdIxd5l52f3pqwSaEAwCfYP74
EjWvrw1Yy952T8PKTPS5+4g=
=F50P
-----END PGP SIGNATURE-----

--VbJkn9YxBvnuCH5J--