ODBC Error: Invalid Column Name :: Error detected by database DLL

[tdiboll]

I download a report and set up the database location. When I go to access report information, I get an error message that says ODBC Error ODBC Sql Server Driver: Invalid Column name. currency_id

If I look at the table of the information that I am pulling the material from the column name is there. Where can I go to or how can I resolve this issue.

thanks,

 

[Turkbear]

Hi,
with the report open in CR, choose the Database..Verify Database option and see what happens..

 

[tdiboll]

Message came up that database is up to date.

 

[Turkbear]

Hi,
And after that it still gave the error?

Odd..

 

[tdiboll]

It is racking my brain. I looked in my report and do not see where the currency id could be tied up with.

 

[synapsevampire]

Export the report to a Report Definition File and then do a search of the resultant text file.

Also check for subreports (the export will include them).

-k

 

[tdiboll]

There are no subreports in my report. This is a customer ranking report by gp.

My software company is telling me it is a billable service which I think is bogus. When I try to create the same report from scratch, it still comes up the the invalid column name error.

 

[dgillz]

You can see the column in SQL but not in crystal?

Software Sales, Training, Implementation and Support for Exact Macola, eSynergy, and Crystal Reports
askdon@srhconsulting.com

http://www.srhconsulting.com

 

[tdiboll]

The column name is there. It is not being used in my report. When I drill down in the Field Explorer and expand my table, the currency_id is there. I used this report a year ago for my end year reports. In that year, I have done two software upgrades.

 

[synapsevampire]

Had you tried what I suggested?

There will be no ambiguity, if the field exists in the report, it will be in the report definition file (unless they've manually edited the SQL, check under Database->Show SQL Query).

-k

 

[tdiboll]

I figured out my problem. Thank all of you for your time.

 

[vidru]

Can you post your solution, so if someone has a similar problem in the future, they can benefit from your experience?

-dave

 

[dchant]

Am also getting "Error Detected by Database DLL" intermittently in Crystal Enterprise v8.5.

Would be helpful if you post your solution.

Thks

 

[powersro]

tdiboll, I have the same problem. How did you resolve it?

Thanks

 

[kskid]

I use CR 8.5 and I was running into the same problem. In my case, I was testing the report against an updated Oracle table that was made by our software vendor.

I did "Verify Database" and it did show the formulas and record selections where the fields were no longer valid and I made the necessary corrections. However, when I ran the report I got the Invalid column error (of course, with Windows XP, it just exits Crystal Report altogether).

I went back in and reverified the database and everything came back Up-to-date but still got the error. I took me from 7:30 this morning until now to find the little bugger. As Snapsevampire suggested, I finally created a Report Definition and started going through it line by line and that's where I found it. As it turns out, it appears that Verify Database does not look at any modifications that I made in the SQL Query (i.e. Database->Show SQL Query) when I first created the report.

Hope this helps some of you.

Would the same thing happen with the Add Command or SQL expressions?

-LW