Welcome to the Visual dBASE Compiler
              ------------------------------------

This file contains important, late-breaking information about the Visual 
dBASE Compiler, including updates to the documentation. 


TABLE OF CONTENTS
-----------------
 1. Configuration and System Requirements
 2. Compiler Installation
 3. Documentation Updates
 4. Automated Registration Notes


1. CONFIGURATION AND SYSTEM REQUIREMENTS
----------------------------------------
The Visual dBASE Compiler requires 8.6Mb of disk space in addition to the
space requirements of the main Visual dBASE product.

Other system requirements and supported networks are the same as those 
for Visual dBASE. For a list of these requirements, see README.TXT.


2. COMPILER INSTALLATION
------------------------

See the Visual dBASE Professional README.TXT for complete installation
instructions.

The compiler should be installed in the same directory as the Visual dBASE 
executable files (normally \VISUALDB\BIN).

Compiler installation causes the following changes in Visual dBASE:

  * Additional command options for the COMPILE command are enabled.
  * The BUILD command is enabled.
  * Additional options appear on the Compile dBASE Source Files dialog box.
  * The Build Executable and Deploy Application commands are added to the
    Program menu.
    
To learn how to build and distribute Windows executables with the Visual
dBASE Compiler, see the Programmer's Guide and online Help.    


3. DOCUMENTATION UPDATES
------------------------
- Using the WAIT command or the INKEY(0) function within a compiled
  application causes focus to shift from your program to the dBASE shell.
  Use the SLEEP command instead.

- Source files assigned to properties of objects are not compiled if
  you issue the COMPILE command with the AUTO option. For example,
  if you compile a program containing the line:

    MyForm.View = "MYVIEW.QBE"

  the file MYVIEW.QBE is not compiled.
  
- One of the Visual dBASE Runtime Engine files is incorrectly listed as
  DBWRUN55.EXE in the Deploy Application dialog Help. The correct file 
  name is DB55RUN.EXE.

- If you are compiling an application that uses .VBX controls in a form, 
  you must include the .BFM file when you BUILD the application, 
  or distribute it externally.

- If you are using VBX/DLL custom controls from a directory other than 
  the current directory or the normal Windows VBX storage directory
  (\WINDOWS\SYSTEM), you must modify the .WFM to strip out the full path 
  specification. If you don't, your deployed application may not find the 
  .VBXs or .DLLs it needs. Alternatively, you can remove path specifications 
  (e.g., "DLL0=C:\APATH\...") from the [DLLs] section of your DBASEWIN.INI 
  file. This forces the Form Designer to ignore specified paths and to 
  conduct normal Windows library searches (current directory, then 
  the Windows directories). 


4. AUTOMATED REGISTRATION NOTES
-------------------------------
The Visual dBASE Compiler features an automated registration system which 
allows you to register your software with Borland at the time you install 
the product. Registration is accomplished via modem, if a modem is 
available, or by printing and then mailing or faxing your registration 
information.

If you start, but do not complete, the automated registration when you
install the compiler, you will be automatically reminded to register after 
14 days. This reminder can be disabled by removing the command 
"C:\VISUALDB\VDC55REG\remind.exe" from the "load=" line in your WIN.INI 
file. (WIN.INI is normally stored in your Windows directory.)

Under Windows NT, the steps to disable the reminder are different. The
steps are:
  - Double-click on REGEDT32.EXE in the \WINDOWS\SYSTEM32 directory.
  - Find the "HKEY_CURRENT_USER on Local Machine" window.
  - Search the tree for Software\Microsoft\WindowsNT\CurrentVersion\Windows
  - Double-click on the "load" item to bring up the String Editor.
  - Remove the entry for REMIND.EXE from the string.

After registering, you can safely remove the directory
\VISUALDB\VDC55REG and the files it contains.