Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations IamaSherpa on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

SQL 2000 Macola 1

Status
Not open for further replies.

wwwedward

IS-IT--Management
Oct 26, 2003
161
US
What is the maximum level of security that can be applied to macola tables and still have the program function?
 
Macola uses SQL authentication to access the tables while the user is in the software. You can lock down the NT user names either directly or through groups and use the db_denydatareader and db_denydatawriter functions to the various databases and Macola will still function. This should include ICR's as well since Macola passess the Macola user name and password for running those reports. You would be limiting or denying access to Macola through outside Crystal reports, MS Access, Query Analyzer or other tools that can read a SQL database.

Kevin Scheeler
 
Kevin,

If you use db_denydatareader and db_denydatawriter, the individuals and groups members will not be able to use Macola, correct?

After all, normal business like entering orders, maintaining items and customers, requires the ability to read, write and delete data from the database.

Software Sales, Training, Implementation and Support for Exact Macola, eSynergy, and Crystal Reports
 
Maybe I should clarify my statment. You would make those changes on any user or group WITHOUT the _SQL at the end of the name. Macola is using the SQL users like SUPERVISOR_SQL or DEMO_SQL. If you modified those, you are correct in that you wouldn't even be able to connect using Progression. However, those SQL user names can only be used by the Macola application since the password inside it is encrypted and you couldn't type it in manually if you tried to use SQL authentication through query analyzer with that user name.

Kevin Scheeler
 
Kevin's right - outside of Macola, SQL database access is tied to the 'non-SQL' version of the user's name. At this level you can control access via third-party tools like Crystal, MSQuery etc. and you have complete control i.e. table, field and row level control. You can also establish trusted connections (though Macola will probably tell you otherwise) so that users do not need to enter a separate SQL password when accessing the data outside of Macola.

Peter Shirley
 
Thanks for the reply. I think I understand everything mucho better, just trying to work better security with macola users and users that might have access via anything outside of macola, an access adp project for instance.

 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top