Using SQL Server 2000...
I have a front end that provides the user with a 'search engine' to
pass search parameters. The stored procedure it calls joins multiple
tables/views to return the proper result.
I am running into a problem that I solved in the interface using code
(that takes WAY too long), but I know there must be a way to have SQL
Server do the work using T-SQL... as this seems a very simple issue.
The following is just a snippet of the pertinent information:
Assume I have a main Customer table with a unique CustID field.
I have another table of descriptive Flags with a unique FlagID field.
A third table Customer_Flag_Link has a unique ID field and contains 2
columns, the CustID and the FlagID.
Obvioulsy, the role of this 3rd table is to be able to assign multiple
Flags to each Customer.
Now assume I have the following data in the Customer_Flag_Link table:
UniqueID CustID FlagID
===============================
1 123 333
2 123 444
3 123 222
4 987 444
5 987 222
6 567 111
7 567 222
My issue is that I want to be able to locate Customers who have ALL of
the passed Flags associated with them, I do not know how many Flags
will be passed (and there are other search parameters passed as well -
but this is the piece that is giving me trouble, though I am sure it
is simple!)
For example, I want to return CustID where exists FlagID 222 AND 444.
Based on the above data it should return CustID 123 and 987, but not
567.
Currently, I use the IN operator (ie: FlagID IN (222,444)) but clearly
this does not give me the results I want.
Any ideas would be appreciated!
Thanks,
AK
This might help.
SELECT COUNT(distinct FlagID)
FROM Customer_Flag_Link
WHERE FlagID IN (222,444)
AND Customer = 'Ralph'
HAVING COUNT(distinct FlagID) = 2
The number of items in the IN clause is what is used in the HAVING
test. Of course this could be written as an EXISTS subquery,
correlated on Customer.
Roy Harvey
Beacon Falls, CT
On Thu, 21 Jun 2007 10:50:45 -0700, aklein <abklein@.optonline.net>
wrote:
>Using SQL Server 2000...
>I have a front end that provides the user with a 'search engine' to
>pass search parameters. The stored procedure it calls joins multiple
>tables/views to return the proper result.
>I am running into a problem that I solved in the interface using code
>(that takes WAY too long), but I know there must be a way to have SQL
>Server do the work using T-SQL... as this seems a very simple issue.
>The following is just a snippet of the pertinent information:
>Assume I have a main Customer table with a unique CustID field.
>I have another table of descriptive Flags with a unique FlagID field.
>A third table Customer_Flag_Link has a unique ID field and contains 2
>columns, the CustID and the FlagID.
>Obvioulsy, the role of this 3rd table is to be able to assign multiple
>Flags to each Customer.
>Now assume I have the following data in the Customer_Flag_Link table:
>
>UniqueID CustID FlagID
>===============================
>1 123 333
>2 123 444
>3 123 222
>4 987 444
>5 987 222
>6 567 111
>7 567 222
>My issue is that I want to be able to locate Customers who have ALL of
>the passed Flags associated with them, I do not know how many Flags
>will be passed (and there are other search parameters passed as well -
>but this is the piece that is giving me trouble, though I am sure it
>is simple!)
>For example, I want to return CustID where exists FlagID 222 AND 444.
>Based on the above data it should return CustID 123 and 987, but not
>567.
>Currently, I use the IN operator (ie: FlagID IN (222,444)) but clearly
>this does not give me the results I want.
>Any ideas would be appreciated!
>Thanks,
>AK
|||Hmmmm...
I have to see how to stick that idea into the larger procedure... but
it gives me a starting point.
Thanks for the idea!
AK
Showing posts with label parameters. Show all posts
Showing posts with label parameters. Show all posts
Monday, March 19, 2012
Locate records that meet ALL the requirements using IN or EXIST? Help?
Using SQL Server 2000...
I have a front end that provides the user with a 'search engine' to
pass search parameters. The stored procedure it calls joins multiple
tables/views to return the proper result.
I am running into a problem that I solved in the interface using code
(that takes WAY too long), but I know there must be a way to have SQL
Server do the work using T-SQL... as this seems a very simple issue.
The following is just a snippet of the pertinent information:
Assume I have a main Customer table with a unique CustID field.
I have another table of descriptive Flags with a unique FlagID field.
A third table Customer_Flag_Link has a unique ID field and contains 2
columns, the CustID and the FlagID.
Obvioulsy, the role of this 3rd table is to be able to assign multiple
Flags to each Customer.
Now assume I have the following data in the Customer_Flag_Link table:
UniqueID CustID FlagID
=============================== 1 123 333
2 123 444
3 123 222
4 987 444
5 987 222
6 567 111
7 567 222
My issue is that I want to be able to locate Customers who have ALL of
the passed Flags associated with them, I do not know how many Flags
will be passed (and there are other search parameters passed as well -
but this is the piece that is giving me trouble, though I am sure it
is simple!)
For example, I want to return CustID where exists FlagID 222 AND 444.
Based on the above data it should return CustID 123 and 987, but not
567.
Currently, I use the IN operator (ie: FlagID IN (222,444)) but clearly
this does not give me the results I want.
Any ideas would be appreciated!
Thanks,
AKThis might help.
SELECT COUNT(distinct FlagID)
FROM Customer_Flag_Link
WHERE FlagID IN (222,444)
AND Customer = 'Ralph'
HAVING COUNT(distinct FlagID) = 2
The number of items in the IN clause is what is used in the HAVING
test. Of course this could be written as an EXISTS subquery,
correlated on Customer.
Roy Harvey
Beacon Falls, CT
On Thu, 21 Jun 2007 10:50:45 -0700, aklein <abklein@.optonline.net>
wrote:
>Using SQL Server 2000...
>I have a front end that provides the user with a 'search engine' to
>pass search parameters. The stored procedure it calls joins multiple
>tables/views to return the proper result.
>I am running into a problem that I solved in the interface using code
>(that takes WAY too long), but I know there must be a way to have SQL
>Server do the work using T-SQL... as this seems a very simple issue.
>The following is just a snippet of the pertinent information:
>Assume I have a main Customer table with a unique CustID field.
>I have another table of descriptive Flags with a unique FlagID field.
>A third table Customer_Flag_Link has a unique ID field and contains 2
>columns, the CustID and the FlagID.
>Obvioulsy, the role of this 3rd table is to be able to assign multiple
>Flags to each Customer.
>Now assume I have the following data in the Customer_Flag_Link table:
>
>UniqueID CustID FlagID
>===============================>1 123 333
>2 123 444
>3 123 222
>4 987 444
>5 987 222
>6 567 111
>7 567 222
>My issue is that I want to be able to locate Customers who have ALL of
>the passed Flags associated with them, I do not know how many Flags
>will be passed (and there are other search parameters passed as well -
>but this is the piece that is giving me trouble, though I am sure it
>is simple!)
>For example, I want to return CustID where exists FlagID 222 AND 444.
>Based on the above data it should return CustID 123 and 987, but not
>567.
>Currently, I use the IN operator (ie: FlagID IN (222,444)) but clearly
>this does not give me the results I want.
>Any ideas would be appreciated!
>Thanks,
>AK|||Hmmmm...
I have to see how to stick that idea into the larger procedure... but
it gives me a starting point.
Thanks for the idea!
AK
I have a front end that provides the user with a 'search engine' to
pass search parameters. The stored procedure it calls joins multiple
tables/views to return the proper result.
I am running into a problem that I solved in the interface using code
(that takes WAY too long), but I know there must be a way to have SQL
Server do the work using T-SQL... as this seems a very simple issue.
The following is just a snippet of the pertinent information:
Assume I have a main Customer table with a unique CustID field.
I have another table of descriptive Flags with a unique FlagID field.
A third table Customer_Flag_Link has a unique ID field and contains 2
columns, the CustID and the FlagID.
Obvioulsy, the role of this 3rd table is to be able to assign multiple
Flags to each Customer.
Now assume I have the following data in the Customer_Flag_Link table:
UniqueID CustID FlagID
=============================== 1 123 333
2 123 444
3 123 222
4 987 444
5 987 222
6 567 111
7 567 222
My issue is that I want to be able to locate Customers who have ALL of
the passed Flags associated with them, I do not know how many Flags
will be passed (and there are other search parameters passed as well -
but this is the piece that is giving me trouble, though I am sure it
is simple!)
For example, I want to return CustID where exists FlagID 222 AND 444.
Based on the above data it should return CustID 123 and 987, but not
567.
Currently, I use the IN operator (ie: FlagID IN (222,444)) but clearly
this does not give me the results I want.
Any ideas would be appreciated!
Thanks,
AKThis might help.
SELECT COUNT(distinct FlagID)
FROM Customer_Flag_Link
WHERE FlagID IN (222,444)
AND Customer = 'Ralph'
HAVING COUNT(distinct FlagID) = 2
The number of items in the IN clause is what is used in the HAVING
test. Of course this could be written as an EXISTS subquery,
correlated on Customer.
Roy Harvey
Beacon Falls, CT
On Thu, 21 Jun 2007 10:50:45 -0700, aklein <abklein@.optonline.net>
wrote:
>Using SQL Server 2000...
>I have a front end that provides the user with a 'search engine' to
>pass search parameters. The stored procedure it calls joins multiple
>tables/views to return the proper result.
>I am running into a problem that I solved in the interface using code
>(that takes WAY too long), but I know there must be a way to have SQL
>Server do the work using T-SQL... as this seems a very simple issue.
>The following is just a snippet of the pertinent information:
>Assume I have a main Customer table with a unique CustID field.
>I have another table of descriptive Flags with a unique FlagID field.
>A third table Customer_Flag_Link has a unique ID field and contains 2
>columns, the CustID and the FlagID.
>Obvioulsy, the role of this 3rd table is to be able to assign multiple
>Flags to each Customer.
>Now assume I have the following data in the Customer_Flag_Link table:
>
>UniqueID CustID FlagID
>===============================>1 123 333
>2 123 444
>3 123 222
>4 987 444
>5 987 222
>6 567 111
>7 567 222
>My issue is that I want to be able to locate Customers who have ALL of
>the passed Flags associated with them, I do not know how many Flags
>will be passed (and there are other search parameters passed as well -
>but this is the piece that is giving me trouble, though I am sure it
>is simple!)
>For example, I want to return CustID where exists FlagID 222 AND 444.
>Based on the above data it should return CustID 123 and 987, but not
>567.
>Currently, I use the IN operator (ie: FlagID IN (222,444)) but clearly
>this does not give me the results I want.
>Any ideas would be appreciated!
>Thanks,
>AK|||Hmmmm...
I have to see how to stick that idea into the larger procedure... but
it gives me a starting point.
Thanks for the idea!
AK
Locate records that meet ALL the requirements using IN or EXIST? Help?
Using SQL Server 2000...
I have a front end that provides the user with a 'search engine' to
pass search parameters. The stored procedure it calls joins multiple
tables/views to return the proper result.
I am running into a problem that I solved in the interface using code
(that takes WAY too long), but I know there must be a way to have SQL
Server do the work using T-SQL... as this seems a very simple issue.
The following is just a snippet of the pertinent information:
Assume I have a main Customer table with a unique CustID field.
I have another table of descriptive Flags with a unique FlagID field.
A third table Customer_Flag_Link has a unique ID field and contains 2
columns, the CustID and the FlagID.
Obvioulsy, the role of this 3rd table is to be able to assign multiple
Flags to each Customer.
Now assume I have the following data in the Customer_Flag_Link table:
UniqueID CustID FlagID
===============================
1 123 333
2 123 444
3 123 222
4 987 444
5 987 222
6 567 111
7 567 222
My issue is that I want to be able to locate Customers who have ALL of
the passed Flags associated with them, I do not know how many Flags
will be passed (and there are other search parameters passed as well -
but this is the piece that is giving me trouble, though I am sure it
is simple!)
For example, I want to return CustID where exists FlagID 222 AND 444.
Based on the above data it should return CustID 123 and 987, but not
567.
Currently, I use the IN operator (ie: FlagID IN (222,444)) but clearly
this does not give me the results I want.
Any ideas would be appreciated!
Thanks,
AKThis might help.
SELECT COUNT(distinct FlagID)
FROM Customer_Flag_Link
WHERE FlagID IN (222,444)
AND Customer = 'Ralph'
HAVING COUNT(distinct FlagID) = 2
The number of items in the IN clause is what is used in the HAVING
test. Of course this could be written as an EXISTS subquery,
correlated on Customer.
Roy Harvey
Beacon Falls, CT
On Thu, 21 Jun 2007 10:50:45 -0700, aklein <abklein@.optonline.net>
wrote:
>Using SQL Server 2000...
>I have a front end that provides the user with a 'search engine' to
>pass search parameters. The stored procedure it calls joins multiple
>tables/views to return the proper result.
>I am running into a problem that I solved in the interface using code
>(that takes WAY too long), but I know there must be a way to have SQL
>Server do the work using T-SQL... as this seems a very simple issue.
>The following is just a snippet of the pertinent information:
>Assume I have a main Customer table with a unique CustID field.
>I have another table of descriptive Flags with a unique FlagID field.
>A third table Customer_Flag_Link has a unique ID field and contains 2
>columns, the CustID and the FlagID.
>Obvioulsy, the role of this 3rd table is to be able to assign multiple
>Flags to each Customer.
>Now assume I have the following data in the Customer_Flag_Link table:
>
>UniqueID CustID FlagID
>===============================
>1 123 333
>2 123 444
>3 123 222
>4 987 444
>5 987 222
>6 567 111
>7 567 222
>My issue is that I want to be able to locate Customers who have ALL of
>the passed Flags associated with them, I do not know how many Flags
>will be passed (and there are other search parameters passed as well -
>but this is the piece that is giving me trouble, though I am sure it
>is simple!)
>For example, I want to return CustID where exists FlagID 222 AND 444.
>Based on the above data it should return CustID 123 and 987, but not
>567.
>Currently, I use the IN operator (ie: FlagID IN (222,444)) but clearly
>this does not give me the results I want.
>Any ideas would be appreciated!
>Thanks,
>AK|||Hmmmm...
I have to see how to stick that idea into the larger procedure... but
it gives me a starting point.
Thanks for the idea!
AK
I have a front end that provides the user with a 'search engine' to
pass search parameters. The stored procedure it calls joins multiple
tables/views to return the proper result.
I am running into a problem that I solved in the interface using code
(that takes WAY too long), but I know there must be a way to have SQL
Server do the work using T-SQL... as this seems a very simple issue.
The following is just a snippet of the pertinent information:
Assume I have a main Customer table with a unique CustID field.
I have another table of descriptive Flags with a unique FlagID field.
A third table Customer_Flag_Link has a unique ID field and contains 2
columns, the CustID and the FlagID.
Obvioulsy, the role of this 3rd table is to be able to assign multiple
Flags to each Customer.
Now assume I have the following data in the Customer_Flag_Link table:
UniqueID CustID FlagID
===============================
1 123 333
2 123 444
3 123 222
4 987 444
5 987 222
6 567 111
7 567 222
My issue is that I want to be able to locate Customers who have ALL of
the passed Flags associated with them, I do not know how many Flags
will be passed (and there are other search parameters passed as well -
but this is the piece that is giving me trouble, though I am sure it
is simple!)
For example, I want to return CustID where exists FlagID 222 AND 444.
Based on the above data it should return CustID 123 and 987, but not
567.
Currently, I use the IN operator (ie: FlagID IN (222,444)) but clearly
this does not give me the results I want.
Any ideas would be appreciated!
Thanks,
AKThis might help.
SELECT COUNT(distinct FlagID)
FROM Customer_Flag_Link
WHERE FlagID IN (222,444)
AND Customer = 'Ralph'
HAVING COUNT(distinct FlagID) = 2
The number of items in the IN clause is what is used in the HAVING
test. Of course this could be written as an EXISTS subquery,
correlated on Customer.
Roy Harvey
Beacon Falls, CT
On Thu, 21 Jun 2007 10:50:45 -0700, aklein <abklein@.optonline.net>
wrote:
>Using SQL Server 2000...
>I have a front end that provides the user with a 'search engine' to
>pass search parameters. The stored procedure it calls joins multiple
>tables/views to return the proper result.
>I am running into a problem that I solved in the interface using code
>(that takes WAY too long), but I know there must be a way to have SQL
>Server do the work using T-SQL... as this seems a very simple issue.
>The following is just a snippet of the pertinent information:
>Assume I have a main Customer table with a unique CustID field.
>I have another table of descriptive Flags with a unique FlagID field.
>A third table Customer_Flag_Link has a unique ID field and contains 2
>columns, the CustID and the FlagID.
>Obvioulsy, the role of this 3rd table is to be able to assign multiple
>Flags to each Customer.
>Now assume I have the following data in the Customer_Flag_Link table:
>
>UniqueID CustID FlagID
>===============================
>1 123 333
>2 123 444
>3 123 222
>4 987 444
>5 987 222
>6 567 111
>7 567 222
>My issue is that I want to be able to locate Customers who have ALL of
>the passed Flags associated with them, I do not know how many Flags
>will be passed (and there are other search parameters passed as well -
>but this is the piece that is giving me trouble, though I am sure it
>is simple!)
>For example, I want to return CustID where exists FlagID 222 AND 444.
>Based on the above data it should return CustID 123 and 987, but not
>567.
>Currently, I use the IN operator (ie: FlagID IN (222,444)) but clearly
>this does not give me the results I want.
>Any ideas would be appreciated!
>Thanks,
>AK|||Hmmmm...
I have to see how to stick that idea into the larger procedure... but
it gives me a starting point.
Thanks for the idea!
AK
Monday, March 12, 2012
Localization problem
Hi
I have a report with a "Jump to report" navigation field to a second report
, some of the parameters to the second report are DateTime values, when my
Local Settings are setted to English (United States) the link works fine,
but when I change my Local Settings to Spanish I get a Type Mismatch
message for this DateTime parameters. The "Language" property of both
reports are "Default", and when I execute by my self the second report
specifying each parameter with the correct locale datetime format it works
fine.
Any idea?
Thanksthis could happend because of session/caching of the subreport.
Click "Refresh" button on the toolbar when viewing the subreport.
--
This posting is provided "AS IS" with no warranties, and confers no rights.
"Mauricio Cadima" <mcadima@.jalasoft.com> wrote in message
news:uqK6c$2mEHA.404@.TK2MSFTNGP12.phx.gbl...
> Hi
> I have a report with a "Jump to report" navigation field to a second
> report
> , some of the parameters to the second report are DateTime values, when my
> Local Settings are setted to English (United States) the link works fine,
> but when I change my Local Settings to Spanish I get a Type Mismatch
> message for this DateTime parameters. The "Language" property of both
> reports are "Default", and when I execute by my self the second report
> specifying each parameter with the correct locale datetime format it works
> fine.
> Any idea?
> Thanks
>|||Thanks for your answer, but I think that is not the problem.
Let me explain the problem again, I have a first report with two parameters,
"Start Date" and "End Date" that are used when the report is executed to get
some information from some DB for this time range, this information is
showed in a table where the first column values are links to other report
(not a subrerport), this second report also uses date range parameters and
its values should be the same of the first report parameters, this means
that also should be specified in the link.
So when I click the link to open the second report and I have Spanish or
other locale selected for my system regional options a type mismatch message
is showed instead of the second report:
"The value provided for the report parameter 'EndDate' is not valid for its
type. (rsReportParameterTypeMismatch)"
My intuition is that the problem is with the date format, the date format
for Spanish locales is 'dd/mm/yyyy' and for english locale 'mm/dd/yyyy' I
think that the second report is trying to build its date time parameters
with the English locale and here is where the exception is raised. E.g. set
a value greater than 12 as month.
When I execute the second report specifying the parameters values manually
with the correct locale date format the report is showed without problems.
When I see the "Language" property of both reports in design mode is set to
default, I suppose that means that the report should works with the system
locale settings and use the correct date formats.
Thanks
Mauricio
"Lev Semenets [MSFT]" <levs@.microsoft.com> wrote in message
news:e8ju$c4mEHA.648@.tk2msftngp13.phx.gbl...
> this could happend because of session/caching of the subreport.
> Click "Refresh" button on the toolbar when viewing the subreport.
> --
> This posting is provided "AS IS" with no warranties, and confers no
rights.
>
> "Mauricio Cadima" <mcadima@.jalasoft.com> wrote in message
> news:uqK6c$2mEHA.404@.TK2MSFTNGP12.phx.gbl...
> > Hi
> > I have a report with a "Jump to report" navigation field to a second
> > report
> > , some of the parameters to the second report are DateTime values, when
my
> > Local Settings are setted to English (United States) the link works
fine,
> > but when I change my Local Settings to Spanish I get a Type Mismatch
> > message for this DateTime parameters. The "Language" property of both
> > reports are "Default", and when I execute by my self the second report
> > specifying each parameter with the correct locale datetime format it
works
> > fine.
> > Any idea?
> > Thanks
> >
> >
>|||What are parameters values that you pass to second report? What do you put
into Parameter Value cell of Parameters dialog?
--
This posting is provided "AS IS" with no warranties, and confers no rights.
"Mauricio Cadima" <mcadima@.jalasoft.com> wrote in message
news:%23HlTA0AnEHA.3196@.TK2MSFTNGP10.phx.gbl...
> Thanks for your answer, but I think that is not the problem.
>
> Let me explain the problem again, I have a first report with two
> parameters,
> "Start Date" and "End Date" that are used when the report is executed to
> get
> some information from some DB for this time range, this information is
> showed in a table where the first column values are links to other report
> (not a subrerport), this second report also uses date range parameters and
> its values should be the same of the first report parameters, this means
> that also should be specified in the link.
>
> So when I click the link to open the second report and I have Spanish or
> other locale selected for my system regional options a type mismatch
> message
> is showed instead of the second report:
>
> "The value provided for the report parameter 'EndDate' is not valid for
> its
> type. (rsReportParameterTypeMismatch)"
>
> My intuition is that the problem is with the date format, the date format
> for Spanish locales is 'dd/mm/yyyy' and for english locale 'mm/dd/yyyy' I
> think that the second report is trying to build its date time parameters
> with the English locale and here is where the exception is raised. E.g.
> set
> a value greater than 12 as month.
>
> When I execute the second report specifying the parameters values manually
> with the correct locale date format the report is showed without problems.
> When I see the "Language" property of both reports in design mode is set
> to
> default, I suppose that means that the report should works with the system
> locale settings and use the correct date formats.
>
> Thanks
> Mauricio
>
> "Lev Semenets [MSFT]" <levs@.microsoft.com> wrote in message
> news:e8ju$c4mEHA.648@.tk2msftngp13.phx.gbl...
>> this could happend because of session/caching of the subreport.
>> Click "Refresh" button on the toolbar when viewing the subreport.
>> --
>> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>>
>> "Mauricio Cadima" <mcadima@.jalasoft.com> wrote in message
>> news:uqK6c$2mEHA.404@.TK2MSFTNGP12.phx.gbl...
>> > Hi
>> > I have a report with a "Jump to report" navigation field to a second
>> > report
>> > , some of the parameters to the second report are DateTime values, when
> my
>> > Local Settings are setted to English (United States) the link works
> fine,
>> > but when I change my Local Settings to Spanish I get a Type Mismatch
>> > message for this DateTime parameters. The "Language" property of both
>> > reports are "Default", and when I execute by my self the second report
>> > specifying each parameter with the correct locale datetime format it
> works
>> > fine.
>> > Any idea?
>> > Thanks
>> >
>> >
>>
>|||The same values of the first report parameters:
Parameter Name Parameter Value
StartDate =Parameters!StartDate.Value
EndDate =Parameters!EndDate.Value
"Lev Semenets [MSFT]" <levs@.microsoft.com> wrote in message
news:%23uc293FnEHA.3452@.TK2MSFTNGP15.phx.gbl...
> What are parameters values that you pass to second report? What do you put
> into Parameter Value cell of Parameters dialog?
> --
> This posting is provided "AS IS" with no warranties, and confers no
rights.
> "Mauricio Cadima" <mcadima@.jalasoft.com> wrote in message
> news:%23HlTA0AnEHA.3196@.TK2MSFTNGP10.phx.gbl...
> > Thanks for your answer, but I think that is not the problem.
> >
> >
> >
> > Let me explain the problem again, I have a first report with two
> > parameters,
> > "Start Date" and "End Date" that are used when the report is executed to
> > get
> > some information from some DB for this time range, this information is
> > showed in a table where the first column values are links to other
report
> > (not a subrerport), this second report also uses date range parameters
and
> > its values should be the same of the first report parameters, this means
> > that also should be specified in the link.
> >
> >
> >
> > So when I click the link to open the second report and I have Spanish or
> > other locale selected for my system regional options a type mismatch
> > message
> > is showed instead of the second report:
> >
> >
> >
> > "The value provided for the report parameter 'EndDate' is not valid for
> > its
> > type. (rsReportParameterTypeMismatch)"
> >
> >
> >
> > My intuition is that the problem is with the date format, the date
format
> > for Spanish locales is 'dd/mm/yyyy' and for english locale 'mm/dd/yyyy'
I
> > think that the second report is trying to build its date time parameters
> > with the English locale and here is where the exception is raised. E.g.
> > set
> > a value greater than 12 as month.
> >
> >
> >
> > When I execute the second report specifying the parameters values
manually
> > with the correct locale date format the report is showed without
problems.
> > When I see the "Language" property of both reports in design mode is set
> > to
> > default, I suppose that means that the report should works with the
system
> > locale settings and use the correct date formats.
> >
> >
> >
> > Thanks
> >
> > Mauricio
> >
> >
> >
> > "Lev Semenets [MSFT]" <levs@.microsoft.com> wrote in message
> > news:e8ju$c4mEHA.648@.tk2msftngp13.phx.gbl...
> >> this could happend because of session/caching of the subreport.
> >> Click "Refresh" button on the toolbar when viewing the subreport.
> >>
> >> --
> >> This posting is provided "AS IS" with no warranties, and confers no
> > rights.
> >>
> >>
> >> "Mauricio Cadima" <mcadima@.jalasoft.com> wrote in message
> >> news:uqK6c$2mEHA.404@.TK2MSFTNGP12.phx.gbl...
> >> > Hi
> >> > I have a report with a "Jump to report" navigation field to a second
> >> > report
> >> > , some of the parameters to the second report are DateTime values,
when
> > my
> >> > Local Settings are setted to English (United States) the link works
> > fine,
> >> > but when I change my Local Settings to Spanish I get a Type Mismatch
> >> > message for this DateTime parameters. The "Language" property of both
> >> > reports are "Default", and when I execute by my self the second
report
> >> > specifying each parameter with the correct locale datetime format it
> > works
> >> > fine.
> >> > Any idea?
> >> > Thanks
> >> >
> >> >
> >>
> >>
> >
> >
>|||I have having the very same problem. Did you ever solve this? And how
if you did?!
Thanks|||I have this problem as well, even though my report language is set to English
(United Kingdom), my Asp.Net app that calls the reporting service web service
is using en-GB as culture. It still thinks that my parameter End Date should
be in mm/dd/yyyy format and pukes when it sees something like 14/12/2004
(December 14, 2004) come over.
"Gearoid" wrote:
> I have having the very same problem. Did you ever solve this? And how
> if you did?!
> Thanks
>|||Adam,
Check the "Language Settings" for your browser.
Open IE, goto Tools->Internet Options->Click 'Languages...' button on the
General tab. Check that your language is English (United Kingdom)
I have got MSRS to work fine with UK English format dates... apart from
when reports are linked using 'Jump to' action.
Joe
"AdamB" wrote:
> I have this problem as well, even though my report language is set to English
> (United Kingdom), my Asp.Net app that calls the reporting service web service
> is using en-GB as culture. It still thinks that my parameter End Date should
> be in mm/dd/yyyy format and pukes when it sees something like 14/12/2004
> (December 14, 2004) come over.
> "Gearoid" wrote:
> > I have having the very same problem. Did you ever solve this? And how
> > if you did?!
> >
> > Thanks
> >
> >|||Try this and see if it works
Parameter Name Parameter Value
StartDate =Format(Parameters!StartDate.Value,
"dd-MMMM-yyyy")
EndDate =Format(Parameters!EndDate.Value,
"dd-MMMM-yyyy")
Cheers,
Harry
"Mauricio Cadima" wrote:
> The same values of the first report parameters:
> Parameter Name Parameter Value
> StartDate =Parameters!StartDate.Value
> EndDate =Parameters!EndDate.Value
> "Lev Semenets [MSFT]" <levs@.microsoft.com> wrote in message
> news:%23uc293FnEHA.3452@.TK2MSFTNGP15.phx.gbl...
> > What are parameters values that you pass to second report? What do you put
> > into Parameter Value cell of Parameters dialog?
> >
> > --
> > This posting is provided "AS IS" with no warranties, and confers no
> rights.
> >
> > "Mauricio Cadima" <mcadima@.jalasoft.com> wrote in message
> > news:%23HlTA0AnEHA.3196@.TK2MSFTNGP10.phx.gbl...
> > > Thanks for your answer, but I think that is not the problem.
> > >
> > >
> > >
> > > Let me explain the problem again, I have a first report with two
> > > parameters,
> > > "Start Date" and "End Date" that are used when the report is executed to
> > > get
> > > some information from some DB for this time range, this information is
> > > showed in a table where the first column values are links to other
> report
> > > (not a subrerport), this second report also uses date range parameters
> and
> > > its values should be the same of the first report parameters, this means
> > > that also should be specified in the link.
> > >
> > >
> > >
> > > So when I click the link to open the second report and I have Spanish or
> > > other locale selected for my system regional options a type mismatch
> > > message
> > > is showed instead of the second report:
> > >
> > >
> > >
> > > "The value provided for the report parameter 'EndDate' is not valid for
> > > its
> > > type. (rsReportParameterTypeMismatch)"
> > >
> > >
> > >
> > > My intuition is that the problem is with the date format, the date
> format
> > > for Spanish locales is 'dd/mm/yyyy' and for english locale 'mm/dd/yyyy'
> I
> > > think that the second report is trying to build its date time parameters
> > > with the English locale and here is where the exception is raised. E.g.
> > > set
> > > a value greater than 12 as month.
> > >
> > >
> > >
> > > When I execute the second report specifying the parameters values
> manually
> > > with the correct locale date format the report is showed without
> problems.
> > > When I see the "Language" property of both reports in design mode is set
> > > to
> > > default, I suppose that means that the report should works with the
> system
> > > locale settings and use the correct date formats.
> > >
> > >
> > >
> > > Thanks
> > >
> > > Mauricio
> > >
> > >
> > >
> > > "Lev Semenets [MSFT]" <levs@.microsoft.com> wrote in message
> > > news:e8ju$c4mEHA.648@.tk2msftngp13.phx.gbl...
> > >> this could happend because of session/caching of the subreport.
> > >> Click "Refresh" button on the toolbar when viewing the subreport.
> > >>
> > >> --
> > >> This posting is provided "AS IS" with no warranties, and confers no
> > > rights.
> > >>
> > >>
> > >> "Mauricio Cadima" <mcadima@.jalasoft.com> wrote in message
> > >> news:uqK6c$2mEHA.404@.TK2MSFTNGP12.phx.gbl...
> > >> > Hi
> > >> > I have a report with a "Jump to report" navigation field to a second
> > >> > report
> > >> > , some of the parameters to the second report are DateTime values,
> when
> > > my
> > >> > Local Settings are setted to English (United States) the link works
> > > fine,
> > >> > but when I change my Local Settings to Spanish I get a Type Mismatch
> > >> > message for this DateTime parameters. The "Language" property of both
> > >> > reports are "Default", and when I execute by my self the second
> report
> > >> > specifying each parameter with the correct locale datetime format it
> > > works
> > >> > fine.
> > >> > Any idea?
> > >> > Thanks
> > >> >
> > >> >
> > >>
> > >>
> > >
> > >
> >
> >
>
>
I have a report with a "Jump to report" navigation field to a second report
, some of the parameters to the second report are DateTime values, when my
Local Settings are setted to English (United States) the link works fine,
but when I change my Local Settings to Spanish I get a Type Mismatch
message for this DateTime parameters. The "Language" property of both
reports are "Default", and when I execute by my self the second report
specifying each parameter with the correct locale datetime format it works
fine.
Any idea?
Thanksthis could happend because of session/caching of the subreport.
Click "Refresh" button on the toolbar when viewing the subreport.
--
This posting is provided "AS IS" with no warranties, and confers no rights.
"Mauricio Cadima" <mcadima@.jalasoft.com> wrote in message
news:uqK6c$2mEHA.404@.TK2MSFTNGP12.phx.gbl...
> Hi
> I have a report with a "Jump to report" navigation field to a second
> report
> , some of the parameters to the second report are DateTime values, when my
> Local Settings are setted to English (United States) the link works fine,
> but when I change my Local Settings to Spanish I get a Type Mismatch
> message for this DateTime parameters. The "Language" property of both
> reports are "Default", and when I execute by my self the second report
> specifying each parameter with the correct locale datetime format it works
> fine.
> Any idea?
> Thanks
>|||Thanks for your answer, but I think that is not the problem.
Let me explain the problem again, I have a first report with two parameters,
"Start Date" and "End Date" that are used when the report is executed to get
some information from some DB for this time range, this information is
showed in a table where the first column values are links to other report
(not a subrerport), this second report also uses date range parameters and
its values should be the same of the first report parameters, this means
that also should be specified in the link.
So when I click the link to open the second report and I have Spanish or
other locale selected for my system regional options a type mismatch message
is showed instead of the second report:
"The value provided for the report parameter 'EndDate' is not valid for its
type. (rsReportParameterTypeMismatch)"
My intuition is that the problem is with the date format, the date format
for Spanish locales is 'dd/mm/yyyy' and for english locale 'mm/dd/yyyy' I
think that the second report is trying to build its date time parameters
with the English locale and here is where the exception is raised. E.g. set
a value greater than 12 as month.
When I execute the second report specifying the parameters values manually
with the correct locale date format the report is showed without problems.
When I see the "Language" property of both reports in design mode is set to
default, I suppose that means that the report should works with the system
locale settings and use the correct date formats.
Thanks
Mauricio
"Lev Semenets [MSFT]" <levs@.microsoft.com> wrote in message
news:e8ju$c4mEHA.648@.tk2msftngp13.phx.gbl...
> this could happend because of session/caching of the subreport.
> Click "Refresh" button on the toolbar when viewing the subreport.
> --
> This posting is provided "AS IS" with no warranties, and confers no
rights.
>
> "Mauricio Cadima" <mcadima@.jalasoft.com> wrote in message
> news:uqK6c$2mEHA.404@.TK2MSFTNGP12.phx.gbl...
> > Hi
> > I have a report with a "Jump to report" navigation field to a second
> > report
> > , some of the parameters to the second report are DateTime values, when
my
> > Local Settings are setted to English (United States) the link works
fine,
> > but when I change my Local Settings to Spanish I get a Type Mismatch
> > message for this DateTime parameters. The "Language" property of both
> > reports are "Default", and when I execute by my self the second report
> > specifying each parameter with the correct locale datetime format it
works
> > fine.
> > Any idea?
> > Thanks
> >
> >
>|||What are parameters values that you pass to second report? What do you put
into Parameter Value cell of Parameters dialog?
--
This posting is provided "AS IS" with no warranties, and confers no rights.
"Mauricio Cadima" <mcadima@.jalasoft.com> wrote in message
news:%23HlTA0AnEHA.3196@.TK2MSFTNGP10.phx.gbl...
> Thanks for your answer, but I think that is not the problem.
>
> Let me explain the problem again, I have a first report with two
> parameters,
> "Start Date" and "End Date" that are used when the report is executed to
> get
> some information from some DB for this time range, this information is
> showed in a table where the first column values are links to other report
> (not a subrerport), this second report also uses date range parameters and
> its values should be the same of the first report parameters, this means
> that also should be specified in the link.
>
> So when I click the link to open the second report and I have Spanish or
> other locale selected for my system regional options a type mismatch
> message
> is showed instead of the second report:
>
> "The value provided for the report parameter 'EndDate' is not valid for
> its
> type. (rsReportParameterTypeMismatch)"
>
> My intuition is that the problem is with the date format, the date format
> for Spanish locales is 'dd/mm/yyyy' and for english locale 'mm/dd/yyyy' I
> think that the second report is trying to build its date time parameters
> with the English locale and here is where the exception is raised. E.g.
> set
> a value greater than 12 as month.
>
> When I execute the second report specifying the parameters values manually
> with the correct locale date format the report is showed without problems.
> When I see the "Language" property of both reports in design mode is set
> to
> default, I suppose that means that the report should works with the system
> locale settings and use the correct date formats.
>
> Thanks
> Mauricio
>
> "Lev Semenets [MSFT]" <levs@.microsoft.com> wrote in message
> news:e8ju$c4mEHA.648@.tk2msftngp13.phx.gbl...
>> this could happend because of session/caching of the subreport.
>> Click "Refresh" button on the toolbar when viewing the subreport.
>> --
>> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>>
>> "Mauricio Cadima" <mcadima@.jalasoft.com> wrote in message
>> news:uqK6c$2mEHA.404@.TK2MSFTNGP12.phx.gbl...
>> > Hi
>> > I have a report with a "Jump to report" navigation field to a second
>> > report
>> > , some of the parameters to the second report are DateTime values, when
> my
>> > Local Settings are setted to English (United States) the link works
> fine,
>> > but when I change my Local Settings to Spanish I get a Type Mismatch
>> > message for this DateTime parameters. The "Language" property of both
>> > reports are "Default", and when I execute by my self the second report
>> > specifying each parameter with the correct locale datetime format it
> works
>> > fine.
>> > Any idea?
>> > Thanks
>> >
>> >
>>
>|||The same values of the first report parameters:
Parameter Name Parameter Value
StartDate =Parameters!StartDate.Value
EndDate =Parameters!EndDate.Value
"Lev Semenets [MSFT]" <levs@.microsoft.com> wrote in message
news:%23uc293FnEHA.3452@.TK2MSFTNGP15.phx.gbl...
> What are parameters values that you pass to second report? What do you put
> into Parameter Value cell of Parameters dialog?
> --
> This posting is provided "AS IS" with no warranties, and confers no
rights.
> "Mauricio Cadima" <mcadima@.jalasoft.com> wrote in message
> news:%23HlTA0AnEHA.3196@.TK2MSFTNGP10.phx.gbl...
> > Thanks for your answer, but I think that is not the problem.
> >
> >
> >
> > Let me explain the problem again, I have a first report with two
> > parameters,
> > "Start Date" and "End Date" that are used when the report is executed to
> > get
> > some information from some DB for this time range, this information is
> > showed in a table where the first column values are links to other
report
> > (not a subrerport), this second report also uses date range parameters
and
> > its values should be the same of the first report parameters, this means
> > that also should be specified in the link.
> >
> >
> >
> > So when I click the link to open the second report and I have Spanish or
> > other locale selected for my system regional options a type mismatch
> > message
> > is showed instead of the second report:
> >
> >
> >
> > "The value provided for the report parameter 'EndDate' is not valid for
> > its
> > type. (rsReportParameterTypeMismatch)"
> >
> >
> >
> > My intuition is that the problem is with the date format, the date
format
> > for Spanish locales is 'dd/mm/yyyy' and for english locale 'mm/dd/yyyy'
I
> > think that the second report is trying to build its date time parameters
> > with the English locale and here is where the exception is raised. E.g.
> > set
> > a value greater than 12 as month.
> >
> >
> >
> > When I execute the second report specifying the parameters values
manually
> > with the correct locale date format the report is showed without
problems.
> > When I see the "Language" property of both reports in design mode is set
> > to
> > default, I suppose that means that the report should works with the
system
> > locale settings and use the correct date formats.
> >
> >
> >
> > Thanks
> >
> > Mauricio
> >
> >
> >
> > "Lev Semenets [MSFT]" <levs@.microsoft.com> wrote in message
> > news:e8ju$c4mEHA.648@.tk2msftngp13.phx.gbl...
> >> this could happend because of session/caching of the subreport.
> >> Click "Refresh" button on the toolbar when viewing the subreport.
> >>
> >> --
> >> This posting is provided "AS IS" with no warranties, and confers no
> > rights.
> >>
> >>
> >> "Mauricio Cadima" <mcadima@.jalasoft.com> wrote in message
> >> news:uqK6c$2mEHA.404@.TK2MSFTNGP12.phx.gbl...
> >> > Hi
> >> > I have a report with a "Jump to report" navigation field to a second
> >> > report
> >> > , some of the parameters to the second report are DateTime values,
when
> > my
> >> > Local Settings are setted to English (United States) the link works
> > fine,
> >> > but when I change my Local Settings to Spanish I get a Type Mismatch
> >> > message for this DateTime parameters. The "Language" property of both
> >> > reports are "Default", and when I execute by my self the second
report
> >> > specifying each parameter with the correct locale datetime format it
> > works
> >> > fine.
> >> > Any idea?
> >> > Thanks
> >> >
> >> >
> >>
> >>
> >
> >
>|||I have having the very same problem. Did you ever solve this? And how
if you did?!
Thanks|||I have this problem as well, even though my report language is set to English
(United Kingdom), my Asp.Net app that calls the reporting service web service
is using en-GB as culture. It still thinks that my parameter End Date should
be in mm/dd/yyyy format and pukes when it sees something like 14/12/2004
(December 14, 2004) come over.
"Gearoid" wrote:
> I have having the very same problem. Did you ever solve this? And how
> if you did?!
> Thanks
>|||Adam,
Check the "Language Settings" for your browser.
Open IE, goto Tools->Internet Options->Click 'Languages...' button on the
General tab. Check that your language is English (United Kingdom)
I have got MSRS to work fine with UK English format dates... apart from
when reports are linked using 'Jump to' action.
Joe
"AdamB" wrote:
> I have this problem as well, even though my report language is set to English
> (United Kingdom), my Asp.Net app that calls the reporting service web service
> is using en-GB as culture. It still thinks that my parameter End Date should
> be in mm/dd/yyyy format and pukes when it sees something like 14/12/2004
> (December 14, 2004) come over.
> "Gearoid" wrote:
> > I have having the very same problem. Did you ever solve this? And how
> > if you did?!
> >
> > Thanks
> >
> >|||Try this and see if it works
Parameter Name Parameter Value
StartDate =Format(Parameters!StartDate.Value,
"dd-MMMM-yyyy")
EndDate =Format(Parameters!EndDate.Value,
"dd-MMMM-yyyy")
Cheers,
Harry
"Mauricio Cadima" wrote:
> The same values of the first report parameters:
> Parameter Name Parameter Value
> StartDate =Parameters!StartDate.Value
> EndDate =Parameters!EndDate.Value
> "Lev Semenets [MSFT]" <levs@.microsoft.com> wrote in message
> news:%23uc293FnEHA.3452@.TK2MSFTNGP15.phx.gbl...
> > What are parameters values that you pass to second report? What do you put
> > into Parameter Value cell of Parameters dialog?
> >
> > --
> > This posting is provided "AS IS" with no warranties, and confers no
> rights.
> >
> > "Mauricio Cadima" <mcadima@.jalasoft.com> wrote in message
> > news:%23HlTA0AnEHA.3196@.TK2MSFTNGP10.phx.gbl...
> > > Thanks for your answer, but I think that is not the problem.
> > >
> > >
> > >
> > > Let me explain the problem again, I have a first report with two
> > > parameters,
> > > "Start Date" and "End Date" that are used when the report is executed to
> > > get
> > > some information from some DB for this time range, this information is
> > > showed in a table where the first column values are links to other
> report
> > > (not a subrerport), this second report also uses date range parameters
> and
> > > its values should be the same of the first report parameters, this means
> > > that also should be specified in the link.
> > >
> > >
> > >
> > > So when I click the link to open the second report and I have Spanish or
> > > other locale selected for my system regional options a type mismatch
> > > message
> > > is showed instead of the second report:
> > >
> > >
> > >
> > > "The value provided for the report parameter 'EndDate' is not valid for
> > > its
> > > type. (rsReportParameterTypeMismatch)"
> > >
> > >
> > >
> > > My intuition is that the problem is with the date format, the date
> format
> > > for Spanish locales is 'dd/mm/yyyy' and for english locale 'mm/dd/yyyy'
> I
> > > think that the second report is trying to build its date time parameters
> > > with the English locale and here is where the exception is raised. E.g.
> > > set
> > > a value greater than 12 as month.
> > >
> > >
> > >
> > > When I execute the second report specifying the parameters values
> manually
> > > with the correct locale date format the report is showed without
> problems.
> > > When I see the "Language" property of both reports in design mode is set
> > > to
> > > default, I suppose that means that the report should works with the
> system
> > > locale settings and use the correct date formats.
> > >
> > >
> > >
> > > Thanks
> > >
> > > Mauricio
> > >
> > >
> > >
> > > "Lev Semenets [MSFT]" <levs@.microsoft.com> wrote in message
> > > news:e8ju$c4mEHA.648@.tk2msftngp13.phx.gbl...
> > >> this could happend because of session/caching of the subreport.
> > >> Click "Refresh" button on the toolbar when viewing the subreport.
> > >>
> > >> --
> > >> This posting is provided "AS IS" with no warranties, and confers no
> > > rights.
> > >>
> > >>
> > >> "Mauricio Cadima" <mcadima@.jalasoft.com> wrote in message
> > >> news:uqK6c$2mEHA.404@.TK2MSFTNGP12.phx.gbl...
> > >> > Hi
> > >> > I have a report with a "Jump to report" navigation field to a second
> > >> > report
> > >> > , some of the parameters to the second report are DateTime values,
> when
> > > my
> > >> > Local Settings are setted to English (United States) the link works
> > > fine,
> > >> > but when I change my Local Settings to Spanish I get a Type Mismatch
> > >> > message for this DateTime parameters. The "Language" property of both
> > >> > reports are "Default", and when I execute by my self the second
> report
> > >> > specifying each parameter with the correct locale datetime format it
> > > works
> > >> > fine.
> > >> > Any idea?
> > >> > Thanks
> > >> >
> > >> >
> > >>
> > >>
> > >
> > >
> >
> >
>
>
Labels:
database,
datetime,
field,
jump,
localization,
microsoft,
mysql,
navigation,
oracle,
parameters,
report,
second,
server,
sql,
values
Subscribe to:
Posts (Atom)