I would follow this format: (This will work in 6.5 not version 7.
Create one eep -- name whatever...
The buttons would be named 01 - 83 -- Must stipulate that numbers below 10 be named 01,02,03..09,etc.. Will explain in a minute.
In your eep put the following code.
SET VAR vm_colname TEXT = NULL
SET VAR vm_colname = (LUC((SGET(.#FORM_COLUMNNAME,2,1))))
IF vm_colname IS NOT NULL THEN
SWITCH(.vm_colname)
CASE '01' BREAK
CASE '02' BREAK
--.... through
CASE '83'BREAK ENDSW ENDIF
If you don't want a lot of individual control you could just do this:
In your eep put the following code. SET VAR vm_colname TEXT = NULL SET VAR vm_colname = (LUC((SGET(.#FORM_COLUMNNAME,2,1)))) IF vm_colname IS NOT NULL THEN Edit using CRC where countynumber = .vm_colname ENDIF
The reason for the 01..09 is that the SET expects 2 values and will bomb rbase bad if it doesn't get the mininimnum it expects.
Then all you would have to do is call the eep behind each button It will read the First 2 Letters of the button and go from there.
Jim Limburg
Thomas Eldred wrote:
I am trying to be clever, but am finding myself rather un-equiped for that activity....
I have a cool form that uses our state map as the background image. I want to select the county by having the user click on the map.
My question is do I need to set 83 buttons with 83 different eeps setting the variable countynumber and then have the eep launch the form using that variable as where clause? or is there a more efficient way to do this?
also in using the eep, in order to launch a form called CRC after setting the variable what syntax do I use, the form is generated in the form designer? would I use the "Edit using CRC where countynumber = xx"
Thanks for your assistance
Tom Eldred
