Xdialog passing duff values?

[Graham Wickens]

I'm probably doing something daft with the following code (relevant bits only).
I click on a row in the Xdialog record list and then write the value to another table. Each time the resulting record in the receiving table is always garbage!!

Lastly, is there a way of passing more than one field value each time?

Var1_rl_def = "kl=sbsmonitor,{keylist_build('H=.030,1:0[],2:10[Reg],3:4[Type]',''+invert(when),''+invert(when),left(''+Reg,10),left(''+Icaotypecode,6))}{}"
varC_result = ui_modeless_dlg_box("SBS Monitor",<<%dlg%
{region}
[%@Var1_rl_def%.30,7Reg_Value];
{endregion};
{line=1,0};
<*8Start?enable_start><8Stop?enable_stop><8Close>
%dlg%,<<%code%
IF reg_value <> "" THEN
	trace.writeln(reg_value)
	sbs2log = table.open("sbs_logging",FILE_RW_SHARED)
	ix = sbs2log.index_primary_put("reggie")
	rec = sbs2log.fetch_find(reg_value)
	if (rec < 0 ) then
		sbs2log.enter_begin(.t.)
		sbs2log.reg = ut(reg_value)
		sbs2log.enter_end(.t.)
	END IF
	sbs2log.close()
END IF
%code%)

[Peter.Wayne]

Re: Xdialog passing duff values?

Assuming "when" is a date value, invert(when) always looks like a crazy value. And you can return any value back from the keylist. Why don't you use recno() and then you can reference any number of values from the source table by doing a fetch_goto() and accessing those fields?

[Graham Wickens]

Re: Xdialog passing duff values?

that makes sense!

In the keylist_build statement what defines the value to pass and what defines the sort order? I created the above keylist_build using Action scripting initially to get the parameters and used trial and error to get the result. The consequences are that I do not know enough about what I am doing.:o

[Graham Wickens]

Re: Xdialog passing duff values?

I think I will have to sit down and start again for several reasons, namely the dialog will only allow me to select one record, it only moves the last record selected before the dialog is closed. There is also an in-built refresh on a timer which also causes a record to be written to the second table every time it is called.

[Mike Wilson]

Re: Xdialog passing duff values?

Graham,
Why don't you use a multiselect dialog, generate a CRLF list as a variable and do this:
1. Get the first value in the list into a variable.
2. Open table and add #1 variable to table.
3. Remove the first value in the list.
4. Repeat step 1-4 until list is empty.

The following is an example you can see work in the Interactive Window.

Hope this helps.

'Create an XDialog dialog box to prompt for parameters.
DIM SHARED vMbox as C
DIM SHARED varC_result as C
auto_list_vMlist = <<%dlg%
10001
10002
10003
10004
10005
10006
10007
10008
10009
10010
%dlg%

temp_count = w_count(auto_list_vMlist,crlf())
DELETE a_vMlist
DIM a_vMlist[temp_count] as c
a_vMlist.initialize(auto_list_vMlist)
ok_button_label = "&OK"
cancel_button_label = "&Cancel"
varC_result = ui_dlg_box("LIST",<<%dlg%
{region}
Type prompt here:| [%M%.40,20vMlist^#a_vMlist];
{endregion};
{line=1,0};
{region}
<*15=ok_button_label!OK> <15=cancel_button_label!CANCEL>
{endregion};
%dlg%)

dim dcycle as N
dim ucycle as N
dim vMvalue as C

	dcycle = w_count(vMlist,crlf())
	ucycle = 1

AGAIN:
ui_msg_box("HERE IS YOUR LIST FOR ROUND #: "+ucycle,vMlist,64)

	vMvalue = word(vMlist,1,crlf(),1)
ui_msg_box("HERE IS THE VALUE TO ENTER INTO THE TABLE FOR ROUND #: "+ucycle,vMvalue,64)

	vMlist = word_remove(vMlist,1)

' >>>>  open second table and add vMvalue to the table

dcycle = dcycle - 1
ucycle = ucycle +1

	 if dcycle = 0 then
		end 
	 else
 	  GOTO AGAIN
 	end if

[Mike Wilson]

Re: Xdialog passing duff values?

I guess the proper order is this:

1. Generate Multiselect Xdialog
2. make choices
3. Open table
4. Get the first value in the CRLF list into a variable.
5. Begin table enter, Add the value to the table,end table enter
6. Remove the first value in the list.
7. Repeat step 4-7 until list is empty.
8. Close table

Which would make the table open step before the AGAIN: symbol in my example.