Crystal Reports Error "Not Consecutive Index Fields"

[Wend5]

I am very new to CR. I have used it only to alter slightly reports that were already in existence in our register program. We are using CR version 6.0

Recently it was suggested that I add store Paid Outs to our Daily Operation Report. When I pulled the report, I found that paid outs were in a file (paradox) that was not associated with this report. I went in to add the file os_ttl.db. Visual Linking Expert appears. I clicked on Tables and saw the new table and added it to the report. The Store Number automatically links. However, the posting date would not link. Whenever I attempt to link it to another existing file's posting date, I get the message "Invalid File Link. Not Consecutive Index Fields" Below is a description of the tables.

File 1 d_ttl.db Index Fields: Store Number, Posting Date
File 2 dg_ttl.db Index Fields: Store Number, Posting Date
File 3(new file)os_ttl.db Index Fields: Store Number, Payment Media, Posting Date



When we run the report the program asks for the posting date and runs the corresponding report. I tried running the report without linking the posting date in the os_ttl.db file and got a report for every posting date......about 1492 pages instead of the normal 16.

I would appreciate any assistance with the problem (lack of knowledge). I have attempted contacting the people that sold us the program. Although they understand the problem, they don't know enough about Crystal Reports to give me a solution.

Any assistance would be greatly appreciated!!!!!

Thank you

 

[FVTrainer]

I've only seen this problem when a report is based on a native driver, as opposed to ODBC. I have not seen it with paradox, but I have seen it with other db engines. If you are using the native Crystal driver for your database (paradox), read on:

When you use a native driver, in CR, you have to link to indexed fields. When you are in the Visual Linking expert, you'll see the indexed fields in a given table because they have a symbol that looks (to me) like home plate on a baseball field. They'll be color coded to indicate whether thay are a primary key index or not.

So, when linking from table 1 to table 2, you can select any field you want in table 1, but the field you link to in table 2 has to be an indexed field. If it is not, Crystal will not allow you to do the join. Additionally, sometimes the order in which you do the link (if there are multiple fields that define the proper join, as is your case) is important. So try doing the join in the order in which the index is defined.

However, there is a simpler way of dealing with this problem. Use an ODBC driver (if one exists) for your database rather than the native driver. You can change the driver by first setting up an odbc connection to your database and then going to Database | Convert database driver. Make sure you have a backup of the report before actually converting the driver. Once the conversion is done, you should be able to join on any field and not worry about the indexes (although your performance may suffer).