Alastair,
Some where in the back of my mind I seem to remember a discussion
thread that concluded there are flaky happenings involving EEP
and a pop-up menu for a single field.  It was sometthing the RBase
wouldn't properly handle pop-up evaluation if there was an EEP
involved.

-- 
Jim Bentley
American Celiac Society
[EMAIL PROTECTED] - email
(973) 325-8837 voice
(973) 669-8808 Fax


---- "Alastair Burr" <[EMAIL PROTECTED]> wrote:
> Yes, they really are text characters and trace shows them correctly.
> 
> I've just posted a response to some other suggestions but I'm
> ready to hold
> off doing anything rash if you can come up with a solution having
> seen that
> response.
> 
> Perhaps putting the problem into words might clarify it a bit
> more:
> 
> What I am trying to do is make the pop-up menu return fewer
> rows as I am
> getting an error message about lack of memory. No problem, I
> know the reason
> is too many rows being returned.
> 
> So I've written an EEP which creates a variable to use to reduce
> the number
> of rows in the selection. This EEP runs before entry into the
> field. As far
> as I can see this works properly and returns the correct text
> values.
> 
> The menu is popped-up automatically and, judging by the way
> trace shows it,
> after the EEP is run - so the variable from the EEP ought to
> be available
> for use in the pop-up's where clause. At least, I'm assuming
> that it is!!
> 
> However, I'm not getting a menu - just error messages that imply
> that the
> where clause is not being evaluated.
> 
> Hope that helps,
> Regards,
> Alastair.
> 
> 
> ----- Original Message -----
> From: "J. Stephen Wills" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Monday, July 01, 2002 9:36 PM
> Subject: RE: Forms: Pop-Up menu - Where clause variable
> 
> 
> > Before I offer my $0.02, Alastair, may I ask you if these
> are indeed
> single
> > characters w/in the paren's?  Might they be INTEGERS?  Although
> I often
> > store the data as TEXT, I "CAST" it to INT w/INT(.vCharacter),
> at least if
> > it's numeric.  Otherwise, I'd use CHAR(.vCharacter) to get
> its ASCII value
> > and use that.
> >
> > I'm asking you this before I offer my assistance as your answer
> to this
> will
> > help guide my answer to your original Q.
> >
> > Thanks,
> > Steve in Memphis
> >
> > > -----Original Message-----
> > > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On
> > > Behalf Of Alastair Burr
> > > Sent: Monday, July 01, 2002 12:09 PM
> > > To: R:Base ListServer
> > > Subject: Forms: Pop-Up menu - Where clause variable
> > >
> > >
> > > Hi everyone,
> > >
> > > I'm trying to get a pop-up menu to work in a form using
> this syntax in
> the
> > > "where clause" box:
> > >
> > > WHERE Name_Type IN (.vLookUp) ORDER BY Full_Name
> > >
> > > The value of vLookUp is defined as text and has a value
> of:
> > > "(A,B,C)" - the
> > > bit between the double quotes.
> > >
> > > I've tried a number of variations such as "&vLookUp" both
> with and
> without
> > > the brackets.
> > > I've also tried putting the IN in the variable: "IN (A,B,C)"
> and
> > > removing it
> > > from the where clause.
> > >
> > > Nothing I've tried seems to work. Is there some limitation
> on variables
> in
> > > the where clause here? R:Base gives me various error messages
> depending
> on
> > > the syntax but the real problem seems to be that it can't
> evaluate the
> > > variable.
> > >
> > > Thanks in advance for any help or suggestions,
> > > Regards,
> > > Alastair.
> > >
> > >
> > > ----------------------------------
> > > A D B Burr,
> > > St. Albans, UK.
> > > ----------------------------------
> > > [EMAIL PROTECTED]
> > > ----------------------------------
> > >
> > > ================================================
> > > TO SEE MESSAGE POSTING GUIDELINES:
> > > Send a plain text email to [EMAIL PROTECTED]
> > > In the message body, put just two words: INTRO rbase-l
> > > ================================================
> > > TO UNSUBSCRIBE: send a plain text email to [EMAIL PROTECTED]
> > > In the message body, put just two words: UNSUBSCRIBE rbase-l
> > > ================================================
> > > TO SEARCH ARCHIVES:
> > > http://www.mail-archive.com/rbase-l%40sonetmail.com/
> > >
> >
> > ================================================
> > TO SEE MESSAGE POSTING GUIDELINES:
> > Send a plain text email to [EMAIL PROTECTED]
> > In the message body, put just two words: INTRO rbase-l
> > ================================================
> > TO UNSUBSCRIBE: send a plain text email to [EMAIL PROTECTED]
> > In the message body, put just two words: UNSUBSCRIBE rbase-l
> > ================================================
> > TO SEARCH ARCHIVES:
> > http://www.mail-archive.com/rbase-l%40sonetmail.com/
> 
> ================================================
> TO SEE MESSAGE POSTING GUIDELINES:
> Send a plain text email to [EMAIL PROTECTED]
> In the message body, put just two words: INTRO rbase-l
> ================================================
> TO UNSUBSCRIBE: send a plain text email to [EMAIL PROTECTED]
> In the message body, put just two words: UNSUBSCRIBE rbase-l
> ================================================
> TO SEARCH ARCHIVES:
> http://www.mail-archive.com/rbase-l%40sonetmail.com/
>  
================================================
TO SEE MESSAGE POSTING GUIDELINES:
Send a plain text email to [EMAIL PROTECTED]
In the message body, put just two words: INTRO rbase-l
================================================
TO UNSUBSCRIBE: send a plain text email to [EMAIL PROTECTED]
In the message body, put just two words: UNSUBSCRIBE rbase-l
================================================
TO SEARCH ARCHIVES:
http://www.mail-archive.com/rbase-l%40sonetmail.com/

Reply via email to