Amour22015
asked on
MS Access 2010 - Required data provider properties could not be set
Hi Experts,
I have a MS Access 2010 Report that is using a Stored Procedure from SQL Server 2008R2
When I try the Report in View Mode I get an error:
"Required data provider properties could not be set"
any idea's what maybe causing this. I just changed the: Access Options>Client Settings>Advanced
to OKE/DDE timeout (sec) to 99,999 so that this does not timeOut.
Thanks.
I have a MS Access 2010 Report that is using a Stored Procedure from SQL Server 2008R2
When I try the Report in View Mode I get an error:
"Required data provider properties could not be set"
any idea's what maybe causing this. I just changed the: Access Options>Client Settings>Advanced
to OKE/DDE timeout (sec) to 99,999 so that this does not timeOut.
Thanks.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I changed to what you mentioned "0" and now it is back to timing out.
So at least the error is gone
So at least the error is gone
What provider are you using or how are you calling the stored procedure?
Jim.
Jim.
ASKER
I am calling the SP on: "Record Source" = Stored Procedure.
On the SQL Server side that SP takes about 2 mins to run.
On the MS Access Report it is a simple report with one subreport as a Report header which only has Company Logo and address.
I am new to all this so:
What do you mean provider? and how do I find what provider?
Thanks
On the SQL Server side that SP takes about 2 mins to run.
On the MS Access Report it is a simple report with one subreport as a Report header which only has Company Logo and address.
I am new to all this so:
What do you mean provider? and how do I find what provider?
Thanks
ASKER
I set the time out to 300 and it seems to work fine. But on the SQL Server side taking about 2 mins seems to long.
ASKER
Thanks for your help
<<What do you mean provider? and how do I find what provider?>>
Using an ADP then...
<<But on the SQL Server side taking about 2 mins seems to long. >>
Two minutes does sound like a very long time for anything, but then it depends on what procedure is doing, size of the tables, indexing, etc.
Jim.
Using an ADP then...
<<But on the SQL Server side taking about 2 mins seems to long. >>
Two minutes does sound like a very long time for anything, but then it depends on what procedure is doing, size of the tables, indexing, etc.
Jim.
ASKER
But I am getting the same error.
Thanks