1. Home
  2. Point-Of-Sale Software
  3. Logging on to more than one HQ Database

Logging on to more than one HQ Database

Hi,

we have several shops accross Europe where each country is using a separate Database in RMS. To connect with the HQ I created a small batchfile that imports the registry keys for the database the user has chosen into the registry and then starts the HQ Manager. That works fine right now because we are using 1.0 where the reg-keys are always the same. In 1.3 (which we will be upgrading to shortly) things are a bit different. Here the Connection Details are encrypted and are therefore from machine to machine. That means I cannot include the registry-keys in the installation routine because they vary from PC to PC. Is there another way to avoid having the user reconfigure using the HQ Admin each time they want to connect to a different Database?

Thanx in advance,

C.Olsen

Reply to
Christian Olsen
Loading thread data ...

I think you've mis-diagnosed the problem with 1.3 registry files. The encrypted values are so long that the get word-wrapped when you export them from Reg Edit. This prevents them from being loaded back in correctly when you try to merge the files. Open the reg file in notepad, Format/Wordwarp, Format/Wordwrap *again*, File/Save. Try merging it again, I think you'll find that it works now. I've heard that you can just open open the file and save it without bothering with the word wrap thing, but I like to actually see the values displayed as a single line :)

That said, I don't quite get your configuration - you have one HQ for each country, each servicing multiple stores, correct? Then there is a global HQ Office that needs to access each of those country HQ Databases? That's more complicated than I'd have ventured, how's RMS working out in that environment?

Glenn Adams Tiber Creek C> Hi,

Reply to
Glenn Adams [MVP - Retail Mgmt

Hi Glenn,

I already realised that I need to unwrap the encrypted values in order to import them to the registry. That works just fine if the .reg file has been created on the same maschine that it will be imported to but not if you want to use this .reg file on a different maschine.

Our configuration works like this: One Server. One Database for each country we have stores in. People in the Headquarter in Germany that access the HQ Databases of each country by starting a small batch that 1st imports the .reg for that country (i.e. it switches the configuration to the correct database) and than starts HQ Manager. With 1.0 that works pretty well. The (encrypted) registry entries are the same regardless of the maschine it's installed on. The only thing is that you cannot open more than one HQ with different databases at the same time.

With 1.3 (our destination version) there is a maschine dependent encryption applied to the username, password... so I can't distribute the new HQ-.reg files accross all our maschines automagically.

As far as I see there are 2 possibilities:

  1. Remotely distribute 1.3 to all workstations and then go to each one of them and do an export of the registry keys.

... until the user has all the .reg file he needs.

  1. Create regfiles for each database containing all the connection details in PLAINTEXT (yes, that works as well). Of course thats not the way we ant to do it.

I suppose there is noth> I think you've mis-diagnosed the problem with 1.3 registry files. The

Reply to
Christian Olsen

Well, I'm probably mistaken, but I'm sure that I've applied reg files across computers. We do that to swap in replacement registers in the event of system failures. I don't believe that the encryption used by RMS is machine dependent. I guess that HQ could be different, but I'd be very surprised if MS created different encryption routines for Stroe Ops and HQ.

No, there's no login manager that I know of.

Glenn Adams Tiber Creek C> Hi Glenn,

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.