|
Buy Support
Incidents |
|
If you can't find your answer
in the FREE PUBLIC QDeveloper Forum, require URGENT Priority Support, or you need to send us
private or confidential information: |
|
Click Here
|
If you can't
login and post questions or you are having trouble viewing forum posts:
Click Here
|
Callback
Support |
|
If you live in USA, UK, Canada, Australia or New
Zealand, you can leave us details on your question and request us to call you back and discuss
them with you personally (charges apply). |
|
Click Here
|
Buy Support
Incidents |
|
If you can't find your answer
in the FREE PUBLIC QDeveloper Forum, require URGENT Priority Support, or you need to send us
private or confidential information: |
|
Click Here
|
|
| Security |
| Author |
Message |
| KofK |
| |
| Group | : Members |
| Posts | : 43 |
| Joined | : 2006-04-04 |
|
| Profile |
|
| Posted : 2006-05-06 03:08:57 |
| Is there away that put a user name and password into the QODBC connection string so I can prevent users from accessing QB data from other programs? |
|
|
|
| Tom |
 |
| Group | : Administrator |
| Posts | : 5510 |
| Joined | : 2006-02-17 |
|
| Profile |
|
| Posted : 2006-05-06 17:37:34 |
QuickBooks controls the security not QODBC, so if you don't want QODBC to connect without a password, disable "auto-login". To do this you must start QuickBooks as the Administrator. Go to the "Edit-Preferences" menu item in QuickBooks. Then select the "Integrated Applications" icon from the left side. Then highlight one application (usually FLEXquarters QODBC) and press the "Properties" button and click on the Company tab.
And uncheck the "Allow this application to login automatically" so that QuickBooks will need to be started by the user and the user name and password entered. |
|
|
|
| KofK |
| |
| Group | : Members |
| Posts | : 43 |
| Joined | : 2006-04-04 |
|
| Profile |
|
| Posted : 2006-05-08 23:53:25 |
The issue I am having is that I want the user of my VB program to be able to access the QB file only through the VB program, this way I am able to control what information the user can see.
The way it's set up now is that the user can start any program that supports ODBC and access any part of the QB file including private information. |
|
|
|
|