>>A few of our clients are getting an obscure error when running reports. While the report is running and being prepared for preview, a dialog pops up prompting the user to find a table/DBF. When the user presses Cancel, the dialog may or may not pop up again multiple times. Eventually, the user receives this error:
>>
>>File 'm_4nl0nroh6.dbf' does not exist.
>>The metadata for some report definition rows could not be loaded.
>>Some dynamic report features may be missing, or a report could not conclude successfully.
>>
>>Three of our clients are running into this now. The only common theme is that the clients either bought new machines with Windows 7 or upgraded to Windows 10. One of the clients inadvertently upgraded to Windows 10 and then started seeing the issue. We tested the issue with the Primo PDF driver, and the error still occurred. So, it doesn't seem to be tied to a specific printer driver.
>>
>>We use XFRX, so I asked them if they have seen this error before. Their response:
>>
>>
This is not error message from XFRX, but (IMHO) from reportlistener class (_reportlistener.vcx) or from VFP. Some operation close internal cursor for reportlistener.>>
>>I agree with their assessment, but it doesn't help me solve it. Has anyone else encountered this issue?
>
>Put your application folder in exclusion list of the antivirus.
>Try to delete all files in TEMP folder of the user.
The error occurs in frxcursor.UnpackFrxMemberData() while attempting to Alter Table on a cursor that was created only a few lines earlier. For some reason, the underlying DBF is missing, but I can't explain why. You are probably on the right track with the temp files, but the error is intermittent and we can't get a consistent repro. At least one of the clients had a virus, but I can't confirm if that was the cause.
What I did find is that some of our reports that contained generic MemberData in the STYLE field of the FRX that was not being used. Once removed, the code producing the error will not need to run. I suspect the data inadvertently got in there in the first place using the Report Designer. If you go to Field Properties->Other and click on the Run-time extensions->Edit Settings button, it will automatically add code to the STYLE field, which will be saved if you press OK.
NOTE: There are legitimate uses of MemberData in the STYLE field, such as rotated labels. In those cases, the STYLE field needs to remain populated, so be sure before deleting the data.
