CR 8.5 using MyODBC(any version) not retrieving data 2

[topjimmie]

I have several reports built with CR 8.5 connecting to a MySQL database ver. 4.0.1 using MyODBC (2.5 or 3.51 same result).
These reports worked prior to me reinstalling myODBC on my pc.
Since I have reinstalled, I have setup exact same MyODBC DSN as the report used previously.
Now when I try to open the reports, I retrieve no records. In troubleshooting I found that I could "browse" data for each field, and it did present the right data, but just would not retrieve any of these fields in the report itself.
This lead me to look at the SQL query that the report had built. Herein lies the problem I think. After each table name, CR has inserted a "1". Same as if I had assigned an alias to the tables. (but I didn't of course).
I double checked for multiple Open ODBC connections that might necessitate an alias from CR, but nothing there.
I can't change it. I have tried adding an alias for each table, then deleting it. It simply appends my alias to the one it initiated. I have edited the query directly, but it reverts back.
This is happening to about 8 reports in total (all of them).
Is there anyone that knows the answer?
Thanks in advance, I'm really stuck on this one.
Jimmie

 

[synapsevampire]

Did you run Database->Verify Database?

Did ou try using Database->Set Location and pointing to one of the tables again and propagating the changes?

-k

 

[topjimmie]

Thanks Synapse, I did do those things. I have figured out a fix for the problem, but certainly not WHY it occured in the first place. After verifying that the ODBC connection itself was not the problem, I began deconstructing the report. What I found in my record selection formula was that I was selecting on a numeric field, but put "totext" for some reason when I was building these. That used to work. I changed this formula to look for the few numeric values AS numeric, and now everything works again.
Example (not working):
totext({table.field}) IN ['10', '12', '14']
Example (working):
{table.field} IN [10, 12, 14]
I don't get it...I'm sure I had a reason at the time, but don't know what it is now. Either way, it was working that way before, and now is not. Wish I knew what the difference is.
Thanks again
Jimmie

 

[kskid]

Maybe the DBA made a table change from text to numeric?

 

[topjimmie]

Thanks wichitakid, I have been focused on CR and ODBC being the culprit...never did consider that the database structure might have changed. Will look into that.
Problem itself is fixed now. Will keep trying to find what caused it and post the answer when I figure it out.
Jimmie