Xdialog Cancel Button

[Tom Henkel]

Re: Xdialog Cancel Button

Sorry about that.

I have modified the code to stop on cancel.

You need to define the variables in the report. I made them GLOBAL in the script. This means that you need to make them Global in the report. The script runs as advertised...now.

Script:

'Create an XDialog dialog box to prompt for parameters.
DIM SHARED DateBegin as D
DIM SHARED DateEnd as D
DIM SHARED varC_result as C
heading_string = "Enter Date Range of Report"
ok_button_label = "&OK"
cancel_button_label = "&Cancel"
varC_result = ui_dlg_box("Customer Contact Report",<<%dlg%
{region}
{text=30,1:heading_string};
{endregion};
{region}
Beginning Date:|	[%DATE;P=popup.calendar(dtoc(DateBegin));I=popup.calendar%.15DateBegin!DateBegin_*];
Ending Date:|	[%DATE;P=popup.calendar(dtoc(DateEnd));I=popup.calendar%.15DateEnd!DateEnd_*];
{endregion};
{line=1,0};
{region}
<*15=ok_button_label!OK> <15=cancel_button_label!CANCEL>
{endregion};
%dlg%,<<%code%
if left(a_dlg_button,10) = "DateBegin_" then 
	if a_dlg_button = "DateBegin_killfocus" then 
		DateBegin = ctod(dtoc(DateBegin))
	end if 
	a_dlg_button = ""
end if 

if left(a_dlg_button,8) = "DateEnd_" then 
	if a_dlg_button = "DateEnd_killfocus" then 
		DateEnd = ctod(dtoc(DateEnd))
	end if 
	a_dlg_button = ""
end if
%code%)
if varC_Result <>"OK"
	ui_msg_box("Customer Reports","Action Cancelled at user request")
	end
end if
dim  cnt as N

cnt = a5_get_records_in_query("customer",between_date("Contact_date",var->datebegin,var->dateend))
IF cnt=0
	ui_msg_box("Customer Report","No Customers match dates in the range of "+dtoc(var->datebegin)+" to "+dtoc(var->dateend))

	END    'DO NOT PRINT THE REPORT

  ELSE	'Preview a report, label, letter, form or browse layout. You can specify which records to preview.
	query.filter = "between(Contact_date,Var->DateBegin,Var->DateEnd)"
	query.order = "recno()"
	'replace variables in the filter with their actual values	
	query.filter = convert_expression(query.filter,"V")
	:Report.Preview("Customer Report",query.filter,query.order)
END IF
END

Attached are the PDF of the report as well as a snapshot of the Variable definition.

Have fun...

Tom

[SFS]

Re: Xdialog Cancel Button

Hey nothing for you to be sorry about. I greatly appreciate it. In your last post, your pasted the script, and in looking at the script, where and when did you change the variables to global? I'm I looking at the right script?

Thanks again...
Kelly

[Mike Wilson]

Re: Xdialog Cancel Button

Tom,
I am seeing that you have scoped the variables datebegin and dateend in your script as Shared. There is nothing else needed other than changing those in your script to global. Right?

Kelly,
Once the variables are global, they are available to place them in your report. The example I provided has this working (see picture).

[Tom Henkel]

Re: Xdialog Cancel Button

At the very top of the script where the variables are dim'd. look for

DIM GLOBAL DateBegin
DIM GLOBAL DateEnd

tom

Obviously, I copied the WRONG version of the script. Where the script says "SHARED", make it "GLOBAL"

[Mike Wilson]

Re: Xdialog Cancel Button

oops,
look again Tom.

[csda1]

Re: Xdialog Cancel Button

Hi Kelly,

...but after reading several replies to this thread, most people are steering away from Action scripting.

I'd actually guess most users of Alpha Five actually use Action Scripting more. It is useful, particularly to non-programmers, but even as a 1st step for programmers. If anything, I would encourage you to move to XBasic coding as abilities allow.

However, one should be familiar with the strengths & weaknesses of any tool they use.

Action Scripts, can be faster to create what you need, especially for the non-trivial action items.

But, it has issues of being overly complex in many cases in it's code generation (out of necessity), slower for the same reason to the equivalent XBasic Code and can potentially change the code each time you resave it with new Alpha 5 patches/versions (adding an unpredictable factor with new patches)

In code generation of action scripts, there are so many combinations of settings in Action Scripts, it is probably impossible to check every combination, making less used selections having a chance of not producing what you tried to create.

[SFS]

Re: Xdialog Cancel Button

Tom, was wondering if you could post your new new script that was modified with the "stop on cancel" so that I can review. Thank you sir...

Kelly

[Mike Wilson]

Re: Xdialog Cancel Button

Kelly,
Look at Tom's script, line 18 defines the buttons that are available in the dialog. They are OK and Cancel. Lines 36-39 reads that if the results of the dialog (VarC_result) it is not OK then end. Given 2 choices, OK and Cancel, if it is not OK, then it is Cancel and therefore the script ends.

[SFS]

Re: Xdialog Cancel Button

Thanks Mike... I have attached a new example. What I'm trying to accomplish is, the user enters in date range then chooses company, if the are NO records in the date range and the company entered, a message box would appear saying "No records found for date range ??/??/?? for ???????" (??????? = company name). Also, in my combo box, duplicate company names are appearing, what filter would you apply to stop duplicate names? Once again thank you for your time... Kelly

[Mike Wilson]

Re: Xdialog Cancel Button

OK, Kelly,
I, like Tom, am more efficient and faster using xbasic and xdialog instead of action scripting, sorry. The attached has an added button on the form that calls a script saved as a user defined function (UDF) which presents a new xdialog for the user to select a date range and the company. I believe this is what you wished for. I also got your report.company_new script to work.

How to get yours to show only unique records. Use word_unique(). The table.external_record_content_get() filter of "unique_key_value()" should work, but I have trouble with it some times, and word_unique() always works. Add this as line 7 of your first action script code:

auto_list_Company = word_unique(auto_list_Company,crlf())

then change line 23 to:

Company:| [.22[COLOR="Red"]v[/COLOR]Company^[COLOR="Red"]+[/COLOR]a_Company];

removing the %v%, and changing the = to a +.

I made the variable name vCompany. I would recommend you not use "company" as a variable name since you have a field name with this and it might confuse alpha. Traditionally people place a "v" or others in front to designate it as a variable. That being said, I then rewrote the filter with the genie for the report preview.

Hope this helps.

[SFS]

Re: Xdialog Cancel Button

Mike, I GREATLY appreciate you taking the time to help me. I did have one question, I noticed your dialog box is much bigger (which I like), were in your code set the size of the box? Once again thank you.....

Kelly

[SFS]

Re: Xdialog Cancel Button

Mike, I did have one additional question. The way we've got the things setup know, the user selects data range and (1) company to report, what if they wanted to select multiple companies and/or ALL companies, what would need to be added? Thank you...

Kelly