× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



In response to Paul, management has given the direction to convert from
NGS-IQ to reporting services. Another application is not in the
picture. Looking at the price for Sequel, it certainly is not in the
picture.

In response to John, thanks for the info on the Date Function & can I
use the .Net provider within Reporting Services (BIDS)?

If so, where & how, or maybe provide a link to some info that I could
read & I definitely would appreciate the info.

Thanks.
James Salter
Systems Programmer
American Cast Iron Pipe Company
phone (205) 325-3033
fax (205) 307-3833



from: "Paul Nelson" <nelsonp@xxxxxxxxxxxxx>
subject: RE: ODBC Parameter Passing for Reporting Services

Have you looked at SEQUEL from HelpSystems? Piece of cake, without the
overhead of ODBC

Paul Nelson
Office 512-392-2577
Cell 708-670-6978
nelsonp@xxxxxxxxxxxxx


from: "John Taylor" <lists@xxxxxxxxxxxxxxxxxxxx>
subject: RE: ODBC Parameter Passing for Reporting Services



-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-
bounces@xxxxxxxxxxxx] On Behalf Of Salter, James
I am running into some problems trying to create parameters for
Reporting Services.

My SQL statement looks something like this - select ... from ....
where
item = ?

This does create a Parameter called Parameter1, however how do you
code
it to get all possible values for all items?

I can use the "LIKE %" syntax, however this does not really give me
the
chance to enter and retrieve an exact value.

I don't understand what you are trying to do. Are you trying to create a
drop-down list parameter of all possible values, or are you trying to
create
a parameter that allows a specific item number or blanks for "all"
products?

Not surprisingly, Microsoft really doesn't support ODBC as well as
they
should.


Why aren't you using the IBM .NET provider?


Also, if you have any tricks for converting the DateTime parameter to
MMDDYY or CCYYMMDD formats, feel free to include these as well.

Don't convert DateTime to match the database column. Do it the other way
around. You can use the SQL DATE() function to convert your CCYYMMDD
field
to a true date field that will allow a direct comparison against
DateTime.
_________Confidentiality Notice_______________________
This e-mail and any files transmitted with it is
confidential and is intended solely for the use of
the individual(s) or entity(ies) to whom this e-mail
is addressed. If you are not the intended recipient
or the person responsible for delivering the e-mail
to the intended recipient, be advised that you have
received this e-mail in error, and that any use,
disclosure, dissemination, forwarding, printing,
retention or copying of this e-mail is strictly
prohibited. If you have received this e-mail in
error, please immediately return this e-mail to
the sender and delete the e-mail from your system.
Thank you.


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.