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 strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

P.SQL field level security issues

Status
Not open for further replies.

dgillz

Instructor
Mar 2, 2001
10,038
US
How do you keep a technical user from accessing certain fields within a P.SQL database? In my example we have a price override password stored in a file, and have application security so that only 2 people have access to maintain that part of the application (the application is Macola V7.5).

However, if you have access to Crystal Reports (as many users do) and you can connect to the database either thru ODBC or a native connection via file.ddf, the entire database is open to you. You can write a crystal report in 2 minutes that will tell you the price override password! There are lots of other areas I'd like to keep people out of as well.

In short, thios all or nothing access does not work well and I need to restrict people from reading the records at a field level. Software Support for Sage Mas90, Macola, Crystal Reports, Goldmine and MS Office
 
Crystal Reports also provides column level security via "Infoviews" so you should be able to do it at the Crystal level, and at the SQL level with groups, users, and views.

Regards,
Pervasivite
 
Perv-

how do I do that in crystal? Software Support for Sage Mas90, Macola, Crystal Reports, Goldmine and MS Office
 
Set up your DB security, and use the GRANT SELECT(Field1, field2,...,fieldn) on your tables. This allows SELECT on the specified fields in PSQL 2000 (I don't know about PSQL V7.x)

 
Vancouverite-

Is DB Security a function of Crystal Reports or a function of P.SQL? Regardless of where it is, please WALK mw through how to do it. Software Support for Sage Mas90, Macola, Crystal Reports, Goldmine and MS Office
 
Database Security in this context is a function of Pervasive.SQL. To configure the security, the manuals have a better description than I can enter here.

Look at the following sections:

Advanced Operations Guide:
Owner Names and Relational Security
Discusses an outline of what is required and how to configure DB Security

Pervasive.SQL Users Guide:
Using Pervasive Control Center:
Setting Database Security
Example of setting up DB security on an existing DB.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top