Using a Record list -List box for selections of more than one field at a time.

[MoGrace]

Re: Using a Record list -List box for selections of more than one field at a time.

Hi Mike,
I am trying to remember what it is you are doing with this script for these devices - copying them to another customer work order wasn't it?
So you would need tables for:
WO_Hdr
Customers (each with a unique cust_id - auto incr assigned in field rules),
Devices (unique devices each with a unique serial number (user input) - no blanks or duplicates allowed);
and an Items table with an unique (auto increment) record id (item_id) field.

The item table would be where you find the same device serial number assigned to different customers, but where the location may be different. There should be no blanks or duplicates in the devices table, just as there would be no blank cust_id's or duplicates in the customer table. It sounds like you may be trying to use the "items" records to copy a device to a new item?

In a work order set it would look similar to the Alpha Sports Invoice set

WO_Hdr  [work order number]
--->customer [cust_id]
==>items  [auto incr field rule adds id during data entry]
   |--->device [SN selected from lookup list]
   |--->location (probably a lookup field and not a set link)

Are you adding the same number of records each time, or do you need to make multiple selections from a list of devices to add? Because there may be a better way...

[Mike Cameron]

Re: Using a Record list -List box for selections of more than one field at a time.

I stumbled around and got the script you provided me working after posting today, I think. I will know when I go by the client's and update using their live data. Spent all afternoon experimenting since I don't/ didn't understand how the one line of code functioned that built the display array.

This line of code is the one I struggle with: dvcSerial_rl_def_orig = "kl=devices,{keylist_build("H=.05,1:15[Serial],2:10[Type],3:8[Size],4:10[Make],5:15[Model],6:15[Location],7:20[Cross_Con],8:15[Hazard],9:10[Testable]",''+serial,left(''+serial,15),left(''+type,10),left(''+size,8),left(''+make,10),left(''+model,15),left(''+location,15),left(''+cross_con,20),left(''+hazard,15),left(''+Testable,10))}{cust_numb = [varC->custid]}"DIM dvcSerial_rl_def as C dvcSerial_rl_def = replace_parameters(dvcSerial_rl_def_orig,local_variables())

Somewhere in here is where the field "Serial" is being used for an index record pointer later in the script. Maybe you could briefly explain to me what this line does.

Thanks

[MoGrace]

Re: Using a Record list -List box for selections of more than one field at a time.

That was the code the AS genie created to make the list for the xdialog. See the Wiki here for more info. But what about my question? Apparently my test data was not exactly the same as your original data. In reviewing the posts here, I am still not exactly sure what you are trying to accomplish. Can you post a screenshot of your form?

[Mike Cameron]

Re: Using a Record list -List box for selections of more than one field at a time.

I don't have access to be able to include a screenshot right now. I believe it is working properly and I appreciate the Wiki link and your quick replies!

In my form I am picking one record from the xdialog box that displays the multiple records in the devices table linked from a unique customer_id and using the chosen record to populate variables that later fill in fields on my data-entry form. . The confusion comes in because one of the fields in the Devices table was named "serial" This field is not a unique populated field and is at times blank or duplicates of other records. When we worked on this before we added a field to the devices table called "dev_id" to provide a unique auto-incremented field. I have now modified the line of code you provided from the genie for the xdialog box to exchange the reference in it from the index named "serial" to one named "dev_id", both from the devises table and the code appears to be working properly and storing the correct record in the variables. I know it is hard to see how this functions without uploading at least the forms and table structure.

Where you see the word DEV_ID in caps in the code below is how i modified it to work. Since this field is always a unique value it appears to work properly.

dvcSerial_rl_def_orig = "kl=devices,{keylist_build("H=.05,1:15[Serial],2:10[Type],3:8[Size],4:10[Make],5:15[Model],6:15[Location],7:20[Cross_Con],8:15[Hazard],9:10[Testable]",''+DEV_ID,left(''+serial,15),left(''+type,10),left(''+size,8),left(''+make,10),left(''+model,15),left(''+location,15),left(''+cross_con,20),left(''+hazard,15),left(''+Testable,10))}{cust_numb = [varC->custid]}