help

Comments

• gordk St.Catherines On. Canada.

  December 2010 edited 11:10PM

  Larry i can't be sure of what they have given you to work with
  but you must convert the inbutbox result to a tdatetime as it is returning a string.
  in design mode on the codepage
  at the top of the page declare your variable this makes it global to all procedures
  and in the bottom
  begin
  end.
  block write code to set the value this block of code is the first script to run
  sample
  
  var
  mydate:tdatetime;
  begin
  mydate:=strtodate(InputBox('Date entry','in the format mm/dd/yyyy','02/28/2010'));
  end.
  or you can use dialog form and a dateedit control
• thumper

  December 2010 edited 11:10PM

  Thanks gordk
  
  while waiting for a reply here I worked that out and was 1st using a string to get the user input then the strtodate to get a valid date.
  your line shortens my code so added in place of my 3 lines and 2 variables..nice
  
  but still have 2 problems
  1 the showmessage ( mydate) taking the default of '18/11/2010' gives me a numeric number of 40500 ??confusing me
  and
  2 if I try to replace the line IF <orders."ORDDATE"> =<date> with IF <orders."ORDDATE"> = <mydate> I get an error at end of report that say's mydate is undeclared so assume its because it was declared in another procedure
  tried adding it at the bottom between the begin and end. but keeps asking for a ;
  
  where do I create the variable that is global ?
  
  my script thus far
  
  
  procedure ReportOnStartReport(Sender: TfrxComponent);
  var
  mydate:tdatetime;
  begin
  mydate:=strtodate(InputBox('Date entry','in the format dd/mm/yyyy','18/11/2010'));
  showmessage( mydate ); ' just for my check returns 40500
  
  end;
  procedure MasterData1OnBeforePrint(Sender: TfrxComponent);
  Begin
  IF <orders."ORDDATE"> =<mydate> ' problem here not picking up mydate
  THEN MASTERDATA1.VISIBLE:= TRUE
  ELSE MASTERDATA1.VISIBLE:= FALSE;
  end;
• gordk St.Catherines On. Canada.

  December 2010 edited 11:10PM

  first declare that variable where i told you making it global to all procedures and lasts for the life of the report.
  not within a procedure (local) when the procedure is finished so is the variable.
  When you use typed variables in code you do not need <> just the variable name.
  only when you use categorized variables(expressions or datafields) do you need to use the <>
  showmessage( mydate ) should be
  showmessage(datetostr(mydate));
• thumper

  December 2010 edited 11:10PM

  GordK
  thanks you are a star my report now works perfectly after finally working out how pascal works logically and now defaults to todays date or user can now change it.
  what would be nice now would be to have an error routine that checks for a valid date before running the procedure and allow the input box to be reshown to corrrect the date.
  any idea on this?
  does Pascal have something like on error goto ?
  
  my script

  ---

  var
  mydate:tdatetime;
  
  procedure MasterData1OnBeforePrint(Sender: TfrxComponent);
  Begin
  IF <orders."ORDDATE"> =mydate
  THEN MASTERDATA1.VISIBLE:= TRUE
  ELSE MASTERDATA1.VISIBLE:= FALSE;
  end;
  
  begin
  mydate:=strtodate(InputBox('Date entry','in the format dd/mm/yyyy',<Date>));
  
  end.

  ---
• gordk St.Catherines On. Canada.

  December 2010 edited 11:10PM

  the report script is actually fastscript using the pascal language.
  there is no goto in pascal but there is a try except finally construct.
  Just for your info you could write this differently
  IF <orders."ORDDATE"> =mydate
  THEN MASTERDATA1.VISIBLE:= TRUE
  ELSE MASTERDATA1.VISIBLE:= FALSE;
  end;
  
  shortform syntax
  masterdata1.visible := (<orders."date"> = mydate);
  
  my own prefrence would be to add a dialog page to the report with a datedit control
  and 2 buttons ok cancel