You need to quote the word shortcut in both places.

NameDose = NameDose IN scripts WHERE NameDose CONTAINS 'shortcut' OR shortcut = 
'shortcut'

Albert

Michael J. Sinclair, MD wrote:
Hi All,
I am converting a form from Rbase 6.5 to Rbase 7.6, and it is not behaving the 
way it used to work. To simplify my problem, I tried recreating the form with 
just the bare minimum to do a look up, 2 columns and 1 variable. Here is what I 
have....

The form is called Medlist1
The table is called medlist1
The look up table is called scripts
On the form I have eliminated everything but 2 fields, shortcut (Text 8) and 
NameDose (Text 30)
I have one variable in the expression builder....
NameDose = NameDose IN scripts WHERE NameDose CONTAINS shortcut OR shortcut = 
shortcut


In my look up table I have a few hundred lines of data. My intention is to allow the user 
to type some or all of the shortcut name for the drug and have all the of the rest of the 
fields get populated from the corresponding line in the table called scripts. In Version 
6.5, if my user typed AMO or AMOX, the field name dose would get the value 
"Amoxicillin 500 mg". If the user was adding a new drug (not found in the table 
called scripts), he could just skip the field called shortcut, and tab to the field 
called NameDose and type whatever new drug he wanted.

In the scripts table my first 2 rows of data look like this....
SHORTCUT                          NAMEDOSE
------------------------------------------------
pcn                              Penicillin 250 mg
amoxil                           Amoxicillin 500 mg

When I run the form, using either EDIT USING or ENTER USING, the form works fine so long as there is some data in the field called shortcut. B U T......when I first start the form, there is no data in the field called shortcut. Instead of having no data at all (which is what I would like to happen), the form puts the value "Penicillin 250 mg" in the field called NameDose. The SET EQNULL on/off does not seem to matter.
What am I doing wrong??
Sorry to be so long winded....I tried to keep it short.
Mike




Reply via email to