location of data

[Jeannie]

Report is created in, for example, c:data.__On same station report is copied to c:
ewdata with matching set of dbfs as in c:data.__rrwrun is called with /Dc:
ewdata.__The report always pulls data from c:data instead of c:
ewdata.__Is there a way to force R&R to look to a specific folder for the data instead of the one used when the report was created?__I^m using a dbf to pass parameters.____Same thing happens on a network. I often want the same report to be run on different data sets. Since the report is always created within one of the data folders and then copied to the others, it^s a mess.____This is causing havoc.____-Jeannie

[Jeannie]

Should have said using version 9 build 9.0.009.

[Jeannie]

One more comment. It would be a nightmare to send an overriding ri_master and aliases for all linked tables. __-Jeannie

[kfleming]

If the data for a report can be found in the saved location we will use the saved location. The default data setting in the INI file is only used when the saved data cannot be found.____Kathleen__R&R Support

[Jeannie]

I understood the hierarchy. ____I told the user to map the data^s folder to an unused drive, create the report using this data path, and finally delete the mapping. Then when run, the report should not find the files which would force it to look at the /D assignment.____So may I add a request to change the /D to be looked at first?____If I fill ri_master and every alias with just the path and several of the aliases are not used on the report, will it make any difference? If that would work, I could automatically fill each at report set up.____-Jeannie

[kfleming]

If you set an RI_ALIAS that is invalid for a given report, then the report will error rather than run.__But using the RI_ALIAS fields is the only way to override any saved file locations.____Kathleen__R&R Support

[Jeannie]

Not the answer I had wanted. Guess I^ll stick to creating a dummy mapping.____thanks,__Jeannie