Establishing new database

I am setting up RMS for the first time - and found it to be very frustrating. I have a backoffice computer and two registers and all three seem to have different issues. Here is what I have done. I initially had the dongle attached to the backoffice database so that I could play around with the software. I over wrote the information in the Sample database to include our store specific information. Next I moved the dongle to the first POS register and tried to log on to the new database. Below are my problems:

1) Since the dongle now resides at Register1, although I start it up first, the office computer still says it has a violation error and is in evaluation mode. I thought that would go away whenever Register1 was logged on to Manager or POS, but it has not. 2) Register1 - In Administrator I can connect to my new database using the IP address of the office and test it. Everything seems okay. But when I got to Manager or POS I get Error 201 Cashier was not found ... I have made sure that the Office and both Registers have unique register numbers. I also use the same logon information for Manager as I do for the Office but Register1 does not recognize it. Does anyone know why?? 3) Register2 - Totally different problem. When I go into Adminstrator and try to connect to the new database, I get this error: 2147217843 Login failed for user SA. Hopefully someone can help me and please spell it out in layterm terms. I am not a computer expert at all! My store opens in one week and we are totally exasperated. Thanks!
Reply to
Dinell
Loading thread data ...

You have to have each register built in the database 1, 2, 3 ect. and make sure your not exceeding your lane limit on your license. (help about displays serial/lane limit) In mgr go to database register list and add additional registers and configure each ones printers, scanners ect. RMS expects to see the key on wich ever reg. had it during the last good read but it can be moved. make sure none of the regs have the same number. (administrator, options, reg number)

Reply to
Ron Reyes

Also you have to have all reg connect to one database on one machine. (make sure they're not all set to "local') The key should be located on the main register that's going to connect first every day.

Reply to
Ron Reyes

Reply to
Dinell

Whereever the licences and data are stored it should be the first one to boot up and last to be shut down at night (if you want).

So that, when 2nd machine or 3rd machine is starting it will easily detects the Server PC ( PC where the data is stored).

For Store Administrator-->It is a one time setup not unless you have change the database name and server name (if your not using an IP address).

I h> Thanks so much for the quick response. Based on your two messages, I have

Reply to
GregDxb

Actually when POS or manager programs are started on the machine with the dongle it updates fields in the database it's connecting to. The other machines read this info (the fields are in the conf. table) and know the dongle was read that day.

Boot up order effects nothing, the program mearly needs to be started on dongle holding machine first to update the DB for that day.....

Reply to
Ron Reyes

There actually two different things the config tab is storing the default database you want to connect to (POS and MGR use these settings) however you can connect to other databases with the connect button. As you likely know you have to use connect to preform reindexes and checks in admin. The config stuff is basically for POS and MGR.

I actually use this as I test stuff on a sample DB but I have to go to Reg 1 and connect to it to reset the license nag/lockout on that DB.

Reply to
Ron Reyes

Rebooting/Windows Start-up order is not important, You just need to close all RMS programs on all systems, then make sure that the register with the dongle starts POS (or manager) first.

Glenn Adams Tiber Creek C> Thanks so much for the quick response. Based on your two messages, I have

Reply to
Glenn Adams [MVP - Retail Mgmt]

BeanSmart website is not affiliated with any of the manufacturers or service providers discussed here. All logos and trade names are the property of their respective owners.