I finally got Crystal Reports 10 up and running after all this time.  Now I'm faced with security issues.
 
Can you limit the tables accessed by the CR designer??
 
Example:  Production Employee wants to run various Inventory reports, label layouts, etc.  (and maybe wants to give a try at designing some of his own).  Can I limit him to just BKICMSTR & MTICMSTR??  Currently he has access to all the other tables with employee info, etc.
 
Lenette

You might say it is more of an ethical than security issue.  Anybody with access to the data they need should understand that other things are outside of their responsibility... aka don't stick your nose in others' business.
 
If you trust your production employees to create reports, you must understand the responsibility that becomes.  If the access is beyond your control, then it is a management issue, and create the reports for them by their request.  Just speaking as an employee whom "reports" for many.

I enabled security on my ODBC DDF files and then granted only select on non critical files (non payroll and non gl) to PUBLIC.
 
When you enable security, Pervasive automatically creates a MASTER user with full privileges.  This is the user that I use for my financial reports.
 
I then added one general user.  The user I added only has access to the "PUBLIC" privileges since I did not specifically assign any privileges to this user.
 
The recommended way to setup security, assign users, create views, etc. is to create an SQL script.  By doing so, you can apply these same settings if it becomes necessary to re-create the ODBC DDF files by running ODBCDDF.RUN.  Re-creating the DDF files deletes all security and stored views.
 
Having said that, be sure to either move ODBCDDF.RUN, or protect access to this specific file with Operating System Security.

If you really care to go through the hassle of implementing security on your database, it is all accessible through the Pervasive Control Center.  You must enable security on your database by setting a Master user password, then create/modify your users/groups, and change the table security/permissions using the table view of PCC accordingly.  I suggest testing this method on the DEMODATA database until you feel comfortable modifying your DBA database.
 
If you're really k33n you can use the SQL functions GRANT, DENY, REVOKE, etcetera, to set the permissions via command statements.

Yes, and there is no need to run any additional programs to recreate the DDF files.  As long as your ODBC DSN resides on the computer you will be accessing/creating your reports from, when you enter Crystal Reports and access your database, a prompt for a username and password will appear.  As I suggested before, give this a try with your DEMODATA database as you can report from the data within it and experiment with enabling security and setting permissions.