Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

 All Forums
 Development Tools
 ASP.NET
 Failed to Open Rowset ERROR in CR

Author  Topic 

BigRetina
Posting Yak Master

144 Posts

Posted - 2002-10-24 : 03:14:17
Salute..
what could casue the following error in Crystal Reports.NET
Failed to Open Rowset..??
I get the error with some reports and not with others!..all are the same basically!!
This happens when deploying on Win98..on Win2K everything works fine!.

Thanks



Edited by - BigRetina on 10/24/2002 03:41:27

robvolk
Most Valuable Yak

15732 Posts

Posted - 2002-10-24 : 07:45:27
Some typical problems with Win98:

A. The MDAC components might need to be updated (2.6 or better). Get the latest here:

http://www.microsoft.com/data/download.htm

B. The Win98 machine cannot connect using named pipes networking; the connection may be attempting to do so. Check to make sure the SQL Server and the client computers are configured to use TCP/IP as the default, and check the connection string for the reports to make sure it specifies a TCP/IP connection.

HTH

Go to Top of Page

BigRetina
Posting Yak Master

144 Posts

Posted - 2002-10-27 : 11:39:42
I discovered an IMPORTANT THING

The ERROR I get when I run the program from Win98 is "Failed To Open Rowset" .. This
error take place when the STORED PROCEDURE that the report is connected to via oledb has datetime or smalldatetime input paramters!...regardless HOW i fill the paramters!
Another thing..everything works fine from Win2000 professional!!
what could be the problem?..please help me!!

Go to Top of Page

BigRetina
Posting Yak Master

144 Posts

Posted - 2002-10-28 : 05:15:20
The stored procedure is as follows:
ALTER PROCEDURE rptTst( @FromDate smalldatetime, @ToDate smalldatetime)
AS
SET NOCOUNT ON
SELECT ChequeId from InwardCheques
WHERE IssuingDate BETWEEN @FromDate AND @ToDate

THAT IS IT!!!!!..

The code block that set's the paramters is as follows:

M_Rpt = New tstRpt()
Me.prmDiscValue = New ParameterDiscreteValue()
Me.prmField = New ParameterField()
Me.prmField.ParameterFieldName = "@FromDate"
Me.prmDiscValue.Value = CDate("1/1/1900")
Me.prmField.CurrentValues.Add(Me.prmDiscValue)
Me.prmFields.Add(Me.prmField)

Me.prmDiscValue = New ParameterDiscreteValue()
Me.prmField = New ParameterField()
Me.prmField.ParameterFieldName = "@ToDate"
Me.prmDiscValue.Value = CDate("1/1/2050")
Me.prmField.CurrentValues.Add(Me.prmDiscValue)
Me.prmFields.Add(Me.prmField)

Me.crvMain.ParameterFieldInfo = Me.prmFields
Me.crvMain.ReportSource = M_Rpt

so what do u think?




Go to Top of Page

nr
SQLTeam MVY

12543 Posts

Posted - 2002-10-28 : 06:19:13
You could try setting the parameter type to smalldatetime.

==========================================
Cursors are useful if you don't know sql.
DTS can be used in a similar way.
Beer is not cold and it isn't fizzy.
Go to Top of Page

BigRetina
Posting Yak Master

144 Posts

Posted - 2002-10-28 : 10:36:58
Sorry..I didnt get you..they are already smalldatetime in the stored procedure!!
First of all..THANKS ALOT for trying to help me, I really appreciate it!
BUT..a BIGGER surprise is that I overrode the paramter values WITHIN the stored procedure and the problem presisted!!.The stored procedure is now as follows :

ALTER PROCEDURE RptTst(@FromDate smalldatetime,@ToDate smalldatetime)
AS
SET NOCOUNT ON
SET @ToDate = '1/1/2050'
SET @FromDate = '1/1/1900'
SELECT ChequeId
FROM InwardCheques
WHERE IssuingDate BETWEEN @FromDate AND @ToDate

It seems that the problem is in the PASSING of the paramters..again..it worked
fine in Win2k but NOT in Win98
Thanks Again For the Effor


Go to Top of Page
   

- Advertisement -