<< But still, an eval copy doesn't help unless they can run it forever. At some point they would have to actually purchase a copy, and that's what they can't do. >>
I think R:Base evaluation do run forever, but they don't let you do certain things -- sending output to the printer is one of them. So you would have to get a real copy of R:Base in there. Perhaps (with the cooperation of the person who needs the work done) you could express the cost of the single R:Base copy within the programming fees? Alternatively, can you load the CSV files to your laptop and generate the reports from there? Obviously that would be more expensive for the client (they would need you to run reports for them) but they seem more concerned with control than cost and this would allow them to keep control of their network. << This is the company where I thought I had a chance of getting RMail in there, until they found out that I had to touch the users' computers. That killed that project. They wanted a nice neat .dll in one place, and only there. >> Although I believe the R:Mail does need access to the system registry for it's settings you have a couple of alternatives. You could ask RBTI to make an enhancement to R:Mail that would allow the settings to optionally be stored in an INI file. Then you _would_ be able to run the program from a DLL located on the server without needed administrative access to the workstation (which I assume is the stumbling block). Alternatively, it is possible to send email from R:Base using VBS or other scripting languages, essentially duplicating (with restrictions) the functionality of R:Mail. I've done this with DLLs, VBS, and Python. -- Larry
