More than one database driver has been used in this report

[GotFish]

I am getting a message "More than one database driver has been used in this report. If you want to change the datbase driver use Database set/location. Also, please make sure that no SQL expression is added and no server-side group-by is performed" in version 8.5. what I am doing is linking a third party vendors prefab crystal, and modifying it, to add 3 SQL Server 2000 table (also theirs) to it, to get the data we want. I have before linked in SQL tables to their visual foxpro tables with no problem, and don't know why, all of a sudden, I am getting this message on this one. I am not doing any server side grouping, and it goes ahead, and lets me add and link the table with an EQUAL join, but does not link any records in on keys I know exist. When the keys exist, and crystal doesn't recognize them, should it drop the whole record, when ALL links are equal joins? It leaves the data as is (before the SQL table was linked in) as if the table asn't even there. Help!!!!!

Has anyone seen my other sock?

 

[synapsevampire]

I guess that you mean that you're taking one of their (prefab crystal) reports and adding more of their tables?

What is the data source of their original report? (Check Database->Set Location)

At any rate, this is a warning, not an error, join the tables manuall and then use some field from the added tables, if you don't Crystal will ignore them.

Hope this helps a bit.

-k

 

[GotFish]

The original tables are, as I stated VFP, and their set location is just a folder on the C: drive, they are temporary VFP tables generated by their system. I DID manually join the back end SQL server 2000 tables, beyond the warning message, and it resulted in the second part of my message above, acting as if the SQL table didn't exist, I pull a field off it, and it shows up as blank, even though I know the key record exist for it, yet, all joins in this SQL are equal joins, so if it is not joining the SQL table, it should be dropping the record, not printing all data up to the point of the join to the SQL table (which is equal joined also) and acting as if the SQL table is invisible. I dumped all these tables into access, and none of them have blank fields.

Has anyone seen my other sock?