Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!zaphod.mps.ohio-state.edu!julius.cs.uiuc.edu!apple!bbn.com!eboneste
From: eboneste@bbn.com (Liz Bonesteel)
Newsgroups: comp.databases
Subject: Re: Informix 4GL CONSTRUCT question
Keywords: clarification
Message-ID: <59822@bbn.BBN.COM>
Date: 5 Oct 90 13:28:28 GMT
References: <59771@bbn.BBN.COM> <1990Oct4.141922.5268@informix.com> <1990Oct4.235559.22686@informix.com>
Sender: news@bbn.com
Reply-To: eboneste@BBN.COM (Liz Bonesteel)
Distribution: na
Organization: Bolt Beranek and Newman Inc., Cambridge MA
Lines: 21


Since I've received several (thanks, folks!) responses to this
question, all suggesting the same course of action, I thought I'd try
to be a little more clear in the statement of my problem.

	CONSTRUCT p1query ON (...fields...) FROM (...fields...)
	CONSTRUCT p2query ON (...fields...) FROM (...fields...)

	LET s1 = "SELECT * FROM stattbl WHERE ", p1query CLIPPED, " AND ", 
	    p2query CLIPPED

	PREPARE s_1 FROM s1

This doesn't work.  However, if I define s1 and s2 and prepare the two
queries separately (not helpful for the application, but an
interesting exercise nonetheless), I have no problems.

I've hit "you can't get there from here" problems with this package
before, and I'm beginning to think this is one of them.

Liz