Q: Why I cannot step through Pdxrbld code after compiling
   it with debug options in the IDE?
A: Units in Pdxrbld do $-include Pdxrbld.inc file with 
   predefined compiler settings that turn debugging information off.
   Just change the line 
   {.$DEFINE DEBUG}
   to
   {$DEFINE DEBUG} 
   in Pdxrbld.inc file and recompile.
-----
Q: I do not want to disclose Master Passwords for tables in my
   application to my customers. Is there any way to hard-wire
   these passwords into Pdxrbld application?
A: There are two ways to achieve this:
   1) Execute Pdxrbld through ShellExecute (or WaitForSingleObject) 
      and specify passwords as /P parameters in the command line.
   2) Pdxrbld code change: add the statement
      "AddSessionPassword(YOUR_PASSWORD_HERE);" (16-bit version)
      or
      "AddSessionPassword('',YOUR_PASSWORD_HERE);" (32-bit version)
      at the end of main form's OnCreate event. The application will 
      then use the password for all tables protected with 
      YOUR_PASSWORD_HERE
      master password. It still prompts for password in tables 
      protected with different password, though.
      Comment: the AddSessionPassword routine in the 32-bit version
      accepts two arguments: px3P key and password value. If you are
      not using Px3P key encryption scheme (see Readme.rtf for more 
      information about Px3P key), the first argument should be empty string.
-----
Q: I am using Px3P key encryption scheme in my Paradox database. How do I check/
   repair such database by using Pdxrbld?
A: There are two ways to achieve this:
   1) Execute Pdxrbld through ShellExecute (or WaitForSingleObject) 
      and specify Px3P key as /X parameters in the command line.
   2) Pdxrbld code change: add the statement
      "AddSessionPassword(YOUR_PX3PKEY_HERE,'');"
      at the end of main form's OnCreate event. 
   The application will then automatically check whether the database tables 
   were encrypted by using given Px3P key. If this will be the case, it will 
   use Px3P key encryption when rebuilding the tables.
   Note: When using the Px3P key encryption scheme, Px3P.DLL must
         be present in the system path.
-----
   