Upgrading to DataFlex 3.2: Difference between revisions

1. Create separate directories for the runtime files and application files, and separate data and source code in the process.

For the remainder of this paper we will assume that the directory where your 2.3b license resides is c:\df23 – you can substitute your actual installed directory name and drive letter for c:\df23.

c:\df23 - original 2.3b directory

              - 2.3 runtime files will remain here

              - a copy of the source code files will remain here to be used with 2.3

c:\app - directory for your application files

                \data - data files to be shared between revisions 2.3 and 3.2 (subdirectory of \app)

                \src - source code files to be used with 3.2 (subdirectory of \app)

Separating your existing 2.3b directory this way will give you numerous operating options:

Concurrently run DataFlex 2.3b and 3.2 (or just 3.2)

Have an existing directory structure to easily upgrade to Visual DataFlex

A. Files to be moved into c:\app\data directory:

:all data files for your application (*.dat, *.k*, *.tag, *.fd, *.def)

filelist.cfg

B. Files to be copied into c:\app\src directory:

One copy of the source code can remain in \df23 for use with (and to keep up) currently running 2.3b applications, and one copy will go into this directory for use with the new 3.2 version.

:all source code files (*.frm, *.src, *.inc, *.rpt, …)

C. Files to remain in c:\df23 (runtime) directory:

the most important are the executable files (*.exe) and termlist.cfg

see Appendix A for a complete list of files that are installed by a DataFlex 2.3b Development License – these are the files that should remain in the c:\df23 directory

2. Install 3.2 into a separate directory and install your DataFlex 3.2 registration code

For the remainder of this paper we will assume that the directory where your 3.2 license resides is c:\df32 – you can substitute your actual installed directory name and drive letter for c:\df32.

Note:

DOS/Windows: Remember to execute the c:\df32\usr\setpath.bat batch file before running DFSetup.exe to install your registration code.

Linux/Unix: Remember to execute the /usr/local/df32/usr/setpath script before running dfsetup to install your registration code.

3. Concurrently Running DataFlex 2.3b and 3.2

A. Running DataFlex 3.2

1. Edit the c:\df32\usr\dfenv.cfg file:

Change the DFPATH= statement to include the c:\app\data directory

Before:

dfpath=.;c:\df32\usr;c:\df32\usr\help;c:\df32\lib;c:\df32\bin;c:\df32\src\pkg;c:\df32\usr\examples\expense;c:\df32\usr\examples\dar;c:\df32\usr\examples\ordentry;c:\df32\usr\examples\big;c:\df32\usr\examples\report;c:\df32\usr\examples\data;

dfpath=.;c:\app\data;c:\df32\usr;c:\df32\usr\help;c:\df32\lib;c:\df32\bin;c:\df32\src\pkg;c:\df32\usr\examples\expense;c:\df32\usr\examples\dar;c:\df32\usr\examples\ordentry;c:\df32\usr\examples\big;c:\df32\usr\examples\report;c:\df32\usr\examples\data;

Note: the DFPath statements above may appear different depending on the software you use to view or print this document, but each DFPath statement is a single continuous statement.

2. Switch to c:\app\src directory

3. Execute c:\df32\usr\setpath.bat

4. Run DataFlex (dfrun programname, dfcomp, dfquery, etc.)

Note: You may want to use different dfenv.cfg files for different applications so that you can place numerous application specific environment variables into each file.

B. Running DataFlex 2.3b

*Switch to c:\df23 directory

*Set the DFPATH environment variable:

*set DFPATH=.;c:\app\data

*Make sure c:\df23 is in your PATH environment variable

*Run DataFlex (dfrun ProgramName, dfcomp, dfquery, etc.)