SQL user- Macola login

[marixb]

Please explain...we create a user and password in visual menu builder, then a user(_sql) is created in the screens database. we have 2 macola companies, 2 screens databases. i would like to use the same login for both companies-we are being told it is not possible. anybody know why? i tried setting up same user in both companies and can see the user in both screens db and in menu builder for each company. macola won't open for the first company, the second opens fine. what other magic is happening?
thank you in advance...

 

[maccrystal]

Normally in a standard install of Progression there is only ONE (1) Screens Database. The user when created can have rights to multiple companies using one login. Can you describe how your installation is configured and specifically why two screens DB's used?
- m:\macsql (installation 1 7.6.300c)uses Screens
- m:\Macsql2 (installation 2 7.5.103f)uses Screens1 (overridden in MAcSQL.cfg)

We use this configuration to keep a test install on 7.5.103F and so the screen sets would not be updated by the newer releases.

http://www.appstratinc.com

 

[kscheeler]

When Macola creates the user in the screens database "MACUSER" it also creates a user in SQL called "MACUSER_SQL". The password is synchronized between Macola and the user in SQL. If you copy the screens database and duplicate it and change the password in just one of them, the user in SQL is still using the "old" password. You cannot just open up the user in SQL using Enterprise Manager and change the password because Macola encrypts it when you save the user through Visual Menu Builder. The users in Both companies can have the same password but once you change it in one, you will have to use a SQL script to update the password in the second screens database or you won't be able to access any companies using it.

Kevin Scheeler

 

[marixb]

i set up both users with the same password.
company one- user fred, password- wilma (set up first)
company two- user fred, password- wilma

we ran script to update users...we are good now...
can you think of any problems this might create?