Thanks fellows. I should have used R:DCC. I seldom have any problems (Dream team is excellent) so I thought it was my code not being "tight" enough. I know RBASE is constantly tightening the code.
James Belisle Making Information Systems People Friendly Since 1990 -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Dan Goldberg Sent: Wednesday, October 07, 2015 9:18 AM To: Jim Belisle Subject: [RBASE-L] - RE: On key press change Me three. Coming soon dan -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Kramer, Jason J Sent: Wednesday, October 07, 2015 7:17 AM To: Dan Goldberg Subject: [RBASE-L] - RE: On key press change I reported a similar situation to R:DCC and received a private update that fixed my issue, so (and I defer to the R:DCC team here), I think that your problem will be resolved with the next update. Thanks, Jason Jason Kramer University Archives and Records Management 002 Pearson Hall (302) 831 - 3127 (voice) (302) 831 - 6903 (fax) -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Jim Belisle Sent: Wednesday, October 07, 2015 10:13 AM To: Kramer, Jason J Subject: [RBASE-L] - On key press change We installed the most recent RBASE 95 64 version within the last couple of weeks. Since then my on key press forms are not working quite like they were before. In one form, I use a variable radio group (vmchoice) to have the user choose which field the code will look at. Then I use a var edit field (vkeyword) where they enter the key strokes. The vaiable lookup list view does start showing choices but does not limit it based on all the key strokes. Example: We have many grills we sell that start with SB16. But when I add an N after the SB16 the choices are not limited to just the ones with SB16N. However if I put a space after the N then I only get the ones with SB16N. Prior to the update the choices constantly dwindled based on each keystroke. I copied the code many years ago from one of the example forms that came with the DB. Do I need to change the code below? GETPROPERTY Keyword TEXTVALUE vKeyword IF vKeyword = '*' OR vKeyword = '%' THEN -- Define Where Clause SET VAR vWhereClause = ('Model# IS NOT NULL') PROPERTY LV_Quotes REFRESHLIST 'TRUE' PROPERTY LV_Quotes SET_FOCUS 'TRUE' PROPERTY ExportResultsAs ENABLED 'TRUE' GOTO Done ENDIF -- Check for at least 2 digeits. IF (SLEN (.vKeyword )) < 2 THEN GOTO Done ENDIF -- Pre-define variables SET VAR vQuotes = (CVAL('QUOTES')) SET VAR vMany = (CVAL('MANY')) SET VAR vSearchString = (.vQuotes+.vKeyword+.vMany+.vQuotes) IF vMchoice = 'ProdDesc' THEN SET VAR vWhereClause = (.vMchoice+' CONTAINS '&.vSearchString) PROPERTY LV_Quotes REFRESHLIST 'TRUE' ELSE SET VAR vWhereClause = (.vMchoice+' LIKE '&.vSearchString ) PROPERTY LV_Quotes REFRESHLIST 'TRUE' ENDIF LABEL Done CLEAR VAR iv% RETURN James Belisle Making Information Systems People Friendly Since 1990 [cid:[email protected]]
