PR>These people will need access to basic Paradox, but is there a way to
PR>keep them out of table restructuring, etc. in the app alias, while
PR>allowing them to play in their own yards all they want?  Thanks again
PR>for your fine help.
Hi Peter:
Glad I could help. In answer to your question, "yes, there is a way to keep
them out of table restructering." To do so, bring up your table, and call up
"table restructure". Under "table properties" you will find "password
security", this I believe is the area you are looking for.
Personally, I don't password protect the tables, and for only one reason.
When you password protect the tables, they become encrypted. Because of
this, when backing up the data tables, the compression is almost nil.
Without the encrytion, my client can backup approximately 5-7 Meg tables on
ONE floppy, whereas if the table is passworded, he would require about 5
diskettes. Since his users have NO access to the tables beyond what my
application permits, there is little reason for passwords in the tables.
Although the tables are not protected, the application is. On what I call
the Database Manager Form for the application, there is a function for the
user logging on. When the user inputs his or her name and password, the
program checks MY config.ini file to allow or disallow the user going
further.
The main disadvantage to this procedure is that if you have "computer
literate" users they can get to the files and tables via DOS. This is not a
problem for my client, but may be for you.
Hope this helps.
Regards,
David.
...coming to you from CANADA - the greatest country on the planet!
...now flying on Windows '95
---
 * VbReader 2.22 #545 * "...ever feel like the only tree in a dog kennel?"
--- QScan/PCB v1.15b / 01-0348
---------------