Running report, Open file box opens

[adm1mxa]

I am running R&R 10.0 and have installed the Version 10.0.012 Service Pack Update. I am using dbf tables with FlexLink indexes. When I run a report (using Report Designer, or RapidRunner), the _Open file_ dialog box appears. When I look at the Windows task bar at the bottom of my screen, I see that a button has appeared labeled _FlexLink indexing in progress; Pres ESC to stop_. In the Open dialog box, I can hit cancel, or type a bogus filename and hit OK. The report does run correctly, but why is this happening. It makes using Rapid Runner virtually useless.____Thanks,____Michael

[kfleming]

This is not one I have seen before. Does it happen with any report that uses Flexlink? Try a new report against the R&R sample files and see if the same thing happens.____Kathleen__R&R Support

[adm1mxa]

I thought that this occurrence had something to do with the relationships, so one-at-a-time, I changed every variable associated with relationships. (I would make one change, save and close the report, delete all index and temp files from my hard drive, test the report again, etc). ____When this did not resolve the problem, I began to look at the data. I thought, maybe two or more records were sharing a common value in the linked filed in a one-to-one relationship, or that there may be a null value in the linked field. I found some records that met those descriptions. I attempted to change the values of those fields, and realized the table was read-only. ____I changed the table to be readwrite, but did not get a chance to update any of the values before I was pulled away from my desk. When I got back, I began to test the report again. The first run, I got the same problem, but every time after that it works fine. Remember, I never changed the data - I just changed the properties of the table so that the read-only attribute was not selected.____We have tested this with numerous reports, dozens of times. Relating to read-only dbf (dbase III) files, using FlexLink, will cause this problem, most every time. There is a variable that we have not figured out yet. Most of our existing reports have this happen, but when we write new ones to test the theory, we are not encountering the problem. I think it has something to do with the fact the tables in question were not read-only when the reports were originally created, but were changed months or years later.____Michael__Michael