|
Posted by Craig on April 9, 2008, 4:26 pm
Please log in for more thread options
I have 1.3R converted to 2.0 on a test sysytem. I have not upgraded my
production system, nor do I intend to until version 3 comes out. In my test
sytem(1 POS machine and 1 back office machine) I had no issues creating a
new tender type, Z'ing out the POS and closing a blind batch. That was the
reason I asked why it did not work for you. I found (in my tests at least)
that you don't need the manager machine assigned a register number like you
did with 1.3 which is what would cause your issue, I believe. Connect to the
database with admin. and under configuration remove the register number on
the machine running manager, and see if you have the same result. Not being
able to test process's such as this with 2.0 is one reason I don't plan to
upgrade to 2.0, and plan to wait for 3.0 . With 1.3 you could test things to
make sure the results were what you intended.
Craig
>I do not know if I will have a problem when I do create a new tender type.
>I
> am trying to avoid a problem in RMS 2.0 that was a Problem in RMS 1.3
>
> I am asking because no one answered completely a previous post on the same
> issue "Server error 131" in RMS 2.0 which happens when you try to close
> out
> without z, after adding Tender Types in RMS 1.3. (from January 2008)
>
> I need to edit and create new tender types, I do not want to find out that
> I
> need to z out a machine that can not be z'd out after the fact.
>
> CRAIG - Did you have RMS 1.3 and convert to RMS 2.0?
>
> If so I would like to know if you have the back office computer still set
> up
> as POS in the Database. (in RMS 1.3 you could run any computer as a POS)
> My
> data base still shows these as registers even though they can not be
> opened
> as POS anymore due to we only have 3 licenses and 3 registers up front.
>
> And since my Store 2 databse was copied from Store 1, my store 2 Database
> shows computers as registers that do not exist. and Store 01 still shows
> computers that were moved to Store 2
>
> --
> DDowningMO
>
> HQ 2.0.0110 / RMS 2.0.0110
> 4 Lanes, 4 Back Office
> Server 2003 SP2
>
>
>
> "Craig" wrote:
>
>> Any time I create a new tender type I only have to Z out the POS on my
>> POS
>> machine. Why won't that work for you?
>> Craig
>>
>> > Akber
>> >
>> > Thank You for the response but I am confused on how to Z out my back
>> > office
>> > computer when I can't start POS on it. When I try to Start POS it tells
>> > me
>> > I
>> > have a license violation and quits.
>> >
>> > So please tell me step by step if you can. How to z out a back office
>> > computer on RMS 2.0
>> > --
>> > DDowningMO
>> >
>> > HQ 2.0.0110 / RMS 2.0.0110
>> > 4 Lanes, 4 Back Office
>> > Server 2003 SP2
>> >
>> >
>> >
>> > "Akber Alwani" wrote:
>> >
>> >> hi Sir,
>> >> You can do Z out in the same way as 1.3 no problem the RMS 2.0 has
>> >> change
>> >> but not at the level of sales operation but item matrix, PO and rest
>> >> of
>> >> the
>> >> master related things >>> Store Manager. Whereas all POS options are
>> >> same
>> >> as
>> >> 1.2, 1.3 and 2.0 so you can do Z out to bring new tender type to POS.
>> >>
>> >> Regards
>> >> Akber
>> >>
>> >>
>> >>
>> >> "DDowningMO" wrote:
>> >>
>> >> > How do we "send" the new tender type information to the Back Ofiice
>> >> > Stations
>> >> > that are used in Closing out?
>> >> >
>> >> > I have to change or add a new Tender Type for the POS stations. We
>> >> > used
>> >> > to
>> >> > have to z out all stations after adding. We can not z out our back
>> >> > office
>> >> > computer because we are now using RMS 2.0, and cannot run POS on it.
>> >> >
>> >> > With RMS 1.3 if you did not z out the Back Office computer you wuld
>> >> > get
>> >> > a
>> >> > server error 131 on the Back office computer when trying to close
>> >> > Blind
>> >> > Closed batches from the POS stations.
>> >> > --
>> >> > DDowningMO
>> >> >
>> >> > HQ 2.0.0110 / RMS 2.0.0110
>> >> > 4 Lanes, 4 Back Office
>> >> > Server 2003 SP2
>> >> > 2 locations
>>
>>
>>
|