I was in dev mode (alone) and everything was fine.  Then I promoted to production (multi-user) and when the second user went to log in, QB threw an error.  Best I can figure (based on the QB login that shows up when I log in afer) is that the DSN UID/PW is being ignored and instead, QB is using the "Login As" on the Access Rights tab folder.  As such, after the first person logs in, QB throws an error saying that the user is already logged in and errors out.

I can't believe this ISN'T something easy, but it's throwing me...any help is appreciated because if not, I'm going to have to run a parallel app that acts as a trigger just so I can have the single connection to QB...which I OBVIOUSLY don't want to do.

Thanks in advance,

SThompson

You actually select the user account that QODBC uses in QuickBooks when you first connect the company file. From the QuickBooks Edit menu, select Preferences, and then select Integrated Applications to edit the account. For multiple uses on a network, the administrator would setup each user to use their own account for each workstation on the network when they setup QODBC.

QODBC doesn't use UID/PWD parameters. Login security is strictly controlled by QuickBooks as required by Intuit.

See: How do I build a connection string with all the available QODBC parameters? for more.

Tom,

I'm on board with you on that part, and all 20+ employees have their own respective login to QuickBooks, but when you do the FLEXquarters QODBC it asks what you want the app to log in as, and so I choose a login.  When two different people on two machines use the QODBC, each then attempts to connect (because of the certificate screen you showed) with the same "Login as" ID, and quickbooks only allows you to log in to the company file one time.

After the first time, you get a nasty error.  Now...interestingly, if I open the app a few times in the same Terminal Services SESSION, it almost "shares" the same conduit to QB and that's fine, but when another user in another TS session attempts to log in, they crash out.  I was going to intially create a complete second set of login's for each user, but since it's not using the UID/PW and only going in using the "Login as" (as defined), it's thinking the same user is logging in all over the place...

Does that better clarify the problem I'm experiencing?

Again, thanks in advance,

SThompson

Because you are using Terminal Server, you will need to use the QODBC Remote Connector for each Terminal Server user. All the copies of QODBC will then all connect to the one copy of QuickBooks using the one admin login running on the Server Console (local session) via the IBiz Remote Connector.

See: W2K3 Terminal Server / QB2006 Ent. + QODBC  for more info.

Would it be an easier setup if I had QODBC set up and running on each PC?  If each person that uses QB has QODBC on their PC, will they connect as they respectively are set up, or will they each ultimately end up hitting QB and then all going in using the same Flex QB "Login as", meaning that they would ultimately crash out again?

(Just trying to come up with the easiest solution for them possible).

Again, many thanks.

-SThompson

Where QuickBooks and QODBC is run on each workstation on the network, the company file is the only thing shared. So each copy of QODBC would use the user's login for each workstation to connect to QuickBooks. So providing you have the right number of QuickBooks users, there's not a problem.

On Terminal Server, while you can run multiple copies of QODBC in each user's virtual machine, there is only one QODBC login connection that can be made to QuickBooks at the one time as there is only one computer.