I encrypt entered passwords, compare them to encrypted stored passwords, ala linux. I am comfortable with that.
I hope you mean hashed... Encrypting passwords is not a lot more secure than storing passwords unencrypted, especially considering the lack of libraries with modern encryption routines on FP DOS.
Currently I use the: if choice='A' .and. x=5 .and. y > 3 do the procedure endif where x is theuser's id number and Y is the user's access level.
The most common approach for that is to assign users specific rights or roles and then check for those. Hardcoding user ids only works in single installations and is prone to errors after years.
I encrypt my source on compiling.
That doesn't help much, to be honest.
I don't use variable names that are too descriptive.
There are two way. A hard one and an easier one.... The hard one is to actually use non-descriptive variable names in the code. That make it hard to maintain the code. The easy way is to use a DEFINE statement to translate the descriptive name to a non-descriptive name.
Since FP DOS does not support include files, you need to insert the #DEFINE statement at the beginning of the program. A simple program can do this automatically in all of your PRGs within a project.
-- Christof
--- StripMime Report -- processed MIME parts --- multipart/alternative text/plain (text body -- kept) text/html ---