Deploying Visual DataFlex 9.1 Applications

A Data Access Worldwide White Paper
by Dennis Piccioni

December 1, 2003
Last Edited: August 2, 2005

Contents

Using Visual DataFlex 9.1, you can develop Windows applications, Web applications, and applications that are a combination of both Windows and Web programs. This paper will tell you how to deploy any of these application types to your users.

Note: This paper applies only to Visual DataFlex 9.1, not revisions newer than 9.1. Starting with Visual DataFlex 10.0, the information in this paper has been added to the Visual DataFlex help system and is updated there for each revision of VDF. Look for a book entitled Deploying Applications in the Visual DataFlex help.

To simplify this paper, the bulk of it has been divided into 3 sections, one for each type of Visual DataFlex application you can deploy. The 4th section discusses miscellaneous topics that may apply to any type of Visual DataFlex application deployed. This way you can focus on the section specific to the application you are deploying, and then finish up by reviewing the Miscellaneous section to see if any of the items there apply to your application.

  1. Deploying a Visual DataFlex Windows Application
  2. Deploying a Visual DataFlex Web Application
  3. Deploying a Visual DataFlex Windows & Web Application
  1. Miscellaneous Deployment Issues

1. Deploying a Visual DataFlex Windows Application

Deploying a Visual DataFlex 9.1 Windows application involves only 2 steps:

1. Run the Visual DataFlex Client Engine Installation
2. Deploy Your Windows Application

1. Visual DataFlex Client Engine Installation

The Visual DataFlex Client Engine Installation (VDFCEI) is an installation program, provided by Data Access Worldwide, that installs the Visual DataFlex Client Engine and (optionally) Database Builder, Database Explorer and other utilities provided by Data Access Worldwide.

The VDFCEI always installs all files and makes all necessary Windows Registry settings to allow Visual DataFlex Windows applications to run on the destination computer. You can control what optional components are installed and certain Client Installation display options by using the Client Installation configuration file. The Client Installation configuration file is a text file and completely self-documented.

You can download the most current Visual DataFlex Client Installation and Visual DataFlex Client Installation Configuration File for the version of Visual DataFlex you are using from the download section of our Web site: http://www.dataaccess.com.

You may choose to develop an installation program for your Visual DataFlex application(s) using any available software installation tool, such as Wise Installer or InstallShield. For licensing reasons, you must install the Visual DataFlex Client Engine using the VDFCEI. You can implement this by calling the VDFCEI program from your installation program.

VDFCEI Network Installation

Most likely, you will install your application on a network rather than a standalone PC.

In order to run a Visual DataFlex Windows application on a Windows workstation from a server, the Visual DataFlex Client Engine has to be installed on the server, and the workstation needs to know the location of the VDF Client Engine. The way the workstation knows where to find the VDF Client Engine is via Registry settings installed by the VDFCEI. The question is how to get these Registry settings onto each workstation. There are 2 common approaches:

  1. Install the VDFCEI from each workstation to the server
  1. Run the VDFCEI on one workstation, while pointing it at the desired server location (via a mapped drive or \\ServerName\Path). This will install the VDF Client Engine on the server, while registering its location on the workstation.
  2. Run the VDFCEI on each workstation the same way as you did on the first. 
  3. You will only have to execute the Visual DataFlex Registration program only once. This will register the license on the server. All workstations will then have access to the registration information on the server.
  1. Install the VDFCEI from one workstation to the server, then import the required Registry settings on the remaining workstation
  1. Run the VDFCEI on one workstation, while pointing it at the desired server location (via a mapped drive or \\ServerName\Path). This will install the VDF Client Engine on the server, while registering its location on the workstation.
  2. Export the Registry settings installed by the VDFCEI on this workstation to Registry (.reg) files.
    You have to export the following Registry keys:
    • HKey_Local_Machine\Software\Data Access Worldwide
      The Registry settings in this key must be installed on each workstation
    • HKey_Classes_Root\VDFWorkspace.Document
      The Registry settings in this key are only needed to allow double-clicking and registering workspace (.ws) files.
  3. Place the .reg files with the exported Registry keys on a removable disk or a network location that all workstation have access to.
  4. Import the Registry settings on each of the remaining workstations.
  5. Ensure that the required minimum revisions of the below DLLs are installed on each workstation.
    The VDFCEI does this for you, but you'll have to make sure the workstation where you do not run the VDFCEI get these minimum DLL versions as well.
    • psapi.dll = 4.0.1371.1
    • msvcrt.dll = 6.0.8797.0
    • mfc42.dll = 6.0.8665.0

2. Deploy Your Windows Application

Once the Visual DataFlex Client Engine is installed via the VDFCEI, you need to install your application.

This may include any or all of the following:

Configuring Deployed Workspaces

The best way to simplify application installation is to mirror the workspace setup of your development environment on the deployment PC. If you need to change the workspace setup to be different than on your development PC, you will have to modify the workspace (.ws) file installed with your application accordingly.

Files to Install

Generally, files in the data, programs, help and bitmaps folders of a Windows application workspace are deployed. So, your deployed workspace's folder structure should look like this:

\Workspace
    \bitmaps
    \data
    \help
    \programs

The files listed below are only those created by the Visual DataFlex development tools when building a VDF application. If your application uses additional files, you must deploy these as well.

  • data folder

Depending on the database you are using, the required files may vary. If you are using databases in your application other than the embedded (DataFlex) database, please consult the documentation for those databases and drivers (Connectivity Kits) about additional files that may need to be distributed.

  • Embedded (DataFlex) database:
    filelist.cfg, *.dat, *.hdr, *.k??, *.tag, *.vld (if present)
  • Pervasive.SQL:
    filelist.cfg, *.btr, *.int, *.ddf, codemast.*, codetype.*
  • Microsoft.SQL:
    filelist.cfg, *.mdf, *.int, codemast.*, codetype.*
  • programs folder
  • *.exe - compiled program files
  • *.ws - workspace file(s)
    You must install the workspace (.ws) file for your workspace in the same folder where your compiled program (.exe) resides, unless you specify the path to this file in your application.
  • help folder

If you have created help files for your application, you want to deploy these. If you are using HTML Help, you should only need to deploy *.chm. Consult the documentation of the help authoring system you use for more details about which files you need to deploy. 

  • bitmaps folder

If you are taking advantage of the ability to embed bitmaps and icons as resources into a compiled application, you do not have to deploy those bitmap and icon files separately.

The necessary files for the FlexCOM component of Visual DataFlex, which allows ActiveX controls to integrate with VDF, are automatically installed by the VDFCEI.

You must install and register any files for the ActiveX controls your application uses. This must be done on each workstation running your application. Consult the documentation provided with the specified controls on how to install them at a client site.

You only need to deploy .ocp files if you are using FlexCOM 1. If you are using FlexCOM2 (any ActiveX controls imported and managed by the Visual DataFlex Studio starting with Visual DataFlex 8.3), you no longer need to distribute these files. You should see these files in Programs folder if they are used by your application.

Due to numerous developer requests, the Crystal Reports runtime is no longer installed as part of the VDFCEI. Thus, if your application includes Crystal Reports reports, you must install the required files to run Crystal Reports reports yourself.

Crystal Reports 9

This section will show files needed for the DataFlex Connectivity Kit for Crystal Reports 9. You need to know which version of the Connectivity Kit you are using to determine which files you need to deploy.

The Visual DataFlex 9.1 development installation does not install Crystal Reports or the Crystal Reports Connectivity Kit. You must install Crystal Reports 9 and the DataFlex Connectivity Kit for Crystal Reports 9 separately to develop Crystal Reports 9 reports for use with Visual DataFlex applications.

This section tells you which files you need to install with your Visual DataFlex application to run Crystal Reports 9 .rpt files. If you are deploying reports developed in Crystal Reports 8, please see the Crystal Reports 8 section. If you are using versions of Crystal Reports other than 9 or 8, please consult the Crystal Reports documentation of that revision for more details on which files to deploy with your reports.

The files listed here are those you need to install for any Crystal Reports 9 report. Most likely, other files will be needed for specific reports, such as files for certain export formats. We recommend that you always install all of the Crystal Reports runtime files, so you never had to worry about a missing file for a specific report. This includes all DLLs in the C:\Program Files\Common Files\Crystal Decisions\2.0\bin folder.

Consult the Crystal Reports 9 Developer Runtime Help (C:\Program Files\Crystal Decisions\Crystal Reports 9\Developer Files\Help\En\Runtime.chm, installed with the Crystal Reports 9 developer edition) for more information about the files that make up the Crystal Reports 9 runtime.

To see which of the Crystal Reports 9 runtime files are necessary for a specific report, open the report in Crystal Reports 9 and check the list of DLLs displayed when clicking on the More Info button from the Help | About Crystal Reports menu.

The More Info button may list winmm.dll, msshrui.dll and other DLLs that are part of the Windows operating system. Do not distribute these files with your report. These files are part of the Windows operating system and are operating system and build specific.

Files

  • WindowsSystemDir refers to the full path to the Windows System folder, the folder in which Windows system files are installed on the current PC. The default value for this on Windows 98, ME and XP is c:\Windows\System. The default value for this on Windows NT 4, 2000 and 2003 is c:\WinNT\System32.
  • RtDeployPath refers to the full path to the folder in which the VDFCEI is installed on the deployment PC.
  • CrystalReportsDevPath refers to the full path to the folder in which the Crystal Reports development license is installed on your development PC. This should be C:\Program Files\Common Files\Crystal Decisions\2.0\bin.

Crystal Reports 9 32-bit Runtime files

Development Location Destination Location
CrystalReportsDevPath\crpe32.dll RtDeployPath\bin\crpe32.dll
CrystalReportsDevPath\crqe.dll * RtDeployPath\bin\crqe.dll
CrystalReportsDevPath\crwrap32.dll ** RtDeployPath\bin\crwrap32.dll
CrystalReportsDevPath\Implode.dll *** RtDeployPath\bin\Implode.dll
CrystalReportsDevPath\querybuilder.dll RtDeployPath\bin\querybuilder.dll
CrystalReportsDevPath\ufmanager.dll RtDeployPath\bin\ufmanager.dll
CrystalReportsDevPath\unicows.dll **** RtDeployPath\bin\unicows.dll
WindowsSystemDir\msvcrt.dll ***** RtDeployPath\bin\msvcrt.dll
WindowsSystemDir\msvcp60.dll ****** RtDeployPath\bin\msvcp60.dll
WindowsSystemDir\riched20.dll RtDeployPath\bin\riched20.dll
WindowsSystemDir\usp10.dll RtDeployPath\bin\usp10.dll

* You must register crqe.dll on each workstation that will run your Crystal Reports 9 reports. Most installation tools, like Wise Installer, have automated methods for doing this. The manual way to do this is as follows:

 
Start > Run > regsvr32 RtDeployPath\bin\crqe.dll

Remember to place quotes around RtDeployPath\bin\crqe.dll if this path contains a space.

** Include crwrap32.dll if your application makes calls to Crystal Reports functions ExportToDisk, ExportToMapi, ExportToHTML, ExportToODBC, SelectPrinter or GetSelectedPrinter.
*** Include Implode.dll only for applications using reports created in versions previous to Crystal Reports 8.
**** Include unicows.dll only for applications installed on Win9x machines. Due to licensing restrictions, you must get unicows.dll from the Microsoft web site. Go to http://www.microsoft.com/msdownload/platformsdk/sdkupdate/default.htm? and select "Microsoft Layer for Unicode on Windows 95/98/ME Systems (MSLU) version 1.0".
***** Msvcrt.dll should only be installed if it does not already exist on the deployment PC.
****** Msvcp60.dll should only be installed if it does not already exist on the deployment PC.

DataFlex Connectivity Kit for Crystal Reports 9 files

Development Location Destination Location
CrystalReportsDevPath\p2bdfapi.dll RtDeployPath\bin\p2bdfapi.dll
CrystalReportsDevPath\crdb_p2bdfapi.dll RtDeployPath\bin\crdb_p2bdfapi.dll
WindowsSystemDir\apidll.dll RtDeployPath\bin\apidll.dll
WindowsSystemDir\df_collate.cfg RtDeployPath\bin\df_collate.cfg

The reason the files in the chart have been moved from the development computer's \WindowsSystemDir to the deployment computer's \bin folder is to avoid possible conflicts with software already loaded on the deployment computers. This chart assumes you are using Crystal Reports .rpt files with your Visual DataFlex application.

If you are using Crystal Reports .exe files (with all the required distribution files), you need to copy the .exe (and distribution files) to the \bin folder so the Connectivity Kit files listed in the chart can be found by the .exe program. If your .exe files cannot be located in the \bin folder, then the Connectivity files listed in the chart need to be copied to the deployment \WindowsSystemDir or to the same folder as the .exe (and distribution files). If the Connectivity Kit files are copied to the deployment computer’s \WindowsSystemDir folder be sure to check that no conflicts with other software exist.

Crystal Reports 8

This section will show files needed for the DataFlex Connectivity Kit for Crystal Reports, version 2.0. You need to know which version of the Connectivity Kit you are using to determine which files you need to deploy.

The Visual DataFlex 9.1 development installation does not install Crystal Reports or the Crystal Reports Connectivity Kit. You must install Crystal Reports 8 and the DataFlex Connectivity Kit for Crystal Reports, version 2.0 separately to develop Crystal Reports 8 reports for use with Visual DataFlex applications.

This section tells you which files you need to install with your Visual DataFlex application to run Crystal Reports 8 .rpt files. If you are deploying reports developed in Crystal Reports 9, please see the Crystal Reports 9 section. If you are using versions of Crystal Reports other than 9 or 8, please consult the Crystal Reports documentation of that revision for more details on which files to deploy with your reports.

The files listed here are those you need to install for any Crystal Reports 8 report. Most likely, other files will be needed for specific reports, such as files for certain export formats. We recommend that you always install all of the Crystal Reports 8 runtime files, so you never had to worry about a missing file for a specific report. Consult the Crystal Reports 8 documentation to see which files make up the Crystal Reports 8 runtime.

To see which of the Crystal Reports 8 runtime files are necessary for a specific report, open the report in Crystal Reports 8 and check the list of DLLs displayed when clicking on the More Info button from the Help | About Crystal Reports menu.

The More Info button may list winmm.dll, msshrui.dll and other DLLs that are part of the Windows operating system. Do not distribute these files with your report. These files are part of the Windows operating system and are operating system and build specific.

Crystal Reports 8 installs numerous files into your Windows System folder. When deploying your application, these files should be installed into the \visual dataflex 9.1\bin folder instead, so that they do not interfere with existing Crystal Reports installations, which may be Crystal Reports revisions different from 8.

Files

  • WindowsSystemDir refers to the full path to the Windows System folder, the folder in which Windows system files are installed on the current PC. The default value for this on Windows 98, ME and XP is c:\Windows\System. The default value for this on Windows NT 4, 2000 and 2003 is c:\WinNT\System32.
  • RtDeployPath refers to the full path to the folder in which the VDFCEI is installed on the deployment PC.
  • VDFDevPath refers to the full path to the folder in which your Visual DataFlex development license is installed on your development PC

Crystal Reports 8 32-bit Client Engine files

Development Location Destination Location
WindowsSystemDir\Crpe32.dll RtDeployPath\bin\Crpe32.dll
WindowsSystemDir\implode.dll RtDeployPath\bin\implode.dll
WindowsSystemDir\mfc42.dll RtDeployPath\bin\mfc42.dll
WindowsSystemDir\msvcirt.dll RtDeployPath\bin\msvcirt.dll
WindowsSystemDir\msvcp60.dll * RtDeployPath\bin\msvcp60.dll

* Msvcp60.dll should only be installed if it does not already exist on the deployment PC.

DataFlex Connectivity Kit for Crystal Reports 8 version 2.0 files

Development Location Destination Location
WindowsSystemDir\Apidll.dll RtDeployPath\bin\Apidll.dll
WindowsSystemDir\Crystal\P2bdfapi.dll RtDeployPath\bin\P2bdfapi.dll
VDFDevPath\bin\Crpaig80.dll RtDeployPath\bin\Crpaig80.dll
WindowsSystemDir\df_collate.cfg RtDeployPath\bin\df_collate.cfg

The reason the files in the chart have been moved from the development computer's \WindowsSystemDir to the deployment computer's \bin folder is to avoid possible conflicts with software already loaded on the deployment computers. This chart assumes you are using Crystal Reports .rpt files with your Visual DataFlex application.

If you are using Crystal Reports .exe files (with all the required distribution files), you need to copy the .exe (and distribution files) to the \bin folder so the Connectivity Kit files listed in the chart can be found by the .exe program. If your .exe files cannot be located in the \bin folder, then the Connectivity files listed in the chart need to be copied to the deployment \WindowsSystemDir or to the same folder as the .exe (and distribution files). If the Connectivity Kit files are copied to the deployment computer’s \WindowsSystemDir folder be sure to check that no conflicts with other software exist.

2. Deploying a Visual DataFlex Web Application

Deploying a Visual DataFlex 9.1 Web application involves only 2 steps:

1. Install the Visual DataFlex Server Installation
2. Deploy Your Web Application

1. Visual DataFlex Web Application Server Installation

The Visual DataFlex Web Application Server Installation (VDFWASI) is an installation program, provided by Data Access Worldwide, that installs the Visual DataFlex Web Application Server, Web Application Administrator, Database Builder, Database Explorer and Error Codes Maintenance.

The VDFWASI always installs all files and makes all necessary Windows Registry settings to allow Visual DataFlex Web applications to run on the destination computer.

You can download the most current Visual DataFlex Web Application Server Installation for the version of Visual DataFlex you are using from the download section of our Web site: http://www.dataaccess.com.

You may choose to develop an installation program for your Visual DataFlex application(s) using any available software installation tool, such as Wise Installer or InstallShield. For licensing reasons, you must install the Visual DataFlex Web Application Server using the VDFWASI. You can implement this by calling the VDFWASI program from your installation program.

2. Deploy Your Web Application

Once the Visual DataFlex Web Application Server is installed via the VDFWASI, you need to install the files needed by your application.

This may include any or all of the following:

  • Configuring Deployed Workspaces

The best way to simplify application installation is to mirror the workspace setup of your development environment on the deployment PC. If you need to change the workspace setup to be different than on your development PC, you will have to modify the workspace (.ws) file installed with your application.

  • Files to Install

Generally, files in the apphtml, data, and programs folders of a Web application workspace are deployed. So, your deployed workspace's folder structure should look like this:

\Workspace
    \apphtml
    \data
    \programs

The files listed below are only those created by the Visual DataFlex development tools when building a VDF application. If your application uses additional files, you must deploy these as well.

  • apphtml folder
  • global.asa, *.asp, *.htm?
  • apphtml\css\*.css
  • apphtml\images\*.*
  • apphtml\inc\*.inc
  • data folder

Depending on the database you are using, the required files may vary. If you are using databases in your application other than the embedded (DataFlex) database, please consult the documentation for those databases and drivers (Connectivity Kits) about additional files that may need to be distributed.

  • Embedded (DataFlex) database:
    filelist.cfg, *.dat, *.hdr, *.k??, *.tag, *.vld (if present)
  • Pervasive.SQL:
    filelist.cfg, *.btr, *.int, *.ddf, codemast.*, codetype.*
  • Microsoft.SQL:
    filelist.cfg, *.mdf, *.int, codemast.*, codetype.*
  • programs folder
  • webapp.exe - compiled Web application file
  • *.ws - workspace file(s)
    You must install the workspace (.ws) file for your workspace in the same folder where your compiled program (.exe) resides, unless you specify the path to this file in your application.

An Internet Information Server (IIS)-based Web Application requires a virtual directory (sometimes called a web share) to run in. This is the second part of the path that is used to access a Web Application:

http://ServerName/VirtualDirectoryName/FileName.asp

For example, the Visual DataFlex WebAppSample91 sample application typically uses this URL to be accessed:

http://localhost/WebAppSample91/default.asp

where WebAppSample91 is the name of the virtual directory this sample application runs in.

To help create virtual directories programmatically, the VDFWASI installs a program named wincrtvdir.exe. This program is installed in the bin folder of your Visual DataFlex installation and accepts parameters for creating virtual directories. There are 2 calls required to create a working virtual directory:

1. wincrtvdir.exe -q CD WindowsFolderName VirtualDirectoryName 513
2. wincrtvdir.exe -q CA w3svc/1/root/VirtualDirectoryName INPROC

where:

- WindowsFolderName is the name of the AppHtml folder for which the virtual directory is to be created
- VirtualDirectoryName is the name of the virtual directory to be created

For example, the calls to create the virtual directory for the WebAppSample91 sample application are these:

1. "c:\program files\visual dataflex 9.1\bin\wincrtvdir.exe" -q CD "C:\Program Files\Visual Dataflex 9.1\Examples\Web\WebAppSample91\AppHtml" WebAppSample91 513

2. "c:\program files\visual dataflex 9.1\bin\wincrtvdir.exe" -q CA w3svc/1/root/WebAppSample91 INPROC

  • Creating and Setting Registry Settings

    All VDF Web Application Server-specific and utility-specific Registry settings are installed by the VDFWASI.

    If there are Registry settings required for your application, you must install them as part of your application installation.

There are 2 ways you can register a Visual DataFlex Web Application for the Web Application Administrator (and the Visual DataFlex Web Application Service):

  1. Via the Visual DataFlex Web Application Administrator

Click on the New Web Application button and follow the steps outlined by the New Web Application wizard.

  1. By installing the required Registry settings for the application

For each Web Application, a set of Registry settings needs to be installed. A Registry key with the Web Application Name must be installed into the key HKey_Local_Machine\Software\Visual DataFlex\9.1\WebApp Server.

For example, the Registry key for the WebAppSample91 sample application is:

HKey_Local_Machine\Software\Visual DataFlex\9.1\WebApp Server\WebAppSample91

You need to install a number of Registry values into the Registry key for your web application. When you are finished, the Registry values for your web application should look like the image below.

After you have installed the Registry settings for your web application, the Visual DataFlex Web Application Server Service will immediately start the application if the service is running or it will automatically start the application the next time the service is started (after a reboot, for example).

3. Deploying a Visual DataFlex Windows & Web Application

In most cases, a Visual DataFlex Web and Windows application would not be hosted on the same server. Typically, one Windows server is used for hosting a Web Application (web server) and another server is used for hosting Windows applications. Occasionally, however, there are application that do have Windows and Web components.

Deploying a Visual DataFlex 9.1 combined Windows and Web application involves only 3 steps:

  1. Install the Visual DataFlex Web Application Server Installation
  2. Deploy Your Combined Application
  3. Register Visual DataFlex Windows Client License

1. Visual DataFlex Web Application Server Installation

The Visual DataFlex Web Application Server Installation (VDFWASI) is an installation program, provided by Data Access Worldwide, that installs the Visual DataFlex Web Application Server, Web Application Administrator, Database Builder, Database Explorer and Error Codes Maintenance.

The VDFWASI always installs all files and makes all necessary Windows Registry settings to allow Visual DataFlex Web applications to run on the destination computer.

You can download the most current Visual DataFlex Web Application Server Installation for the version of Visual DataFlex you are using from the download section of our Web site: http://www.dataaccess.com.

You may choose to develop an installation program for your Visual DataFlex application(s) using any available software installation tool, such as Wise Installer or InstallShield. For licensing reasons, you must install the Visual DataFlex Web Application Server using the VDFWASI. You can implement this by calling the VDFWASI program from your installation program.

VDFCEI Network Installation

In order to run a Visual DataFlex Windows application on a Windows workstation from a server, the Visual DataFlex Client Engine has to be installed on the server, and the workstation needs to know the location of the VDF Client Engine. The way the workstation knows where to find the VDF Client Engine is via Registry settings installed by the VDFCEI. The question is how to get these Registry settings onto each workstation. There are 2 common approaches:

  1. Install the VDFCEI from each workstation to the server
  1. Run the VDFCEI on one workstation, while pointing it at the desired server location (via a mapped drive or \\ServerName\Path). This will install the VDF Client Engine on the server, while registering its location on the workstation.
  2. Run the VDFCEI on each workstation the same way as you did on the first. 
  3. You will only have to execute the Visual DataFlex Registration program only once. This will register the license on the server. All workstations will then have access to the registration information on the server.
  1. Install the VDFCEI from one workstation to the server, then import the required Registry settings on the remaining workstation
  1. Run the VDFCEI on one workstation, while pointing it at the desired server location (via a mapped drive or \\ServerName\Path). This will install the VDF Client Engine on the server, while registering its location on the workstation.
  2. Export the Registry settings installed by the VDFCEI on this workstation to Registry (.reg) files.
    You have to export the following Registry keys:
    • HKey_Local_Machine\Software\Data Access Worldwide
      The Registry settings in this key must be installed on each workstation
    • HKey_Classes_Root\VDFWorkspace.Document
      The Registry settings in this key are only needed to allow double-clicking and registering workspace (.ws) files.
  3. Place the .reg files with the exported Registry keys on a removable disk or a network location that all workstation have access to.
  4. Import the Registry settings on each of the remaining workstations.
  5. Ensure that the required minimum revisions of the below DLLs are installed on each workstation.
    The VDFCEI does this for you, but you'll have to make sure the workstation where you do not run the VDFCEI get these minimum DLL versions as well.
    • psapi.dll = 4.0.1371.1
    • msvcrt.dll = 6.0.8797.0
    • mfc42.dll = 6.0.8665.0

2. Deploy Your Combined Application

Once the Visual DataFlex Web Application Server is installed via the VDFWASI and the client license registered, you need to install your application.

This may include any or all of the following:

Configuring Deployed Workspaces

The best way to simplify application installation is to mirror the workspace setup of your development environment on the deployment PC. If you need to change the workspace setup to be different than on your development PC, you will have to modify the workspace (.ws) file installed with your application accordingly.

Files to Install

Generally, files in the apphtml, data, programs, help and bitmaps folders of a Windows application workspace are deployed. So, your deployed workspace's folder structure should look like this:

\Workspace
    \apphtml
    \bitmaps
    \data
    \help
    \programs

The files listed below are only those created by the Visual DataFlex development tools when building a VDF application. If your application uses additional files, you must deploy these as well.

  • apphtml folder
  • global.asa, *.asp, *.htm?
  • apphtml\css\*.css
  • apphtml\images\*.*
  • apphtml\inc\*.inc
  • data folder

Depending on the database you are using, the required files may vary. If you are using databases in your application other than the embedded (DataFlex) database, please consult the documentation for those databases and drivers (Connectivity Kits) about additional files that may need to be distributed.

  • Embedded (DataFlex) database:
    filelist.cfg, *.dat, *.hdr, *.k??, *.tag, *.vld (if present)
  • Pervasive.SQL:
    filelist.cfg, *.btr, *.int, *.ddf, codemast.*, codetype.*
  • Microsoft.SQL:
    filelist.cfg, *.mdf, *.int, codemast.*, codetype.*
  • programs folder
  • webapp.exe - compiled Web application file
  • *.exe - compiled Windows program files
  • *.ws - workspace file(s)
    You must install the workspace (.ws) file for your workspace in the same folder where your compiled program (.exe) resides, unless you specify the path to this file in your application.
  • help folder

If you have created help files for your application, you want to deploy these. If you are using HTML Help, you should only need to deploy *.chm. Consult the documentation of the help authoring system you use for more details about which files you need to deploy. 

  • bitmaps folder

If you are taking advantage of the ability to embed bitmaps and icons as resources into a compiled application, you do not have to deploy those bitmap and icon files separately.

  • Creating a Virtual Directory

    An Internet Information Server (IIS)-based Web Application requires a virtual directory (sometimes called a web share) to run in. This is the second part of the path that is used to access a Web Application:

    http://ServerName/VirtualDirectoryName/FileName.asp

    For example, the Visual DataFlex WebAppSample91 sample application typically uses this URL to be accessed:

    http://localhost/WebAppSample91/default.asp

    where WebAppSample91 is the name of the virtual directory this sample application runs in.

    To help create virtual directories programmatically, the VDFWASI installs a program named wincrtvdir.exe. This program is installed in the bin folder of your Visual DataFlex installation and accepts parameters for creating virtual directories. There are 2 calls required to create a working virtual directory:

    1. wincrtvdir.exe -q CD WindowsFolderName VirtualDirectoryName 513
    2. wincrtvdir.exe -q CA w3svc/1/root/VirtualDirectoryName INPROC

    where:

    - WindowsFolderName is the name of the AppHtml folder for which the virtual directory is to be created
    - VirtualDirectoryName is the name of the virtual directory to be created

    For example, the calls to create the virtual directory for the WebAppSample91 sample application are these:

    1. "c:\program files\visual dataflex 9.1\bin\wincrtvdir.exe" -q CD "C:\Program Files\Visual Dataflex 9.1\Examples\Web\WebAppSample91\AppHtml" WebAppSample91 513

    2. "c:\program files\visual dataflex 9.1\bin\wincrtvdir.exe" -q CA w3svc/1/root/WebAppSample91 INPROC

  • Creating and Setting Registry Settings

    All VDF Client Engine-specific and utility-specific Registry settings are installed by the VDFWASI.

    If there are Registry settings required for your application, you must install them as part of your application installation.

The necessary files for the FlexCOM component of Visual DataFlex, which allows ActiveX controls to integrate with VDF, are automatically installed by the VDFWASI.

You must install and register any files for the ActiveX controls your application uses. This must be done on each workstation running your application. Consult the documentation provided with the specified controls on how to install them at a client site.

You only need to deploy .ocp files if you are using FlexCOM 1. If you are using FlexCOM2 (any ActiveX controls imported and managed by the Visual DataFlex Studio starting with Visual DataFlex 8.3), you no longer need to distribute these files. You should see these files in Programs folder if they are used by your application.

There are 2 ways you can register a Visual DataFlex Web Application for the Web Application Administrator (and the Visual DataFlex Web Application Service):

  1. Via the Visual DataFlex Web Application Administrator

Click on the New Web Application button and follow the steps outlined by the New Web Application wizard.

  1. By installing the required Registry settings for the application

For each Web Application, a set of Registry settings needs to be installed. A Registry key with the Web Application Name must be installed into the key HKey_Local_Machine\Software\Visual DataFlex\9.1\WebApp Server.

For example, the Registry key for the WebAppSample91 sample application is:

HKey_Local_Machine\Software\Visual DataFlex\9.1\WebApp Server\WebAppSample91

You need to install a number of Registry values into the Registry key for your web application. When you are finished, the Registry values for your web application should look like the image below.

After you have installed the Registry settings for your web application, the Visual DataFlex Web Application Server Service will immediately start the application if the service is running or it will automatically start the application the next time the service is started (after a reboot, for example).

The Crystal Reports runtime is not installed as part of the VDFWASI. Thus, if your application includes Crystal Reports reports, you must install the required files to run Crystal Reports reports yourself.

Crystal Reports 9

This section will show files needed for the DataFlex Connectivity Kit for Crystal Reports 9. You need to know which version of the Connectivity Kit you are using to determine which files you need to deploy.

The Visual DataFlex 9.1 development installation does not install Crystal Reports or the Crystal Reports Connectivity Kit. You must install Crystal Reports 9 and the DataFlex Connectivity Kit for Crystal Reports 9 separately to develop Crystal Reports 9 reports for use with Visual DataFlex applications.

This section tells you which files you need to install with your Visual DataFlex application to run Crystal Reports 9 .rpt files. If you are deploying reports developed in Crystal Reports 8, please see the Crystal Reports 8 section. If you are using versions of Crystal Reports other than 9 or 8, please consult the Crystal Reports documentation of that revision for more details on which files to deploy with your reports.

The files listed here are those you need to install for any Crystal Reports 9 report. Most likely, other files will be needed for specific reports, such as files for certain export formats. We recommend that you always install all of the Crystal Reports runtime files, so you never had to worry about a missing file for a specific report. This includes all DLLs in the C:\Program Files\Common Files\Crystal Decisions\2.0\bin folder.

Consult the Crystal Reports 9 Developer Runtime Help (C:\Program Files\Crystal Decisions\Crystal Reports 9\Developer Files\Help\En\Runtime.chm, installed with the Crystal Reports 9 developer edition) for more information about the files that make up the Crystal Reports 9 runtime.

To see which of the Crystal Reports 9 runtime files are necessary for a specific report, open the report in Crystal Reports 9 and check the list of DLLs displayed when clicking on the More Info button from the Help | About Crystal Reports menu.

The More Info button may list winmm.dll, msshrui.dll and other DLLs that are part of the Windows operating system. Do not distribute these files with your report. These files are part of the Windows operating system and are operating system and build specific.

Files

  • WindowsSystemDir refers to the full path to the Windows System folder, the folder in which Windows system files are installed on the current PC. The default value for this on Windows 98, ME and XP is c:\Windows\System. The default value for this on Windows NT 4, 2000 and 2003 is c:\WinNT\System32.
  • RtDeployPath refers to the full path to the folder in which the VDFWASI is installed on the deployment PC.
  • CrystalReportsDevPath refers to the full path to the folder in which the Crystal Reports development license is installed on your development PC. This should be C:\Program Files\Common Files\Crystal Decisions\2.0\bin.

Crystal Reports 9 32-bit Runtime files

Development Location Destination Location
CrystalReportsDevPath\crpe32.dll RtDeployPath\bin\crpe32.dll
CrystalReportsDevPath\crqe.dll * RtDeployPath\bin\crqe.dll
CrystalReportsDevPath\crwrap32.dll ** RtDeployPath\bin\crwrap32.dll
CrystalReportsDevPath\Implode.dll *** RtDeployPath\bin\Implode.dll
CrystalReportsDevPath\querybuilder.dll RtDeployPath\bin\querybuilder.dll
CrystalReportsDevPath\ufmanager.dll RtDeployPath\bin\ufmanager.dll
CrystalReportsDevPath\unicows.dll **** RtDeployPath\bin\unicows.dll
WindowsSystemDir\msvcrt.dll ***** RtDeployPath\bin\msvcrt.dll
WindowsSystemDir\msvcp60.dll ****** RtDeployPath\bin\msvcp60.dll
WindowsSystemDir\riched20.dll RtDeployPath\bin\riched20.dll
WindowsSystemDir\usp10.dll RtDeployPath\bin\usp10.dll

* You must register crqe.dll on each workstation that will run your Crystal Reports 9 reports. Most installation tools, like Wise Installer, have automated methods for doing this. The manual way to do this is as follows:

Start > Run > regsvr32 RtDeployPath\bin\crqe.dll

Remember to place quotes around RtDeployPath\bin\crqe.dll if this path contains a space.

** Include crwrap32.dll if your application makes calls to Crystal Reports functions ExportToDisk, ExportToMapi, ExportToHTML, ExportToODBC, SelectPrinter or GetSelectedPrinter.
*** Include Implode.dll only for applications using reports created in versions previous to Crystal Reports 8.
**** Include unicows.dll only for applications installed on Win9x machines. Due to licensing restrictions, you must get unicows.dll from the Microsoft web site. Go to http://www.microsoft.com/msdownload/platformsdk/sdkupdate/default.htm? and select "Microsoft Layer for Unicode on Windows 95/98/ME Systems (MSLU) version 1.0".
***** Msvcrt.dll should only be installed if it does not already exist on the deployment PC.
****** Msvcp60.dll should only be installed if it does not already exist on the deployment PC.

DataFlex Connectivity Kit for Crystal Reports 9 files

Development Location Destination Location
CrystalReportsDevPath\p2bdfapi.dll RtDeployPath\bin\p2bdfapi.dll
CrystalReportsDevPath\crdb_p2bdfapi.dll RtDeployPath\bin\crdb_p2bdfapi.dll
WindowsSystemDir\apidll.dll RtDeployPath\bin\apidll.dll
WindowsSystemDir\df_collate.cfg RtDeployPath\bin\df_collate.cfg

The reason the files in the chart have been moved from the development computer's \WindowsSystemDir to the deployment computer's \bin folder is to avoid possible conflicts with software already loaded on the deployment computers. This chart assumes you are using Crystal Reports .rpt files with your Visual DataFlex application.

If you are using Crystal Reports .exe files (with all the required distribution files), you need to copy the .exe (and distribution files) to the \bin folder so the Connectivity Kit files listed in the chart can be found by the .exe program. If your .exe files cannot be located in the \bin folder, then the Connectivity files listed in the chart need to be copied to the deployment \WindowsSystemDir or to the same folder as the .exe (and distribution files). If the Connectivity Kit files are copied to the deployment computer’s \WindowsSystemDir folder be sure to check that no conflicts with other software exist.

Crystal Reports 8

This section will show files needed for the DataFlex Connectivity Kit for Crystal Reports, version 2.0. You need to know which version of the Connectivity Kit you are using to determine which files you need to deploy.

The Visual DataFlex 9.1 development installation does not install Crystal Reports or the Crystal Reports Connectivity Kit. You must install Crystal Reports 8 and the DataFlex Connectivity Kit for Crystal Reports, version 2.0 separately to develop Crystal Reports 8 reports for use with Visual DataFlex applications.

This section tells you which files you need to install with your Visual DataFlex application to run Crystal Reports 8 .rpt files. If you are deploying reports developed in Crystal Reports 9, please see the Crystal Reports 9 section. If you are using versions of Crystal Reports other than 9 or 8, please consult the Crystal Reports documentation of that revision for more details on which files to deploy with your reports.

The files listed here are those you need to install for any Crystal Reports 8 report. Most likely, other files will be needed for specific reports, such as files for certain export formats. We recommend that you always install all of the Crystal Reports 8 runtime files, so you never had to worry about a missing file for a specific report. Consult the Crystal Reports 8 documentation to see which files make up the Crystal Reports 8 runtime.

To see which of the Crystal Reports 8 runtime files are necessary for a specific report, open the report in Crystal Reports 8 and check the list of DLLs displayed when clicking on the More Info button from the Help | About Crystal Reports menu.

The More Info button may list winmm.dll, msshrui.dll and other DLLs that are part of the Windows operating system. Do not distribute these files with your report. These files are part of the Windows operating system and are operating system and build specific.

Crystal Reports 8 installs numerous files into your Windows System folder. When deploying your application, these files should be installed into the \visual dataflex 9.1\bin folder instead, so that they do not interfere with existing Crystal Reports installations, which may be Crystal Reports revisions different from 8.

Files

  • WindowsSystemDir refers to the full path to the Windows System folder, the folder in which Windows system files are installed on the current PC. The default value for this on Windows 98, ME and XP is c:\Windows\System. The default value for this on Windows NT 4, 2000 and 2003 is c:\WinNT\System32.
  • RtDeployPath refers to the full path to the folder in which the VDFWASI is installed on the deployment PC.
  • VDFDevPath refers to the full path to the folder in which your Visual DataFlex development license is installed on your development PC

Crystal Reports 8 32-bit Client Engine files

Development Location Destination Location
WindowsSystemDir\Crpe32.dll RtDeployPath\bin\Crpe32.dll
WindowsSystemDir\implode.dll RtDeployPath\bin\implode.dll
WindowsSystemDir\mfc42.dll RtDeployPath\bin\mfc42.dll
WindowsSystemDir\msvcirt.dll RtDeployPath\bin\msvcirt.dll
WindowsSystemDir\msvcp60.dll * RtDeployPath\bin\msvcp60.dll

* Msvcp60.dll should only be installed if it does not already exist on the deployment PC.

DataFlex Connectivity Kit for Crystal Reports 8 version 2.0 files

Development Location Destination Location
WindowsSystemDir\Apidll.dll RtDeployPath\bin\Apidll.dll
WindowsSystemDir\Crystal\P2bdfapi.dll RtDeployPath\bin\P2bdfapi.dll
VDFDevPath\bin\Crpaig80.dll RtDeployPath\bin\Crpaig80.dll
WindowsSystemDir\df_collate.cfg RtDeployPath\bin\df_collate.cfg

The reason the files in the chart have been moved from the development computer's \WindowsSystemDir to the deployment computer's \bin folder is to avoid possible conflicts with software already loaded on the deployment computers. This chart assumes you are using Crystal Reports .rpt files with your Visual DataFlex application.

If you are using Crystal Reports .exe files (with all the required distribution files), you need to copy the .exe (and distribution files) to the \bin folder so the Connectivity Kit files listed in the chart can be found by the .exe program. If your .exe files cannot be located in the \bin folder, then the Connectivity files listed in the chart need to be copied to the deployment \WindowsSystemDir or to the same folder as the .exe (and distribution files). If the Connectivity Kit files are copied to the deployment computer’s \WindowsSystemDir folder be sure to check that no conflicts with other software exist.

3. Register Visual DataFlex Windows Client License

Install the registration code for your Visual DataFlex Windows client license using the VDF Registration tool: Start > Programs > Visual DataFlex 9.1 > Register Visual DataFlex. Add this registration code to the existing code or codes already on the registration list.

The VDFWASI automatically installs a 1 user VDF Windows client registration code so that you can run tools such as Database Builder on the web server. Thus, installing a Windows client registration will add 1 to the number of users on that license. For example, installing a 10 user VDF Windows client license will allow access for 11 users.

Miscellaneous Deployment Issues

On Windows Server 2003, Active Server Pages (ASP) are not enabled by default even after installing Internet Information Server 6 (IIS). Since Visual DataFlex Web applications use ASP pages, you must enable this before your applications can run on Windows Server 2003.

To install IIS 6.0:
- Select Start | Manage Your Server (if Manage Your Server does not come up automatically)
- Select Add or Remove role on the right-top side of the panel
- Click Next on the first screen
- Select Custom Configuration and press Next
- Highlight Application Server (IIS, ASP.NET) and press Next
- Check the boxes to add tools you would like to install (not needed for ASP support)
- Review the options selected to confirm your options and press Next
- Wait until the installation is completed (the Windows 2003 CD may be needed) and click Finish at the "This Server is Now an Application server" panel


After having IIS 6.0 installed, you will still not be able to run WebApp Server applications on it. You need to enable ASP to run on that machine -- this is also disabled by default -- otherwise you will experience 404 error messages when running the samples or even your applications.

In order to enable ASP, you need to:
- Select Start | Manage Your Server (if Manage Your Server does not come up automatically)
- Click on Manage this Application server
- Expand Internet Information Services (IIS) | <your_machine_name> (local computer)
- Highlight Web Service Extensions
- On the right-side panel, highlight Active Server Pages (the default status is prohibited)
- Click on the Allow button from the group of buttons on the left

  • Deploying the Workspaces.ini File

    The bin folder of your Visual DataFlex development system contains a file named workspaces.ini. This file contains the list of registered workspaces. It is used by any program that:

  1. Uses the package SelectWorkspace.dg (which includes VDF utilities, such as DataBase Builder and Database Explorer).
  2. To allow selection of different workspaces in any VDF application.
  3. VDF applications that use certain functions of the cWorkspace class, those functions that depend on the information in Workspaces.ini (like in GetWorkspaceFileName, IsRegistered and OpenWorkspace). For more information, refer to the Visual DataFlex 9 online help.

If you are not deploying any of our utilities and your applications do not do anything on the list above, you do not need to deploy workspaces.ini.

You can start Database Builder and Database Explorer in a specific workspace by passing a workspace file as a command line argument.

For example, this will start Database Builder in the Order Sample workspace:

"C:\Program Files\Visual DataFlex 9.1\bin\dbBldr" -w"C:\Program Files\Visual DataFlex 9.1\Examples\Windows\Order\Programs\DAW.Examples.Windows.Order.ws"

For example, this will start Database Explorer in the Order Sample workspace:

"C:\Program Files\Visual DataFlex 9.1\bin\dbExplor" "C:\Program Files\Visual DataFlex 9.1\Examples\Windows\Order\Programs\DAW.Examples.Windows.Order.ws"

  • "Current Workspace" Registry Setting

    If you deploy Database Builder or the Error Maintenance Utility, you should be aware that these utilities will attempt to open the workspace named in the Current Workspace Registry setting by default. So, be sure to set this Registry setting to the name of the workspace you wish to have the utilities open by default.

    The full path to the Current Workspace Registry setting for VDF 9.1 is:
    HKey_Current_User/Software/Data Access Worldwide/Visual DataFlex/9.1/Workspaces/Current Workspace

    NOTE: You will not be able to create a new workspace on a PC with only a VDFCEI installed.

You may have a need to create multiple workspaces to be accessed from the same application, for example, to provide different sets of some tables to different departments at a client site. The ability to do this is now easier and more controlled by the application developer than with prior VDF versions.

There is a complete code example of allowing an application to accept command line parameters to decide which workspace to open. View it in the Visual DataFlex Help (Start > Programs > Visual DataFlex 9.1 > Visual DataFlex Help > Class Reference > cWorkspace.

Data Access Corporation has several database drivers (Connectivity Kits) available:

  • DataFlex Connectivity Kit for Pervasive.SQL
  • DataFlex Connectivity Kit for IBM DB2 Universal Database
  • DataFlex Connectivity Kit for ODBC
  • DataFlex Connectivity Kit for Microsoft SQL Server

Visit the Client/Server Solutions page of the DAW Web Site to find out more information about our Connectivity Kits.

The Visual DataFlex Client Engine loads the driver(s) for any database you wish to use without having to recompile the application, so you can seamlessly switch to or access any database you wish to.

Please consult the documentation for the individual Connectivity Kits for installation information.

  • Finding DLLs

    The finding of DLLs (.dll files or dynamic link libraries) has changed from older revisions of Visual DataFlex that did not compile to .exe files (revisions 7 and prior). This may especially affect you if you use products such as Crystal Reports and/or one or more of our Connectivity Kits.

    The locations Windows executable (.exe) programs search for DLLs they need to load is these (in order):

    1. The same folder as the .exe file
    2. The Windows system folders
    3. Along the PATH

    In VDF revisions 7 and below, the main Windows executable file for VDF applications was dfrun.exe, which was located in the same folder (bin) where all related DLLs were installed. So, the DLLs installed there would be found first and any older versions of the same DLLs located in the Windows system folders were ignored. Now, older versions of DLLs used by VDF that are found in the Windows system folders may be loaded first, resulting in error messages from applications expecting newer versions of these DLLs.

    To solve this problem, you may have to install DLLs that cause such problems to the same folder where your compiled application (.exe) is located, so that they are found first by your application.

  • Using Universal Naming Convention (UNC)

You may want to consider using the Universal Naming Convention (UNC) for your network installations. This will prevent problems with mapped drive mismatches.

For example:

  • user 1 may have F: mapped to \\Server1\Drive1\Visual DataFlex 9.1
  • user 2 may have G: mapped to \\Server1\Drive1\Visual DataFlex 9.1

In this scenario, without using UNC, you would have to:

  • Customize each user's Registry entries or
  • Synchronize all user's drive mappings

Universal naming convention does not use mapped drives, but instead addresses networked folders and files using this method:

\\ServerName\ShareName\Path\FileName

where:

ServerName is the name of the server (PC) where the files are located
ShareName is the shared folder name where the files are located
Path is the additional path to the files (if applicable) below the shared folder
FileName is the name of the file (if applicable) to access

Windows 2003, 2000 and XP use a newer format for Registry files than do older version of Windows (98, ME and NT). When exporting Registry information from the Windows Registry Editor on a 2003, 2000 or XP machine, the default format is "Registration Files", which uses the 2003/2000/XP format, but you can also select "Win9x/NT4 Registration Files" as the format, which will export the information using the old file format. For network installations, the best tip is to export all necessary Registry settings in both formats, so that they can be imported onto any type of Windows PC.

This paper is intended as a technical guide for deploying VDF applications. Please see your VDF License Agreement or contact Data Access Worldwide for licensing issues. The license agreement should be located in the root folder of your VDF development installation (e.g. C:\Program Files\Visual DataFlex 9.1). 

You may pre-register a Client License for your client using the Visual DataFlex Registration utility (Start > Programs > Visual DataFlex 9.1 > Utilities > Register Visual DataFlex), and install the registration files as part of your application installation. The registration files are termlist.cfg and {Serial Number}.dfr (e.g. 123456.dfr), and should be placed in the bin folder of the deployment PC.

A separate install for Novell's Transaction Tracking System (TTS) support files has been produced for Visual DataFlex. The Visual DataFlex 9.1 TTS File Install Kit is available on the DAW Web Site.

Additional Reading

  • You may want to check for an updated version of this White Paper on our Web site from time to time. Many of our White Papers are updated as information changes. For those papers, the Last Edited date is always at the top of the paper.
  • The Visual DataFlex 9.1 Help: Start > Programs > Visual DataFlex 9.1 > Visual DataFlex Help
  • Opportunistic Locking and Read Caching on Microsoft Windows Networks, White Paper, Data Access Corporation, May 2002, available from the Download section of Data Access Website: http://www.dataaccess.com.
  • Integrating DataFlex with Netware, White Paper, Jim Albright, Wizard Systems, January 1997, available from the Download section of Data Access Website: http://www.dataaccess.com.

Contacting Data Access Worldwide

Data Access Worldwide
14000 SW 119 Ave
Miami, FL 33186
305-238-0012
Domestic Sales: 800-451-3539
Fax: 305-238-0017
email: sales@dataaccess.com
Newsgroup Server: news.dataaccess.com
Internet: http://www.dataaccess.com

Data Access Worldwide - Asia Pacific
Suite 5, 333 Wantirna Road, Wantirna VIC 3152 Australia
Phone: +61 3 9800 4233 f: +61 3 9800 4255
Sales: asiapacific@DataAccess.com
Support: support.asiapacific@DataAccess.com
Internet: http://www.DataAccess.com/AsiaPacific

Data Access Worldwide - Brasil
Av.Paulista, 1776 - 21st.Floor
São Paulo -SP - Brazil
CEP 01310-921
Phone: 5511-3262-2000
Fax 5511-3284-1579
Sales: info@dataaccess.com.br
Support: suporte@dataaccess.com.br
Internet: http://www.dataaccess.com.br

Data Access Worldwide - Europe
Lansinkesweg 4
7553 AE Hengelo
The Netherlands
Telephone: +31 (0)74 - 255 56 09
Fax: +31 (0)74 - 250 34 66
Sales: info@dataaccess.nl
Support: support@dataaccess.nl
Internet: http://www.dataaccess.nl

Data Access Technical Support
800-451-3539 / 305-232-3142
email: support@dataaccess.com
Visit our Support Home page to see all of our Support options: http://www.dataaccess.com/support

Data Access Technical Knowledge Base    http://www.dataaccess.com/kbase
Many answers to technical problems can be found online in the Data Access Technical Knowledge Base. Here, you can access the same live data that Data Access Worldwide technical support and development staff use to enter and track technical articles. 

Copyright Notice
This document is property of Data Access Corporation. With credit to Data Access Corporation for its authorship, you are encouraged to reproduce this information in any format either on paper or electronically, in whole or in part. You may publish this paper as a stand alone document within your own publications conditional on the maintenance of the intent, context, and integrity of the material as it is presented here.

DataFlex is a registered trademark of Data Access Corporation.

NO LIABILITY FOR CONSEQUENTIAL DAMAGES
To the maximum extent permitted by applicable law, in no event shall Data Access Corporation be liable for any special, incidental, indirect, or consequential damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or any other pecuniary loss) arising out of the use of or inability to use any information provided in this document, even if Data Access Corporation has been advised of the possibility of such damages. Because some states and jurisdictions do not allow the exclusion or limitation of liability for consequential or incidental damages, the above limitation may not apply to you.