--=_NextPart_000_0052_01C4F56E.058CFCB0
Content-Type: text/plain;
charset="windows-1255"
Content-Transfer-Encoding: quoted-printable
If I include a date parameter in a report- in the title of the deployed = report appears a textbox in which the user should type the date in the = correct format with no mistakes (08/01/2004 ?.. 01/08/2004 ?.. 20040108 = ?..).
Is there a way to combine a standart windows calendar control instead? = how?
--=_NextPart_000_0052_01C4F56E.058CFCB0
Content-Type: text/html;
charset="windows-1255"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
&
If I include a date parameter in a = report- in the title of the deployed report appears a textbox in which the user should = type the date in the correct format with no mistakes (08/01/2004 ?.. = 01/08/2004 ?.. 20040108 ?..).
Is there a way to combine a standart = windows calendar control instead? how?
--=_NextPart_000_0052_01C4F56E.058CFCB0--This is a multi-part message in MIME format.
--=_NextPart_000_000F_01C4F624.EE666500
Content-Type: text/plain;
charset="windows-1255"
Content-Transfer-Encoding: quoted-printable
Hi Geri,
You'll need to provide your own user interface (eg. a web page) and =place the control on it to capture (and validate) the date before the =report submision is made.
Usuallly, it's best to create a web page that will call RS to determine =what parameters are required for the report at runtime and dynamically =show the user control that best fists the parameter datatype.
This generic web page can then be used over and over to provide =parameter entry / validation support for other reports as well.
- peteZ
"Geri Reshef" <GeriReshef@.Yahoo.com> wrote in message =news:uOMd81V9EHA.2032@.tk2msftngp13.phx.gbl...
If I include a date parameter in a report- in the title of the =deployed report appears a textbox in which the user should type the date =in the correct format with no mistakes (08/01/2004 ?.. 01/08/2004 ?.. =20040108 ?..).
Is there a way to combine a standart windows calendar control instead? =how?
--=_NextPart_000_000F_01C4F624.EE666500
Content-Type: text/html;
charset="windows-1255"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
&
Hi Geri,
You'll need to provide your own user interface (eg. =a web page) and place the control on it to capture (and validate) the date before the report submision is made.
Usuallly, it's best to create a web page that will =call RS to determine what parameters are required for the report at runtime and =dynamically show the user control that best fists the parameter =datatype.
This generic web page can then be used over and over =to provide parameter entry / validation support for other reports as well.
- peteZ
"Geri Reshef"
If I include a date parameter in a =report- in the title of the deployed report appears a textbox in which the user =should type the date in the correct format with no mistakes (08/01/2004 ?.. 01/08/2004 ?.. 20040108 ?..).
Is there a way to combine a standart =windows calendar control instead? how?
--=_NextPart_000_000F_01C4F624.EE666500--|||This is a multi-part message in MIME format.
--=_NextPart_000_01C5_01C4F61F.AA3585F0
Content-Type: text/plain;
charset="windows-1255"
Content-Transfer-Encoding: quoted-printable
"PeteZ" <peteZ@.aol.com> wrote in message =news:%23r4R4ic9EHA.3940@.tk2msftngp13.phx.gbl...
Hi Geri,
You'll need to provide your own user interface (eg. a web page) and =place the control on it to capture (and validate) the date before the =report submision is made.
Usuallly, it's best to create a web page that will call RS to =determine what parameters are required for the report at runtime and =dynamically show the user control that best fists the parameter =datatype.
This generic web page can then be used over and over to provide =parameter entry / validation support for other reports as well.
- peteZ
"Geri Reshef" <GeriReshef@.Yahoo.com> wrote in message =news:uOMd81V9EHA.2032@.tk2msftngp13.phx.gbl...
If I include a date parameter in a report- in the title of the =deployed report appears a textbox in which the user should type the date =in the correct format with no mistakes (08/01/2004 ?.. 01/08/2004 ?.. =20040108 ?..).
Is there a way to combine a standart windows calendar control =instead? how?
--=_NextPart_000_01C5_01C4F61F.AA3585F0
Content-Type: text/html;
charset="windows-1255"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
&
"PeteZ"
Hi Geri,
You'll need to provide your own user interface =(eg. a web page) and place the control on it to capture (and validate) the date before the report submision is made.
Usuallly, it's best to create a web page that will =call RS to determine what parameters are required for the report at runtime =and dynamically show the user control that best fists the parameter datatype.
This generic web page can then be used over and =over to provide parameter entry / validation support for other reports as well.
- peteZ
"Geri Reshef"
If I include a date parameter in a =report- in the title of the deployed report appears a textbox in which the user =should type the date in the correct format with no mistakes (08/01/2004 ?.. = 01/08/2004 ?.. 20040108 ?..).
Is there a way to combine a =standart windows calendar control instead? how?
--=_NextPart_000_01C5_01C4F61F.AA3585F0--|||You'd better combine a web calendar control in a web application ,which call
Reporting Service as a web service.I.ve implemented it .
"Geri Reshef" wrote:
> If I include a date parameter in a report- in the title of the deployed report appears a textbox in which the user should type the date in the correct format with no mistakes (08/01/2004 ?.. 01/08/2004 ?.. 20040108 ?..).
> Is there a way to combine a standart windows calendar control instead? how?
No comments:
Post a Comment