Is there any reason that these unique files cannot be ;TEMP, temp files,
which are only visible to the job or session that create them? This way, the
job stream can live entirely on the 3000, maintained and controlled from
there.

Failing that, as mentioned, you can grab a variable that is unique to the
job, like job number, and use that in your file name. Of course, then you
have the happy chore of making sure that those files actually do get cleaned
up. This housekeeping could simply be done at the start of every job.

Also, I believe that Access will let you use VBA. You can also ftp the file
to a unique name, and then SITE STREAM it. That promises to be ugly, but
probably no uglier than other means of passing the job from Access to the
3000.

Greg Stigers
http://www.cgiusa.com

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *