RMS 1.3 & Blind Closeout

JJ - are you around offline from the newsgroup? You can do this with some really easy scripting - but I am not about throwing that stuff around on the groups.

JJ - just curious - any reason in particular why the blind closeout can't be done at the register....? - maybe it's a few floors down and when its miller time its miller time, not walk a few floors down to do a blind closeout time...?

"I was > Jocelyn,

JJ - Please note that going the scripting route should only be used for events where you can not get to the register because something happened and you can not change the reg # on the one you are using.

For daily maintenance - this is not a solution. As a general response to your question - no, you can not blind close a register from Mgr. But - if it is a must, you can jump through a million hoops to script the changes - but scripting always puts you at a higher risk for data loss and/or corruption.

Please let me know the reason for the blind close from Mgr.

Thanks,

Oh - I see! There is zero chance that scripting the changes would be any kind of a valid operation for this issue. The scripts would be more for sever data issues where you can not access the regs.

If the bookkeeper machine is on the same LAN as the register (as it may be since its running the manager application), if the bookkeeper has a login to POS, look into installing VNC on your computers for remote connections and remote management - there is a free entry level version that will let the bookkeeper connect to the POS machine over the LAN, log into POS, do the blind closeout, then disconnect by closing the VNC program.....

"When some> JJ - just curious - any reason in particular why the blind closeout can't be