Converting paths in reports

[Simon_Garrod_(Guest)]

We have to provide a series of reports to customers as part of our product release. The problem is that the location of customers data can vary from site to site. As, for a given customer the data location remains constant we really need to write a conversion routine to convert the paths of data within reports. This would be run once during the installation of the product.__Does any one know a method of writing such a conversion routine?

[kfleming]

You might be able to accomplish this by simply editing the RRW.INI so that the DataDir points to the user^s data directory.____When a report is opened, R&R will look in the saved location for data files. If not found in the saved location, then it will use the data directory that is set in the RRW.INI.____Kathleen__R&R Support

[Eddie_Marshall]

I can confirm we edit the RRW.INI file with the path of the data to enable the running of R&R reports from within our application. This is just a simple instruction to the user and can easily be incorporated into the Installation documentation.____Eddie

[Best Online Loans]

Thanks for the replies. The problem with using the ini file is that there are two places where the data is located, one is a shared directory on the network and the other a local directory (which holds the master file, this is a temporary file constructed just before the report runs).__

[Pat_Dempsey_(Guest)]

We do this by aliasing ri_master, ri_mindex, ri_alias1, ri_alias2, etc.____An example of the entry into the R&R control file for RI_ALIAS1 would be RRNVTR=E:IA32MYDATA.DBF,E:IA32MYDATA.CDX____As long as the application knows the location of the data it can be passed to the report via the variables in the RRIN control file. RRNVTR is the name of the file used to develope the report. It^s name and path is saved in the report, but it can be completely redefined for the master file and up to 9 related files.____Hope this helps.__Pat__

[Lynn_(Guest)]

I^ve been able to accomplish this by adding a network path field in my program^s setup file or the registry. Then at runtime I write the path to the control file. This works very well, but if you change a relation, you need to change this file also or you will get alias errors.____CASE cReport="IINSTTOT-1"__oControlFile:Goto(1)__oControlFile:RI_MASTER:=cDirNetwork+"ILIST.DBF"__oControlFile:Ri_alias1:="ICPRN="+cDirLocal+"ICPRN.DBF"__oControlFile:Ri_alias2:="ISYSTEM="+cDirLocal+"ISYSTEM.DBF"__oControlFile:Ri_alias3:="ITSDEF="+cDirNetwork+"ITSDEF.DBF, "+cDirNetwork+"ITSDEF.CDX, ITSDEF"__oControlFile:ri_alias4:=Space(172)__oControlFile:ri_alias5:=Space(172)__oControlFile:ri_alias6:=Space(172)__oControlFile:ri_alias7:=Space(172)__oControlFile:ri_alias8:=Space(172)__oControlFile:ri_alias9:=Space(172)__oControlFile:Close()__RUN RRWRUN CONTROLFILE 1 /H_______