"bhc" <bhc@discussions.microsoft.com> wrote in message
news:46E4343F-8FB0-4F09-A582-D7A3F5E9AF0A@microsoft.com...
> Yes, I have tried using just the generic query designer (that's what I'm
> used
> from RS 2000). It is the generic query designer where I'm having all the
> problems. It's very unreadable and does not parse when MySQL functions
> are
> used in the query even if the generic query designer is the only pane
> displayed. The properties on Query Designer are as follows:
> Distinct Values = No
> Output All Columns= No
> Query Parameter Identification = [nothing here]
> Query Parameter List = [greyed out, no parameters specified]
>
> Thoughts?
> bhc
>
> "Bruce L-C [MVP]" wrote:
>
>> Have you tried going to the generic query designer? I have no doubt you
>> are
>> seeing these problems in the 4 pane graphical query designer. What
>> happens
>> if you switch over to the generic query designer.
>>
>>
>> --
>> Bruce Loehle-Conger
>> MVP SQL Server Reporting Services
>>
>> "bhc" <bhc@discussions.microsoft.com> wrote in message
>> news:ABF940A7-4625-4F04-8A88-D26B05E8B78B@microsoft.com...
>> >I get the following after converting to the new report definition format
>> >when
>> > I access the Data tab:
>> > Error in SELECT clause: alias not recognized.
>> > Error in list of function arguments: 'DataCenter' not recognized.
>> > Error in list of function arguments: ',' not recognized.
>> > Error in list of function arguments: '<' not recognized.
>> > Error in list of function arguments: 'out_month' not recognized.
>> > Unable to parse query text.
>> >
>> > If I let things load in the multi-pane view and use the Verify SQL
>> > button,
>> > a
>> > Microsoft Visual Database Tools window pops up with "The command is not
>> > supported by this provider".
>> >
>> > Having reviewed a few of my report queries facing this issue, I notice
>> > problems only with queries using native MySQL functions, such as
>> > date/time
>> > conversions. All functions have been encapsulated by single quotes, so
>> > instead of 60-SECOND(A.TIMESTAMP), I now have to contend with
>> > 60-'SECOND'(A.TIMESTAMP). Any attempts to remove them are futile; they
>> > simply get inserted when I go to verify the SQL or move out of the
>> > Query
>> > text
>> > pane. Though I get the above errors on other MySQL queries, I am still
>> > able
>> > to run ones without functions in them.
>> >
>> > Is there any way to configure RS to stop doing this? This is just
>> > nasty.
>> > Thanks.
>> > bhc
>> >
>> > "Bruce L-C [MVP]" wrote:
>> >
>> >> Have you tried using the generic query designer (2 panes instead of
>> >> 4). I
>> >> should leave it a alone. It is one of the buttons to the right of the
>> >> ...
>> >> to
>> >> switch to it).
>> >>
>> >>
>> >> --
>> >> Bruce Loehle-Conger
>> >> MVP SQL Server Reporting Services
>> >>
>> >> "bhc" <bhc@discussions.microsoft.com> wrote in message
>> >> news:40DB9C60-A240-4B6E-9020-E79DEBEA613A@microsoft.com...
>> >> > Yikes! I have upgraded to SQL Server 2005 Developer Edition,
>> >> > including
>> >> > the
>> >> > RS upgrade. The ReportServer and reports all came over and are
>> >> > running
>> >> > fabulously well. However, strange things are happening with my
>> >> > queries
>> >> > in
>> >> > Intelligence Studio (and VS Studio 2005, I've tried both) after
>> >> > being
>> >> > converted to the new report definition format. My extensive queries
>> >> > have
>> >> > been reformatted predominantly as straight-text (very unreadable)
>> >> > and
>> >> > my
>> >> > queries no longer pass SQL verification.
>> >> >
>> >> > I tried retrieving the well-formatted queries from local text file
>> >> > backups,
>> >> > but the new designer continues to reformat it as straight-text.
>> >> >
>> >> > What can I do to get the following format in my queries:
>> >> > Select A,
>> >> > B,
>> >> > C (as string),
>> >> > D
>> >> > From TableA
>> >> > Where [clause]
>> >> >
>> >> > I'm querying against a MySQL 4.0 database with MyODBC 3.5.1 driver.
>> >> >
>> >> > Thanks.
>> >> > bhc
>> >>
>> >>
>> >>
>>
>>
>>

"Bruce L-C [MVP]" <bruce_lcNOSPAM@hotmail.com> wrote in message
news:%238%23y%23UW5FHA.724@TK2MSFTNGP14.phx.gbl...
>I am in the process of upgrading and testing all my reports. I will look at
>some of the more complex ones that go against Sybase and see how it works.
>I'll let you know.
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
>
>
> "bhc" <bhc@discussions.microsoft.com> wrote in message
> news:46E4343F-8FB0-4F09-A582-D7A3F5E9AF0A@microsoft.com...
>> Yes, I have tried using just the generic query designer (that's what I'm
>> used
>> from RS 2000). It is the generic query designer where I'm having all the
>> problems. It's very unreadable and does not parse when MySQL functions
>> are
>> used in the query even if the generic query designer is the only pane
>> displayed. The properties on Query Designer are as follows:
>> Distinct Values = No
>> Output All Columns= No
>> Query Parameter Identification = [nothing here]
>> Query Parameter List = [greyed out, no parameters specified]
>>
>> Thoughts?
>> bhc
>>
>> "Bruce L-C [MVP]" wrote:
>>
>>> Have you tried going to the generic query designer? I have no doubt you
>>> are
>>> seeing these problems in the 4 pane graphical query designer. What
>>> happens
>>> if you switch over to the generic query designer.
>>>
>>>
>>> --
>>> Bruce Loehle-Conger
>>> MVP SQL Server Reporting Services
>>>
>>> "bhc" <bhc@discussions.microsoft.com> wrote in message
>>> news:ABF940A7-4625-4F04-8A88-D26B05E8B78B@microsoft.com...
>>> >I get the following after converting to the new report definition
>>> >format
>>> >when
>>> > I access the Data tab:
>>> > Error in SELECT clause: alias not recognized.
>>> > Error in list of function arguments: 'DataCenter' not recognized.
>>> > Error in list of function arguments: ',' not recognized.
>>> > Error in list of function arguments: '<' not recognized.
>>> > Error in list of function arguments: 'out_month' not recognized.
>>> > Unable to parse query text.
>>> >
>>> > If I let things load in the multi-pane view and use the Verify SQL
>>> > button,
>>> > a
>>> > Microsoft Visual Database Tools window pops up with "The command is
>>> > not
>>> > supported by this provider".
>>> >
>>> > Having reviewed a few of my report queries facing this issue, I notice
>>> > problems only with queries using native MySQL functions, such as
>>> > date/time
>>> > conversions. All functions have been encapsulated by single quotes,
>>> > so
>>> > instead of 60-SECOND(A.TIMESTAMP), I now have to contend with
>>> > 60-'SECOND'(A.TIMESTAMP). Any attempts to remove them are futile;
>>> > they
>>> > simply get inserted when I go to verify the SQL or move out of the
>>> > Query
>>> > text
>>> > pane. Though I get the above errors on other MySQL queries, I am
>>> > still
>>> > able
>>> > to run ones without functions in them.
>>> >
>>> > Is there any way to configure RS to stop doing this? This is just
>>> > nasty.
>>> > Thanks.
>>> > bhc
>>> >
>>> > "Bruce L-C [MVP]" wrote:
>>> >
>>> >> Have you tried using the generic query designer (2 panes instead of
>>> >> 4). I
>>> >> should leave it a alone. It is one of the buttons to the right of the
>>> >> ...
>>> >> to
>>> >> switch to it).
>>> >>
>>> >>
>>> >> --
>>> >> Bruce Loehle-Conger
>>> >> MVP SQL Server Reporting Services
>>> >>
>>> >> "bhc" <bhc@discussions.microsoft.com> wrote in message
>>> >> news:40DB9C60-A240-4B6E-9020-E79DEBEA613A@microsoft.com...
>>> >> > Yikes! I have upgraded to SQL Server 2005 Developer Edition,
>>> >> > including
>>> >> > the
>>> >> > RS upgrade. The ReportServer and reports all came over and are
>>> >> > running
>>> >> > fabulously well. However, strange things are happening with my
>>> >> > queries
>>> >> > in
>>> >> > Intelligence Studio (and VS Studio 2005, I've tried both) after
>>> >> > being
>>> >> > converted to the new report definition format. My extensive
>>> >> > queries
>>> >> > have
>>> >> > been reformatted predominantly as straight-text (very unreadable)
>>> >> > and
>>> >> > my
>>> >> > queries no longer pass SQL verification.
>>> >> >
>>> >> > I tried retrieving the well-formatted queries from local text file
>>> >> > backups,
>>> >> > but the new designer continues to reformat it as straight-text.
>>> >> >
>>> >> > What can I do to get the following format in my queries:
>>> >> > Select A,
>>> >> > B,
>>> >> > C (as string),
>>> >> > D
>>> >> > From TableA
>>> >> > Where [clause]
>>> >> >
>>> >> > I'm querying against a MySQL 4.0 database with MyODBC 3.5.1 driver.
>>> >> >
>>> >> > Thanks.
>>> >> > bhc
>>> >>
>>> >>
>>> >>
>>>
>>>
>>>
>
>

"Bruce L-C [MVP]" wrote:

> The way the generic query designer works for me is it leaves everything
> exactly the way I type it in. If it has been in the graphical designer it
> can get munged up. If you clean it up it should work for you.
>
> The properties you mentioned, I don't see anyplace to see these properties?
> Where are you seeing them?
>
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
>
>
> "Bruce L-C [MVP]" <bruce_lcNOSPAM@hotmail.com> wrote in message
> news:%238%23y%23UW5FHA.724@TK2MSFTNGP14.phx.gbl...
> >I am in the process of upgrading and testing all my reports. I will look at
> >some of the more complex ones that go against Sybase and see how it works.
> >I'll let you know.
> >
> > --
> > Bruce Loehle-Conger
> > MVP SQL Server Reporting Services
> >
> >
> > "bhc" <bhc@discussions.microsoft.com> wrote in message
> > news:46E4343F-8FB0-4F09-A582-D7A3F5E9AF0A@microsoft.com...
> >> Yes, I have tried using just the generic query designer (that's what I'm
> >> used
> >> from RS 2000). It is the generic query designer where I'm having all the
> >> problems. It's very unreadable and does not parse when MySQL functions
> >> are
> >> used in the query even if the generic query designer is the only pane
> >> displayed. The properties on Query Designer are as follows:
> >> Distinct Values = No
> >> Output All Columns= No
> >> Query Parameter Identification = [nothing here]
> >> Query Parameter List = [greyed out, no parameters specified]
> >>
> >> Thoughts?
> >> bhc
> >>
> >> "Bruce L-C [MVP]" wrote:
> >>
> >>> Have you tried going to the generic query designer? I have no doubt you
> >>> are
> >>> seeing these problems in the 4 pane graphical query designer. What
> >>> happens
> >>> if you switch over to the generic query designer.
> >>>
> >>>
> >>> --
> >>> Bruce Loehle-Conger
> >>> MVP SQL Server Reporting Services
> >>>
> >>> "bhc" <bhc@discussions.microsoft.com> wrote in message
> >>> news:ABF940A7-4625-4F04-8A88-D26B05E8B78B@microsoft.com...
> >>> >I get the following after converting to the new report definition
> >>> >format
> >>> >when
> >>> > I access the Data tab:
> >>> > Error in SELECT clause: alias not recognized.
> >>> > Error in list of function arguments: 'DataCenter' not recognized.
> >>> > Error in list of function arguments: ',' not recognized.
> >>> > Error in list of function arguments: '<' not recognized.
> >>> > Error in list of function arguments: 'out_month' not recognized.
> >>> > Unable to parse query text.
> >>> >
> >>> > If I let things load in the multi-pane view and use the Verify SQL
> >>> > button,
> >>> > a
> >>> > Microsoft Visual Database Tools window pops up with "The command is
> >>> > not
> >>> > supported by this provider".
> >>> >
> >>> > Having reviewed a few of my report queries facing this issue, I notice
> >>> > problems only with queries using native MySQL functions, such as
> >>> > date/time
> >>> > conversions. All functions have been encapsulated by single quotes,
> >>> > so
> >>> > instead of 60-SECOND(A.TIMESTAMP), I now have to contend with
> >>> > 60-'SECOND'(A.TIMESTAMP). Any attempts to remove them are futile;
> >>> > they
> >>> > simply get inserted when I go to verify the SQL or move out of the
> >>> > Query
> >>> > text
> >>> > pane. Though I get the above errors on other MySQL queries, I am
> >>> > still
> >>> > able
> >>> > to run ones without functions in them.
> >>> >
> >>> > Is there any way to configure RS to stop doing this? This is just
> >>> > nasty.
> >>> > Thanks.
> >>> > bhc
> >>> >
> >>> > "Bruce L-C [MVP]" wrote:
> >>> >
> >>> >> Have you tried using the generic query designer (2 panes instead of
> >>> >> 4). I
> >>> >> should leave it a alone. It is one of the buttons to the right of the
> >>> >> ...
> >>> >> to
> >>> >> switch to it).
> >>> >>
> >>> >>
> >>> >> --
> >>> >> Bruce Loehle-Conger
> >>> >> MVP SQL Server Reporting Services
> >>> >>
> >>> >> "bhc" <bhc@discussions.microsoft.com> wrote in message
> >>> >> news:40DB9C60-A240-4B6E-9020-E79DEBEA613A@microsoft.com...
> >>> >> > Yikes! I have upgraded to SQL Server 2005 Developer Edition,
> >>> >> > including
> >>> >> > the
> >>> >> > RS upgrade. The ReportServer and reports all came over and are
> >>> >> > running
> >>> >> > fabulously well. However, strange things are happening with my
> >>> >> > queries
> >>> >> > in
> >>> >> > Intelligence Studio (and VS Studio 2005, I've tried both) after
> >>> >> > being
> >>> >> > converted to the new report definition format. My extensive
> >>> >> > queries
> >>> >> > have
> >>> >> > been reformatted predominantly as straight-text (very unreadable)
> >>> >> > and
> >>> >> > my
> >>> >> > queries no longer pass SQL verification.
> >>> >> >
> >>> >> > I tried retrieving the well-formatted queries from local text file
> >>> >> > backups,
> >>> >> > but the new designer continues to reformat it as straight-text.
> >>> >> >
> >>> >> > What can I do to get the following format in my queries:
> >>> >> > Select A,
> >>> >> > B,
> >>> >> > C (as string),
> >>> >> > D
> >>> >> > From TableA
> >>> >> > Where [clause]
> >>> >> >
> >>> >> > I'm querying against a MySQL 4.0 database with MyODBC 3.5.1 driver.
> >>> >> >
> >>> >> > Thanks.
> >>> >> > bhc
> >>> >>
> >>> >>
> >>> >>
> >>>
> >>>
> >>>
> >
> >
>
>