>I'm not sure why it would make you nervous.... >1) Use Launch rather than Zip (Starts a separate process??) >2) Put an Icon on the desktop just for the purpose of printing this >report. (They can tinker in Dos) >Ben Petersen
Makes me nervous only because of memory considerations. They would be zipping in and out of RBDos many times a day, maybe a few times an hour. Not sure this would hold up, but it's worth a try. I don't know if zipping to an empty batch would clean up any memory problems. Launch will only work if I associate a program with a file extension. I wouldn't want to do that with a standalone RBase command file. Otherwise someone could double click on a program in explorer and it would start RBase, right? Yes, putting a separate ICON just for the DOS database is definitely an option. But for those who were hoping that DOS would be totally out of there, zipping to it would almost hide the fact that it's still around (of course you still can see the program starting and working). >So why not write the report in Access (using linked >tables to get the data from R:Base via ODBC) and then >LAUNCH the Access App from inside R:Base. It could be >completely transparent to the user >Larry A good idea, Larry! I like launching to the database rather than having them actually go into Access to run this. That is, if I wind up going that route... Karen
