updated to crystal 2008, get error message

[Kellys19]

Failed to retrieve data from the database.
Details: 07002:[Microsoft][ODBC Microsoft Access Driver] Too few parameters. Expected 1. [Database Vendor Code: -3010]

Anyone got an answer for this one? Help please!

Kelly

 

[boblarson]

Sounds like you are trying to get information from a query which has a parameter on it. Is that the case?

 

[Kellys19]

No, it is just a table. But it does have columns that reference other tables. I didn't have a problem with Crystal 10. Only since the upgrade to 2008.

 

[boblarson]

No, it is just a table. But it does have columns that reference other tables. I didn't have a problem with Crystal 10. Only since the upgrade to 2008.

The database should not have lookups defined at table level. That is a big Access database no, no. I fear that because of that you are going to have continued issues. They should not be set at table level but instead used on forms. See here for more about that.

 

[Kellys19]

Yes, I did have an issue with those tables in Crystal v 10, but I managed to fix it. Now it seems it is back. Darn it. Thanks for the info.

 

[angle222]

I have been working a lot with Crystal Reports XI lately. I am writing a report that will use multiple stored procedures(as in about 25.....is that a WTF itself?). I noticed that my stored procedure didn't contain all the information that I needed, so I edited the stored procedure in SQL Server 2005. To make Crystal Reports get the new updated version of the stored procedure, I did the "Verify Database". I was then prompted with this very informative "error" message.

 

[boblarson]

I have been working a lot with Crystal Reports XI lately. I am writing a report that will use multiple stored procedures(as in about 25.....is that a WTF itself?). I noticed that my stored procedure didn't contain all the information that I needed, so I edited the stored procedure in SQL Server 2005. To make Crystal Reports get the new updated version of the stored procedure, I did the "Verify Database". I was then prompted with this very informative "error" message.

Are you using OLE DB connection to the SQL Server or are you using ODBC? If using ODBC are you using the SQL Native Client driver and NOT the SQL Server driver?