DG>a Menu system and disables any keyboard input that is not specifically
DG>required by MY program. Disabling some keyboard input also "keeps" the 
ser
DG>out of Paradox quite effectively. This places my application in TOTAL
DG>control. I have even disabled the Paradox signon screen, so the user sees
DG>little if any of the Paradox program.
David, thank you so much for responding!  This is exactly what I was
trying to get Paradox to do.  Now that I know what to look for, I should
be able to dredge up the information on the switches from the
documentation.  I was under the impression that I had to use dialog
boxes instead of forms in order to hide the Paradox application screen.
What you're doing is changing the Paradox application screen to meet
your needs -- an approach I hadn't thought of.  My application is going
to have 2 kinds of users (not uncommon, in my experience) -- data entry
people, who need speed and accuracy in entering the raw data but won't
need to build queries and reports, and analysts who can be "trusted" to
build their own queries and reports without hosing up the relationships.
These people will need access to basic Paradox, but is there a way to
keep them out of table restructuring, etc. in the app alias, while
allowing them to play in their own yards all they want?  Thanks again
for your fine help.
Peter
peter.reader@nwcs.org
 * SLMR 2.1a * --T-A+G-L-I+N-E--+M-E-A+S-U-R+I-N-G+--G-A+U-G-E--
--- WILDMAIL!/WC v4.12 
---------------