One Step Retail Solutions Community Forums / Retail Pro / Products / Scheduling RPRODB / Latest Posts

RE: Scheduling RPRODB

Brett R — Thu, 09 Jul 2009 15:08:34 GMT

Workstation number will come up if Environment Variables aren't set with the RPROWS=1 etc.

Should also have RPRONET=MSNET

RE: Scheduling RPRODB

farinbegay — Thu, 02 Jul 2009 08:56:29 GMT

what parameters should i set besides the workstation number? or how do i omit the error message.

RE: Scheduling RPRODB

jake — Thu, 02 Jul 2009 08:43:45 GMT

the /poll /proc will do the trick.
i think that if you run a main station the /poll could be omitted.

RE: Scheduling RPRODB

Brett R — Wed, 01 Jul 2009 16:40:17 GMT

Not thru a scheduler, you could try the /poll /proc prameters, (which is what a remote is supposed to have after procin)

I dont think that is designed to remove locks though.

I would probably go with a batch file.

Scheduling RPRODB

farinbegay — Wed, 01 Jul 2009 15:43:31 GMT

good afternoon fellow colleagues.
I came across a problem with RPRO scheduler. i am running RPRO Version 8.52 and running the application off a virtual file server without any main install and deployed via a citrix presentation server. The originating problem was polling: when the scheduled MPROCOUT.EXE is executed, the error message displays "WS# is in use" or "Run the Master Workstation" then hangs until user closes application. Therefore, by running RPRO DB the file locks are removed; also by polling manually. I also tried scheduling a lock out period under syspref, but to no avail. The main main problem or uncertainty is how to schedule RPRO DB to automatically select "ok" when prompted, before my scheduled MPROCOUT.EXE, any ideas or solutions would be appreciated, and thank you...