<< 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? >>
I don't think this is strictly correct. It's true that LAUNCH can be used with a document file only if the file's extension is associated with the appropriate application. But LAUNCH can also be used with a complete command line (LAUNCH C:\RBTI\RBDOS65\RBASE.EXE DoRep.CMD) and will work similarly to a ZIP command except that the specified program will run in a separate process. (At least, I think that's true). << 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... >> You could set up the Access database with just your report and links to the R:Base data. Then specify a startup form that would print the report and then quit Access. That would print the report with no user intervention. There are ways to spawn processes in Windows and have them be invisible -- so it might be possible to do this without the user even seeing the Access application at all. Finally, you could probably accomplish the same thing via Automation in a Visual Basic script -- launch the script and it could control the use of Access or other scriptable applications to do the printing. -- Larry
