Visual DataFlex 7 Development System 7 serial key or number

Visual DataFlex 7 Development System 7 serial key or number

Visual DataFlex 7 Development System 7 serial key or number

Visual DataFlex 7 Development System 7 serial key or number



Shared knowledge leads to accumulated knowledge

Welcome to the cWindowsEx framework!

The cWindowsEx framework is a set of the WinAPI Classes and supplement tools. For Visual Dataflex(R) 7 and higher. Most of these classes are the wrappers to the external Windows Common Controls and system DLLs (Like the Kernel, User or GDI).


Includes most of the packages to be compiled into the application. / cBaseWinControl.h

Includes cBaseWinControl class (Based on cWinControl superclass) definition and expanded with some additional standard Windows Common controls features like hot tracking, tool tips, bitmaps etc. Most of the cWindowsEx framework visual classes have been based on this class. / cDateTimePick.h

These packages include the Standard Windows DateTimePick control that allows the user to select date or time using simple built-in calendar and/or Up/down buttons. Appears as a combo- or spin- form. Uses only Windows Common Controls library. The control can display a date or time and allows you to modify it.

Includes cEnumRegistryKey class definition. This support class allows to enumerate any Windows registry branch. Supports both - keys and values enumeration.

This package enables you to enumerate thru files and folders on a windows box. It works with the windows API and creates a object oriented interface to work with the data. There is no userface attached anywhere, so that you can safely use this from both VDF as well as WebApp.

Allows to format output generated by your application into the HTML or RTF formats. / cMonthCal.h

This Windows control allows the user to select date or time using simple builtin Windows calendar.

Allows split windows vertically or horizontally and resize these parts. Written by Vincent Oorsprong.

Part of The Hammer project. Does not use sentinel and allows you to show simple progress on some batch operations. / cSysLink.h

Windows SysLink Common Control class definition. / cWinBaseEx.h

Set of the functions to provide basic features. These functions allow you to get the Windows profiles directory, All users profiles directory, Default user profiles directory and the User's name. / cWinButton.h

Extended button control that allows bitmaps and text on the button face, supports standard cWindowsEx control functionality, font and color schemas.

Includes some additional code to support cWindowsEx visual controls. / cWinError.h

Handler for Windows errors. Introduces new command "WError" that works similar to the standard VDF "Error" command and is completely integrated into the VDF error processing engine.

Defines very powerful MS Windows file system class that allows open, read and write any file of the file system. Additionally, this package includes some extra functionality like Execute file, check if file exists, get some file attributes (Created, Last write etc), can return file title, file path or file size using standard function call. Introduces new variable type "FileSystem" that may be used like any other local variable. Not limited to the standard 10 channels VDF output. Originally written by Allan Kim Eriksen (AkeFS).

Very fancy control. Part of The Hammer project. Contains a class for Folder Tabs just like the Worksheet selector in M$ Excel. Originally written by Bernhard Ponemayr.

Includes number of functions to aid in binary operations like Shift Left, Shift Right, ROL, INOT, XOR and much more. Originally code has been written by Oliver T. Nelson and Sture Anderson.


Utilises Windows API GDI Interface.


Supplemental function to draw gradients in custom user controls.

Defines cWinImageList class and supports 24 bit colors for any VDF control that supports Image Lists (like cToolBar, cTabDialog, cListView, cTreeView and others). / cWinKernEx.h

Includes a set of supplemental methods and external functions definitions for the Windows Kernel Interface.

Allows you to get complete information about a user's keyboard.

Defines cWinLink class that appears just like any other hyperlink in the application. May accept any action and does have a very fancy behaviour. May have any target as per standard hyperlink - http, nntp, mailto and any others. / cWinListView.h

A DataFlex class to support the Windows' ListView class. This class supports nearly all of the features available in the windows cListCtrl class. Most of the missing features are not available because they cannot be properly supported from within VDF. The original author is Oliver T. Nelson. / cWinNetWk.h

Supplement function definitions that allow you to get extended information about Windows network drives and determine if the drive specified is a network drive. / cWinNls.h

Supplement packages for the Windows locale support.


Supplement package for the interface to the Windows OLE components. / cWinPathEx.h

Supplemental package that defines a number of functions to examine the Windows path specified. With this you can get the following information like, does the specified path exists, is it a directory, is it a file path, is it a network path, server path or url along with any other useful information about paths.

Defines cWinPlatform class. Allows you to retrieve sophisticated information about Operation System used on User's PC. Can obtain full operation system name, revision entries, service pack details and much more.

Defines interface to WinAPI function EnumProcessModules. Originally written by Ulbe Stellema and Vincent Oorsprong. / cWinShellEx.h

Defines Windows Shell Interface. / cWinSpoolEx.h

Defines cWinPrinters class and allows to enumerate all installed printers on the user's PC. Original code written by Vincent Oorsprong.

Supplement package with cWinStack class. Allows push and pop any value into and from the stack object.

TextBox cWinTextBox class based on Windows Common controls that supports any standard functionality of the cWindowsEx framework controls (like tooltips, hot tracking and gradients). / cWinToolTip.h

Defines mixin class cWinToolTip_mx which can be mixed into any standard cWindowsEx controls class library for tooltip support.


Supplement package to support mouse tracking events like MouseMove and MouseLeave for the standard cWindowsEx framework controls.


Supplies Windows API User interface. / cWinVerEx.h

This package defines cWinVer class to retrieve current version information from executable MS Windows files.

Defines cWinVolumeInfo class. Allows to retrieve a lot of useful information about Windows volume specified. It includes Volume label, file system type, type (removable, fixed, remote etc), serial number, total number of bytes, number of free bytes and a lot of other information.

Supplement package that simplifies work with bitmaps and icons. Part of The Hammer project. Originally written by Michael Kurz.

Supplement package that simplifies work with pointers in VDF. Part of The Hammer project. Originally wrote by Michael Kurz.

Standard VDF Controls

Standard VDF controls with ToolTip Support:

CTab Control

New control that looks similar to standard TabDialog, but allows any Tabs to be used for the page switching ( Under Development ).

cWindowsEx Framework Supplement files

Along with these packages, the cWindowsEx framework includes supplement files for the integration of visual controls into the Visual Dataflex IDE and Studio and a sample application that includes sophisticated examples on using cWindowsEx packages, classes and methods.

cWindowsEx Framework Support

We do not provide any support for these components. It is free to use, public and open source! Feel free to contact us for any change, additions and/or improvements that you have made and want us to include in the framework. Bug reports are also welcome. But we can't promise that any request will be served fast and fix implemented.
But we will put all our efforts for solving the problem if time permits.

All of the components included in the cWindowsEx framework are supplied 'AS IS' without warranty of any kind. Use it on your own risk. Some of the techniques used in the code are not recommended by Data Access in any form. Not all of the components may work flawlessly in any environment depending on the Visual Dataflex or Operation System revision used. We simply have not had to the time to test everything on all of the possible combinations.

You may use these packages as you feel fit, but you must notify the Project coordinator (see Credits page) on any change you have made into the packages. Also, statements of the LGPL license apply to these components for Visual Dataflex. Also, note that you MUST have a legal version of Visual Dataflex or the WebApp product series.

Note: Page updated on regular basis.

Copyright © - VDF-GUIdance on all material published, for details see our Disclaimer.

Источник: []
, Visual DataFlex 7 Development System 7 serial key or number


DataFlex is an object-orientedhigh-level programming language and a fourth generation visual tool 4GL for developing Windows, web and mobile software applications on one framework-based platform. It was introduced and developed by Data Access Corporation beginning in [5][2][6][7]

History and overview[edit]

DataFlex can be traced back to when the company called Data Access Corporation[8] (founded in ) created and developed a language allowing application code to run on almost any system architecture, regardless of hardware.[2][9] It started as a relatively early example of a fully fledged and commercially used fourth-generation programming language (4GL). In its early forms, DataFlex was available for CP/M, MS-DOS, TurboDOS, Novell NetWare,[10]OS/2, Unix, VAX/VMS and IBM AIXoperating systems.[11] By , DataFlex was applied in a variety of high-tech industries including automated inventory control systems and insurance fraud detection systems.[5]

DataFlex has lasted many years as a niche application development environment. The DataFlex product supports many database environments: Oracle database, Microsoft SQL Server, IBM DB2, MySQL, PostgreSQL and any ODBC database. DataFlex applications are used by around 3 million users. In , the version with a modernized interface was released.[12] In , Data Access released / version.[13] As of April , the version is

DataFlex is developed and provided by Data Access Worldwide, a software company with main offices in Miami, Florida, Hengelo, Netherlands, and São Paulo, Brazil.[1][14]


The DataFlex language supports:

  • Supports many database environments: Oracle database, Microsoft SQL Server, IBM DB2, MySQL, PostgreSQL as well as any ODBC database.
  • Easily switch between database backends, no code change needed.
  • Variables are loosely typed. The virtual machine takes care of conversions.
  • Flexibility; you can define your own commands.
  • Code compiles to an intermediate byte-code which makes the programs easily portable between operating systems.
  • No threads or multitasking
  • Methods can - for ease of coding - be defined or redefined inside the object definition. Technically the compiler simply sub-classes the superclass and adds the methods to the class.
  • Automatic delegation of messages in the object-oriented programming environment
  • Embedded Database access is ISAM-based. It can be used royalty-free.

Language Extension[edit]

  • Functions defined in Dynamic Link Libraries can be used.
  • Classes, methods and properties defined in a COM module can be used. COM automation, controls and embedding is supported.

Development environments[edit]

The DataFlex programming language is used in the following development environments:

DataFlex Studio
This is the flagship visual development environment from Data Access Worldwide. The current version is (). DataFlex is available for Microsoft Windows only. DataFlex is a GUI development language in a style comparable with Visual Basic, Delphi and C++. From version 4 () up until version (), the product was labeled Visual DataFlex.
DataFlex WebApp Server
Available for Microsoft IIS only, the DataFlex WebApp Server can be used to develop thin client applications such as browser-based applications (both full class browsers such as Google Chrome, Internet Explorer, Mozilla Firefox and Opera, as well as WAP browsers). Developers can also create Web Service client and server applications. The server has built-in load balancing capabilities which also assist with High Availability, this does, however, require an SPLF license.
Web Framework
DataFlex includes a web framework for writing web and mobile applications.
Character mode DataFlex
The latest iteration of the original character mode application () is available as a Console Mode application for MS-DOS, Microsoft Windows and Unix variants (notably Linux).

External links[edit]


  1. ^ abc"DataFlex / Release". Retrieved 6 February
  2. ^ abc"Definition of: DataFlex". PC Magazine. Retrieved February 6,
  3. ^"Installing DataFlex". Johan Broddfeld comments on code. Retrieved 6 February
  4. ^“DataFlex License Info”
  5. ^ ab“DataFlex: An Introduction by Curtis Krauskopf”
  6. ^"DataFlex for Creators". InfoWorld. 4 (26).
  7. ^“InfoWorld (June 1, )”
  8. ^"DataFlex: Programming Gymnastics". PC. 3 (17).
  9. ^"InfoNews/Software, CP/M, DataFlex". InfoWorld. Vol.&#;4 no.&#;9. IDG. March 8, p.&#; ISSN&#;
  10. ^Aarons, Richard N. (September 4, ). "DataFlex: Programming Gymnastics". PC Magazine. Vol.&#;3 no.&#; Ziff Davis. pp.&#;– ISSN&#; Retrieved March 8,
  11. ^Duncan, Judy; Petreley, Nicholas; Chiu, Peter; Mathews, Carla (November 18, ). "Product comparison, Database building blocks". InfoWorld. Vol.&#;13 no.&#; IDG. p.&#; ISSN&#;
  12. ^“InfoWorld (August 12,)”
  13. ^“Benzinga:"DataFlex / Released by Data Access Worldwide”
  14. ^“DataFlex - Overview”
Источник: []
Visual DataFlex 7 Development System 7 serial key or number

DataFlex Installation and Environment Guide



Installation and Environment Guide

Newsgroup: news:// Technical support: (voice) (FAX) Internet: World Wide Web at URL Last Update: March 26, Part Number: IG

Installation and Environment Guide


Copyright DATA ACCESS CORPORATION. All rights reserved. No part of this publication may be copied or distributed, transmitted, transcribed, stored in a retrieval system, or translated into any human or computer language, in any form or by any means, electronic, mechanical, magnetic, manual, or otherwise, or disclosed to third parties without the express written permission of Data Access Corporation, Miami, Florida, USA. DISCLAIMER Data Access Corporation makes no representation or warranties, express or implied, with respect to this publication, or any Data Access Corporation product, including but not limited to warranties of merchantability or fitness for any particular purpose. Data Access Corporation reserves to itself the right to make changes, enhancements, revisions and alterations of any kind to this publication or the product(s) it covers without obligation to notify any person, institution or organization of such changes, enhancements, revisions and alterations. TRADEMARKS DataFlex is a registered trademark and Flex-Keys is a trademark of Data Access Corporation. All other brand and product names are trademarks or registered trademarks of their respective companies. All other company, brand, and product names are registered trademarks or trademarks of their respective holders.

DataFlex for DOS/UNIX/Win32

CONTENTS 3 PLATFORMS SUPPORTED 5 UNIX 5 SCO Unix 5 IBM AIX 5 Linux 5 Sun Solaris 2 5 UnixWare 6 Hewlett-Packard HP-UX 6 DOS 6 Minimum System Requirements 6 Recommended System Configuration 7 WIN32 7 INSTALLING DATAFLEX 7 CD DELIVERY MEDIUM 7 IMPORTANT NOTES FOR CURRENT DATAFLEX USERS 8 BEFORE YOU BEGIN 10 DOS/WIN32 INSTALLATION 10 Registering DataFlex 12 Configuring DataFlex 13 User Counting System 15 Use of the SHARE Command for Windows, Single-User DOS, Peer-toPeer Networks, and Other Networks 17 Windows NT Networks 19 Sharing DataFlex Files on NT Servers 21 Microsoft Redirectors for a Novell Network 23 NetWare Transaction Tracking System 24 UNIX INSTALLATION 25 Installing from CD-ROM 25 Installation, Registration, and Setup 26 Modifying Terminal Information 28 INCREASING THE NUMBER OF USERS 28 THE SAMPLE APPLICATIONS 29
Installation and Environment Guide 3


DataFlex for DOS/UNIX/Win32

Platforms Supported
The CD-ROM may contain one ore more installation programs for the platforms listed. The Software License will indicate the appropriate platform and license (Full Development or Runtime Only) to install. If the license you purchased is runtime only, you may upgrade this software to a full development package merely by purchasing a full development upgrade license either from your runtime supplier or Data Access Corporation. Neither package can be used direct from the distribution media; they must be installed. SCO Unix This version is ported and tested using SCO v, and tested on SCO v It is intended for use on systems running SCO v4 and higher. If you are using UnixWare or higher, we recommend the using the UnixWare port instead of the SCO port. IBM AIX This version is ported and tested on IBM AIX It is intended for use systems running IBM AIX and higher. Linux This version is ported and tested on Red Hat kernel It was also tested on Caldera kernel It is intended for use on systems running any Linux system with a kernel of or higher. Sun Solaris 2 This version is ported and tested using SunOS Generic. It is intended for use on systems running Solaris or higher.

Installation and Environment Guide

UnixWare This version is ported and tested on (SCO) UnixWare using CCS It is intended for use on systems running UnixWare and higher. Hewlett-Packard HP-UX This version is ported and tested on HP-UX It is intended for use systems running HP-UX and higher.

To run the DOS runtime (DFRUN) or any of DataFlexs other executables (utilities), DOS Version with EMM (included with your DOS) or QEMM Version , or higher are required. SHARE may have to be loaded. The recommended settings are SHARE /F /L Note: this revision of DataFlex is not supported for use under OS/2. Minimum System Requirements This revision of DataFlex cannot be expected to perform well the following minimum requirements: A class PC or better. Kilobytes of base RAM. A hard disk drive, with at least 30 Megabytes of available disk space. The DataFlex documentation will consume approximately 20 Megabytes of additional disk space. 3 Megabytes of free EMS or XMS. Note that you cannot add EMS and XMS memory together to yield the required amount. For larger applications, this memory requirement may be greater.

DataFlex for DOS/UNIX/Win32

Recommended System Configuration For optimum performance, we recommend the following system configuration: A Pentium PC or better. Kilobytes of base RAM. A hard disk drive, with at least 30 Megabytes of available disk space. The DataFlex documentation will consume approximately 20 Megabytes of additional disk space. 5 Megabytes of Windows memory above any required by the operating system for other processes running.

To run the Windows console-mode runtime (DFRUNCON), Windows 95/98/ME, Windows NT or Windows are required. The Windows registry must also be changed as described in Windows NT Networks starting on Page To use the Novell TTS capabilities you must have the Novell client software installed.

Installing DataFlex
This information will assist you in the installation of DataFlex and its electronic documentation.

CD Delivery Medium
The software for all the supported platforms is present on the media. If you install DataFlex for a platform other than that for which you are licensed, it will install, but every attempt to run it will trigger a DataFlex not Installed error, and it will not run.

Installation and Environment Guide

CD Directory Structure
Directory ACROBAT DACDOC DACDOC\DF32 Contains, in Acrobat format, the complete documentation set for DataFlex. Note that the PDF files are not compressed. Contents Contains the Acrobat Readers

PRODUCTS PRODUCTS\DF32 PRODUCTS\DF32\DOS-CM Contains all the files to install DataFlex for DOS Protected Mode and Console Mode. Contains all the files to install DataFlex for Sun Solaris Contains all the files to install DataFlex for Linux Contains all the files to install DataFlex for Hewlett-Packard HP-UX Contains all the files to install DataFlex for IBM AIX Contains all the files to install DataFlex for SCO UNIX System V. Contains all the files to install DataFlex for SCO UnixWare (SCO ).




Important Notes for Current DataFlex Users

Here are some points to note about running existing DataFlex programs with this runtime: If you plan to install DataFlex as an upgrade to an existing Full Development license, you should install it as a new license in a separate area and become sufficiently familiar with the new features.
DataFlex for DOS/UNIX/Win32

This revision of DataFlex can run only programs compiled with the current compiler and (fmac). If you wish to run any program that relied on a modified fmac, you must replicate those modifications in the current fmac and repack it to a new before recompiling. Do not install or use the DataFlex Application Framework with this revision. Improved Framework capabilities are integrated in this revision of DataFlex. Where you must retain the Flex-Key mappings of Rev. for an application, you may add a read_dfini statement to the beginning of the program(s) naming \DF32\USR\DFINICFG, a file supplied for this purpose. If you wish to change the mapping in this file, use the Configuration Utility (DFCONFIG) to edit this file. .FLX files compiled in Revision cannot be run by earlier revisions of DataFlex! DataFlex and source code is fully compatible with Revision (when used in non-DD mode) and should compile and operate without problem. If you use the current File Definition Utility to modify (e.g., to add a field or turn header-integrity checking on), a data file created under an earlier revision of DataFlex, the data file will be saved in the new format. As a result, you will thereafter not be able to access the data file with any runtime earlier than Rev. b or programs compiled under such revisions. Where you must retain the ability to use the earlier revision, modify such files only with the utilities of the earlier revision. Files created using extended filelist are only accessible by DataFlex , Visual DataFlex 7 and WebApp Server 3 (or higher). Data files created in the format of the current revision will be accessible by all revisions b or later, unless you use the extended filelist capabilities of DataFlex Files created using extended filelist are only accessible by DataFlex , Visual DataFlex 7 and WebApp Server 3 (or higher).

Installation and Environment Guide

This version of DataFlex no longer supports DataFlex graphics. User counting is maintained in: UNIX Systems: /usr/tmp in a file named, where serial_num is the serial number of the DataFlex runtime.

DOS and Win32 Systems /df32/bin

The file is created whenever DFSETUP is run and the changes are saved. Except for when user rights are insufficient, problems are normally corrected by re-running DFSETUP.

Before You Begin

The installation process is highly automated, and will offer you a number of choices as it proceeds. Prior to installation of the software, confirm that the follow precautionary steps are taken. Make sure a good system backup has just been performed. Check the System Requirements above and verify that you have everything required to run DataFlex. If you are installing a full Development License, decide whether you wish to install the Sample Applications (highly recommended for both first-time users and seasoned developers).

DOS/Win32 Installation
The following steps will install DataFlex on your system. 1. Start up your computer or network server (log in as the system administrator or most-privileged user) as you
10 DataFlex for DOS/UNIX/Win32

normally do. 2. Place the CD-ROM disk in your CD-ROM drive, log on to that drive, and change to the \PRODUCTS\DF32\DOS-CM subdirectory. 3. At the operating-system command line, type INSTALL (and press Enter). 4. You will be asked to verify the target drive letters and directory name. If they are not correct, or if one or more were omitted, you may change them at this point. 5. The installation program will display details about the version of DataFlex you are installing. Read this description carefully so as to avoid installing the wrong version of DataFlex. Follow the succeeding screen prompts carefully. If at any time you need to stop installation, press Ctrl+C. 6. If the installation program displays one or more operating system error messages, you should take note of them, correct their cause, and then rerun the installation program. Examples of errors are: "disk full"; "can't create directory"; "drive not ready"; "write protected"; or "invalid drive". 7. To install the Novell TTS software, you will have to accept the Novell client license that will be displayed. If necessary, check with your applications developer to determine whether such support is used in your application. 8. The DataFlex files are copied onto your hard drive in a logically designed directory structure under the main directory you specified at the beginning of the installation (or under the default, \DF32). You may change the location of the files, but it is suggested you do not, unless you have particular reasons to do so. The installation process includes the writing of a batch file, which you can call to set the environment variables PATH, and DFENV, so that DataFlex can find all the correct files when they are needed. This batch file, named, is located in the USR directory under the main directory where you installed DataFlex. You can either run it manually each time you want
Installation and Environment Guide 11

to run DataFlex, or you can add its commands to your file so that the environment variables are set automatically each time you boot your computer. The DFENV environment variable allows you to specify the full path of an ASCII file containing environment settings. For example, you may create a file named under the \DF32\USR sub-directory. In this file you may include a string value for the DFPATH environment variable, which contains the name of the directories searched on your disk drive(s) when you are opening, creating, deleting, renaming, or copying DataFlex files. To actually use the string value, you must set the new environment variable, DFENV, to the name of the configuration file (i.e., One of the benefits of using this mechanism is that you can specify an extremely long DFPATH value without worrying about operating system limitations. Furthermore, you may include any number of DataFlex environment variables in this configuration file. By default, DataFlex installs a configuration file named in your USR directory. It is important to note that the values defined in this file for DataFlex environment variables will supersede any settings you may have set at the O/S level directly in the same variables. 9. After all of the files are placed onto the hard disk, a message will appear, informing you that the installation process has been completed. The installation program will ask you whether you want to start the setup program DFSETUP. This program is used to install your registration code. The registration instructions displayed will take you through this process step by step. Note: Runtime installations may require extra installation steps, as provided by the application vendor. Registering DataFlex The Setup Utility DFSETUP will start at the end of the installation process if you confirm that you wish it to. This utility is discussed
12 DataFlex for DOS/UNIX/Win32

in more detail in the Setup and Configuration chapter of the DataFlex User's Guide. Its purpose is to register your license and create the user-counting file. Configuring DataFlex Using DFCONFIG The Configuration Utility (DFCONFIG) allows you to optionally set certain attributes such as screen colors and function keys to use, which characters to use to represent money amounts, and how to format dates.

In previous revisions of DataFlex 3, the Setup Utility allowed you to modify the DataFlex screen colors. In , you must use the DFCONFIG utility instead. The Windows Operating System does not support the blinking screen attribute and therefore, is not supported by DataFlex.

Default Function-Key Assignments Your DataFlex package comes with certain function keys already assigned. If you wish to change any of these assignments, then you must run the DataFlex Configuration Utility (DFCONFIG). Refer to the DataFlex User's Guide for more information about DFCONFIG. See the paragraph under "The Installation Program" about Flex-Key functionality of programs compiled under earlier revisions of DataFlex and running under the current revision. The default function key assignments are shown in the following tables, with those defined in Data Access packages followed by an asterisk (*):

Installation and Environment Guide


DataFlex Universal Keyboard

KEY F1 F2 F3 F4 Help Save Record Exit Function Prompt

Shift + KEY

Ctrl + KEY

Alt + KEY User Key 1

Delete Record Trace Mode* Print Screen

User Key 2

Exit Applicatio n Clear All Panels Switch to Prev Panel* Calculate Switch to Next Panel*

F5 F6

Clear Area Switch to Next Area Find Previous Find Next Find Switch to Action Bar Accept Next Item Insert/Overty pe Toggle Delete Character Cursor Left Cursor Right Cursor Up

Refresh Screen Switch to Prev Area Superfind Previous Superfind Next Superfind Add Mode On/Off*

F7 F8 F9 F10 Enter Tab Insert Delete left arrow right arrow up arrow

Trace On/Off*


Clear and Return Previous Item

Skip Word Left Skip Word Right Begin of Panel


DataFlex for DOS/UNIX/Win32

KEY down arrow spacebar Backspac e Home End Page Up Page Down Esc \ + Cursor Down Selection Toggle Destructive Backspace Begin of Line End of Line Scroll Page Up Scroll Page Down Escape (Cancel)

Shift + KEY

Ctrl + KEY End of Panel

Alt + KEY

Erase to End of Line Begin of Data End of Data Scroll Page Left Scroll Page Right

Non-WP backspace

Mark Paste Copy Cut

User Counting System Upon execution of the DFSETUP program, a file will be created to count concurrent users of DataFlex on a LAN. This is usually stored in the directory where DFSETUP was executed and will have a root name equivalent to your serial number and an extension of .DFR. For example, if your serial number is ,, then the .DFR file will be named DFR. (UNIX: DFR) Only one copy of the .DFR file should exist for any one serial number and that file must be accessible, via DFPATH, to all users who use that serial number. (UNIX: The location is \usr\tmp A .DFR file should not be moved or copied. It may only be

Installation and Environment Guide

created with DFSETUP. Attempting to move the file or having more than one .DFR file for the same serial number may cause the file to be rejected. If the .DFR file is damaged in any way, you will receive an appropriate error message when you try to run DataFlex. You may re-create the .DFR file by running the DFSETUP program and selecting Option 3. Each invocation of DFRUN consumes one authorized user, regardless of whether this is on the same computer or another using the runtime. Only the first invocation of DFRUNCON is counted on each machine. When the maximum number of users accessing DataFlex and another user attempts to start it, that user will receive a message explaining the condition and will be unable to start DataFlex successfully. The user will be able to start DataFlex as soon as one or more of the current users exits DataFlex. You may purchase additional user licenses from your dealer or Data Access Corporation.


DataFlex for DOS/UNIX/Win32

Use of the SHARE Command for Windows, Single-User DOS, Peer-to-Peer Networks, and Other Networks When to Load SHARE You only need to load SHARE if you are not using an operating system which has SHARE's functionality built in (like Novell's NetWare) and you are accessing files in a multi-user manner. Accessing files in a multi-user manner could mean actually having multiple users open and accessing the file (i.e. Lantastic), and/or having multiple tasks accessing the same files (i.e. Windows or DesqView), or running DataFlex programs (whether single or multi-user) that open the same file more than once concurrently. How can you determine whether such a condition applies to your system? Check for any of the following conditions: 1. If you use the chain wait command to invoke a second DataFlex program, and that program opens one of the same files in use by the original program, SHARE is needed. Note: If you use the export_files option SHARE is not needed, since both programs will share the same file buffer and handles. 2. If you use file aliases, you need SHARE loaded. This is the process of defining multiple files in with different DataFlex names but using the same physical rootname. 3. If you are using the File Definition Utility open a file, and then execute a maintenance option. This invokes the File Maintenance Utility, a separate program, which could access the same files that File Definition already has opened. SHARE is needed in this case. This is of concern only for users with development licenses, since File Definition is not part of the runtime license. 4. The following test fails. THE FOLLOWING TEST SHOULD NOT BE PERFORMED ON LIVE DATA! This test consists of two machines, named A and B, which are running DataFlex and accessing the same data file(s). Machine "A"
Installation and Environment Guide 17

finds a record and performs a lock on that record. Machine "B" Finds, Edits, and attempts to save the same record. If Machine B can save the record, the test fails (SHARE is required). The test succeeds if Machine "B" waits indefinitely for Machine A to release the lock. If you are using an operating system, which does not have, SHARE support built in (the test described above fails) and you are doing one of the above three items, you need to load SHARE. If SHARE happens already to be active on any computer that is using DataFlex, you must check to make sure it is loaded with at least the command-line parameters shown below. How do you load SHARE? Simply add the line SHARE to your file. This loads SHARE with the default parameters. There are two parameters used when loading SHARE: the L and F parameters. They define the size of two separate tables that SHARE maintains. The first, L, is the size of the SHARE LOCK table. The L parameter defines the number of locks that SHARE can access. The default L parameter is Set the L parameter to a number equal to the number of locks you expect plus a bit of extra space. Note that DataFlex will issue a maximum of one lock per data file. The F parameter specifies how many bytes are allocated to the file handle table. This table stores the complete pathname of the file plus 11 bytes of overhead per file. Thus C:\DATAFLEX\DATA\ would require 36 bytes in the file handle table. The default for the F parameter is , which will allow you to approximately 20 files with large file paths. Increase this number as needed for your application. Keep in mind that SHARE is not a per-process setting, but a permachine setting. Thus, if you want to run 5 different programs at the same time on the same machine, each one opening 30 files, the F parameter in SHARE would need to be large enough for files. Also, the L parameter would need to be able to handle
18 DataFlex for DOS/UNIX/Win32

the potential locks. Here is an example of loading SHARE, increasing the F parameter to and the L parameter to

If SHARE is not loaded and you attempt multi-user access (and you are not using an operating system with SHARE capabilities built in) file corruption can occur. If you install SHARE with insufficient settings for the F or L parameters, a variety of DataFlex errors may result such as: "Can't open datafile", "Too many locks"," Read error on index file", "Seek to unwritten extent", etc. The corruption can occur due to DOS keeping a separate buffer and file handle for the same file in two different applications. When records are added or edited in one file, the other (really the same physical file) does not get updated. With SHARE, all files opened with the same physical name share the same buffers, regardless of which application opened them. Note that the above setting would use bytes: for the
F parameter and for the L parameter (each lock requires 7

bytes of overhead). For more information on SHARE, consult your DOS documentation or contact your DOS manufacturer. Windows NT Networks Windows 95 Workstation Clients Using Microsoft Network redirectors that open files stored on Windows NT machines results in buffering, which causes data corruption. Microsoft has now provided a replacement, Microsoft Network Redirectors for Windows 95 that does disable the buffering of files shared on Windows NT. The redirector executable is a self-installing program provided by Microsoft. Run it under Windows 95 and it installs itself and makes the needed changes to your Windows registry. You then need to restart Windows 95 for the changes to take effect. This new redirector removes the local caching that the old redirector included. The local caching would cause data errors
Installation and Environment Guide 19

when retrieving data from an NT server. The new redirector has been extensively tested by Data Access Corporation and does indeed solve the problems with data reliability between a Windows 95 workstation and an NT server. This redirector is not needed if accessing data on a NetWare server. However, installing the new redirector will have no detrimental effects on sites not using NT servers. Thus, our general recommendation would be to use the new redirector at all customer sites. You may find the VREDIR executable on your disk after the installation process of DataFlex if you installed from CD media. The new OSR2 version of Windows 95 (generally shipped with new machines in the last quarter of and into ) comes pre-installed with the new redirector. This is the same version of Windows 95 with the new FAT32 file system. Note: When you search for on a machine that has not had either the patch or the OSR2 revision installed, the first entry found is simply the component name and its associated data (displayed in hex). On any machine which was shipped with the OSR2 release, or had the patch installed, the first entry that is found displays a comment about Samba UNIX and the revision number beneath the comment (the screen with the hex data will be the second one found). Warning: Even if your machine came with the new (Version ) installed, you will still experience corruption problems if the registry key DiscardCacheOnOpen is not set to true (1 hex). This key is not defined as part of standard Windows 95 installations, but will automatically be defined and set if you use the patch provided to us by Microsoft. (You may download this patch from, or install it from the DataFlex CD from the directory \MISC\REDIR). You may verify (and correct, if necessary) this setting with Regedit by querying this key in HKEY_LOCAL_MACHINE/System/CurrentControlSet/Services/V xD/VREDIR DiscardCacheOnOpen = (1 hex). If you have OSR2, you must enter it yourself. Start the program:
20 DataFlex for DOS/UNIX/Win32 Choose: HKey_Local_Machine -> System -> Current Control Set -> Services -> VxD -> VREDIR -> Right-click or pull down Edit -> New -> Binary Value -> Rename value -> Value name: DiscardCacheOnOpen Data type : BINARY Modify -> Parameter value: 00 01 (type in the zeroes)

Sharing DataFlex Files on NT Servers You will experience data and index file corruption (or at least an apparent lack of synchronization between the data at various workstations) when using DataFlex in configurations, where the shared-files are stored on a Windows NT Server. These problems were verified in-house. It was also reported that Microsoft Access had similar problems and required that opportunistic locking (an NT feature) be disabled at the server, for the Access application to function correctly. This information is covered in the Microsoft Knowledge Base article Q If you examine the Knowledge Base article, references are made
Installation and Environment Guide 21

to NT Workstation settings, as well as the server settings. It is important to note that the updated workstation fix is also required for stable operations, when using Windows 95 workstations. There are actually two different operating system level functions at work. Using combinations of Windows 95 and Windows NT workstations and Windows NT server: local buffering of data at the Windows 95 workstations. Controlled by and its registry settings at the workstation, and opportunistic-locking buffering at the Windows NT workstations (controlled by combinations of settings at the workstation and server) are supported by disabling it at the server level. Verify (and correct, if necessary) these NT Server parameters:

EnableOpLockForceClose REG_DWORD set to 1 (default=0) EnableOpLocks REG_DWORD set to 0 (default =1)

This is done by starting the program with: "Start" | "Run" | "Regedit" OR \WinNT\ Choose: HKEY_Local_Machine -> System -> Current Control Set -> Services -> LanmanServer -> Parameters -> If the Value EnableOpLockForceClose exists -> Double-click on it OR
22 DataFlex for DOS/UNIX/Win32

Select it, then pull down "Edit" and choose DWORD -> In DWORD Editor, Hex selected, enter the value 1 If it does not exist, pull down Edit -> Add value -> Value name: EnableOpLockForceClose Data type: REG_DWORD OK - > In DWORD Editor, Hex selected, enter the value 1 If Value EnableOpLocks exists -> Double-click it OR Select it, then pull down "Edit" and choose DWORD -> In DWORD Editor, Hex selected, enter the value 0 If it does not exist, pull down Edit -> Add value -> Value name: EnableOpLocks Data type: OK -> In DWORD Editor, Hex selected, enter the value 0 Microsoft Redirectors for a Novell Network When running Windows 95 with Microsoft redirectors for a Novell network, programs that open files read only may not have access to updates to that file made by other users while the program
Installation and Environment Guide 23


runs. You can overcome this behavior by having your read-only program perform a write to the file from time to time, which will flush the Windows VCACHE buffer. An alternative that requires no changes to your program code are to edit your Windows file. Search for the [NWREDIR] section, adding it if there is none. Place the line ReadCaching=0. End result: [NWREDIR] ReadCaching=0 NetWare Transaction Tracking System Server-based transaction control permits complete backing-out of an incomplete transaction upon failure of the program or the workstation from which the transaction is being entered. This occurs automatically upon such failure. If this feature is in use, no reindexing should be required after such a failure. In fact, other workstations, even those with incomplete transactions at the time, can continue normal operations through such an event. The DataFlex database driver uses NetWare's Transaction Tracking System to support transaction control at the server. You must use a NetWare shell in order to make use of this feature, and TTS must be enabled in your installation of the shell. The Microsoft drivers for NetWare are not supported; only those from Novell are. Use of this feature entails no special provisions in the source code of the program other than those required for transaction control generally. It is, however, necessary to set the DF_FILE_TRANSACTION attribute of every file involved to DF_FILE_TRANSACTION_SERVER_ATOMIC to use it. This can be done either from your program or with DFADMIN.

Setting a file server-atomic causes the NetWare "transaction flag" to be set on the .DAT, .VLD, and .K## files. When a DataFlex transaction is started, a NetWare TTS transaction start is sent to every NetWare server on which any of these files resides. At the end of the transaction, a TTS transaction end is
24 DataFlex for DOS/UNIX/Win32

sent to the same servers. If a DataFlex transaction exceeds the size limits imposed by your local version of TTS, the network administrator will receive a NetWare error report of it. The DataFlex program itself, however, will function normally, but without TTS protection for such transaction. If you try to delete a TTS flagged file through the operating system, you will receive an error message. You would have to reset the flag with the NetWare FLAG command before deletion. If you perform such manipulations through DataFlex, however, the flag will be reset as necessary to permit the desired operations. If you attempt to set a file to server-atomic that is not on a TTS capable NetWare volume, Error "File not on TTS volume" will be reported. If a DataFlex program opens a file flagged for TTS that is not on a TTS capable volume, the same error will be reported at that time. Similarly, the same error will be reported if the file is set to SERVER_ATOMIC and the NetWare redirector drivers are not installed.

UNIX Installation
Prior to installing DataFlex, be sure that you have your serial number, registration name, and registration code. You must be logged on as the root user prior to installing DataFlex. Installing from CD-ROM 1. Place the CD in the appropriate drive and type: 2. List the sub-directories and identify the directory containing the DataFlex version for your platform (refer to your DataFlex License). Note: Your CD-ROM must be mounted as a file system before you can use it. Please consult the system
Installation and Environment Guide 25

administrator's guide that came with your system for details. Typically, the CD-ROM is mounted as /cdrom or /CDROM. 3. On the target drive create a new temporary directory and then change (cd) to that directory. This step places all the files into the selected temp directory. 4. Type the following command:
tar -xvf filename substitute the filename with the CD-ROM file name (as described in step 2). Below is a typical example command line for AIX. tar -xvf /CDROM/products/df32/aix/

In some systems, the file names may appear with a semicolon (;) and a number appended to it. In this case, enclose the filename in quotes, as displayed in the example below. Tar -xvf "/CDROM/products/df32/aix/;1" Installation, Registration, and Setup Use the Bourne or Korn shell, not the 'C' shell. The Install procedure aborts if it detects insufficient disk space unless you use the -c option. If the drive onto which you are installing has more than 2 Gigabytes of space, use this option to keep the procedure from aborting erroneously. Using this option, however, does not guarantee that an interrupted installation can be completed without starting over. You can specify both options (the order of the commands is irrelevant.)
./Install [- [d] [c] ]

Where devicename is that supplied by the manufacturer of the drive or your operating system for the drive you are using. The installation program will ask you to enter the directory where the DataFlex system should be installed, offering the default of /usr/local/df If the directory used contains an existing DataFlex 3.x installation, the installation of DataFlex is completed without
26 DataFlex for DOS/UNIX/Win32

overwriting the existing menu.*, query.*, flexerrs.*, and *.cfg files. If the directory contains a previous revision of DataFlex, a warning against overwriting a previous revision is displayed. If this warning is overridden, a directory named backup is created under df31d/usr and the existing menu.*, query.*, flexerrs.*, and *.cfg files are copied into it before they are overwritten in their original location along with all the other existing DataFlex system files. The installation shell script should adequately guide you through the rest of the installation. New installation only: Once the installation process has finished, the installation program will automatically execute the Setup Utility (dfsetup). Proceed to register your DataFlex license. Do not exit DFSetup without fully registering your license. Change the current directory to /df32/usr. Execute the setpath script by typing
. ./setpath


The space after the first dot is required.

This script sets the value of the DFPATH environment variable. DFPATH (and the other DataFlex environment variables) can alternatively be set by means of a text file, described in the documentation, named This alternative was created to deal with limitations to which UNIX is not subject. If you do choose to use, you must set an environment variable called DFENV to the directory path in which the file resides (df32/usr by default from the install procedure). For example, your could contain: DFPATH= .:/usr/local/df32/bin:/usr/local/df32/usr The example below assumes that the files are located in the default directory, substitute the default directory with the installed directory name.
DFENV= /usr/local/df32/usr Installation and Environment Guide 27

export DFENV

At this point, DataFlex can be run, but modification of its terminal information (described in Modifying Terminal Information) may be required for full keyboard functionality on your terminals. Modifying Terminal Information If you are not modifying the terminfo entry, refer to Section of the DataFlex UNIX System Administrator's Guide for specific information on your terminal. If you want to modify an existing terminal entry or create a new one, see Section You can change the directory in which DataFlex searches for your terminal entries by changing the DataFlex DFTERMINFO environment variable (cipsas.comINFO=/usr/lib/terminal would force DataFlex to search that directory for the appropriate terminal entry).

Increasing the Number of Users

To purchase an increase for the number of users supported by your DataFlex license, contact Data Access Corporation or your local DataFlex distributor elsewhere. They will supply you with a new registration code, which you should install with the DFSetup Utility. It will replace the registration code you used initially and accommodate the larger number of users. All active users must be off the system when Setup is launched; you must be logged in at the root in UNIX or at the highest level of system administration in other environments. From the usr sub-directory, run the SETPATH procedure, and then DFSETUP. No other installation or new software is required for this change. Increasing the user capacity of DataFlex in this manner may not affect applications that limit user capacity independently of DataFlexs limit. If your application does this, you must secure any needed expansions from the supplier of your application.


DataFlex for DOS/UNIX/Win32

The Sample Applications

Once you have successfully installed a DataFlex development license, we strongly suggest that you run and examine the Sample Applications supplied with your license. They are located in the Directories \DF32\USR\EXAMPLES and \DF32\USR\EXAMDD.

Release Notes
Be sure to read the various readme files for the newer revisions of DataFlex. They contain important information on program, feature, and command changes and additions. They are supplied on disk and may be read in the same manner as the rest of the on-line documentation.

Installing and Using the Electronic Documentation

All DataFlex documentation is supplied in Adobe Acrobat format.

Adobe Acrobat Reader

The Adobe Acrobat Reader uses a minimum of 10 Mb of disk space. Instructions on its use are installed automatically with the Reader. The version supplied on the distribution media is Note: You may also want to log on to the Adobe Web site for updates, languages, and additional plug-ins ( If any problems should arise with Acrobat Reader, please refer to Adobe's Technical Support Department or their World Wide Web site for troubleshooting. Adobe provides Acrobat Readers for many platforms. The Adobe Acrobat Exchange package (not included) enables you to create, annotate and modify PDF files. If you decide to distribute your own PDF files, you can also create full text indexes for collections of PDF files, such as the cross-index for the DataFlex documentation. For more information about Adobe Acrobat, you may contact Adobe Systems at
Installation and Environment Guide 29

Installing the Adobe Acrobat Reader

The various Acrobat Reader installation programs are located in the \Acrobat folder on the distribution CD ROM. The Acrobat Reader installation program for your platform can be selected from the following: AIX Solaris Bit Windows Bit Windows Linux Hewlett Packard rs16eexe

Installing the Documentation

The documentation requires 22 Mb of disk space. After installing the Acrobat Reader as discussed above, you can access the documentation directly from the DACDOC\DF32 directory of the CD. You may choose to copy the documentation to your hard disk, since random access is likely to be faster than when accessing it directly from the CD. If you do so, copy the entire DACDOC\DF32 directory and all directories below it.

Using the Documentation

As previously mentioned, the \DACDOC\DF32 directory on the CD-ROM constitutes the electronic version of the entire DataFlex documentation. In order to view the documentation, you must open the files with the Acrobat Reader. Using the documentation with the Acrobat Reader is as simple as opening a document in your favorite word processing software. In fact, every time you run the Acrobat Reader software, a dialog appears prompting you for the name of the PDF file to open. You
30 DataFlex for DOS/UNIX/Win32

may choose to open the file here, or select File from the Main Menu; both methods are valid. The documentation files are: DFPDF This document contains the DataFlex Installation and Environment Guide. _Language_Changes This document contains information on the changes in the DataFlex language when using the new Data Dictionary capabilities of DataFlex Using_DDOs_in_PDF This document contains instructions on how to invoke the use of the new Data Dictionary capabilities of DataFlex This document contains the complete reference information on Data Dictionaries and their use. _on_WinNT_and_PDF This document contains important information about the requirements and limitations of using the DOS components of DataFlex on Windows NT and This document contains the list of bugs that were fixed in DataFlex Updating_to_pdf This document contains important information on upgrading applications to DataFlex from DataFlex Updating_to_pdf This document contains important information on upgrading applications to DataFlex from DataFlex

Installation and Environment Guide


Updating_to_pdf This document contains important information on upgrading applications to DataFlex from DataFlex This document contains the Developing Applications with DataFlex manual. This document contains the DataFlex 3 User's Guide. This document contains the DataFlex 3 UIMS Reference. This document contains the DataFlex 3 UIMS Handbook. This document contains the DataFlex 3 Encyclopedia. This document contains important release notes from DataFlex This document contains important release notes from DataFlex c. This document contains important release notes from DataFlex d.


DataFlex for DOS/UNIX/Win32

Getting Starting with DataFlex (UNIX)

To execute DataFlex, refer to the following steps. 1. Login, as you usually do. 2. Run the SETPATH script file. 3. Verify that the TERM and DFTERM settings are correct. 4. Type: dfrun Note: Runtime installations refer to your application vendor's documentation.

Getting Starting with DataFlex (DOS & Win32)

To execute DataFlex, follow these steps: 1. If you have modified the or files, shut down and reboot your computer so the new settings take effect. 2. If you have not modified, you must run SETPATH to set up PATH and DFENV. To do this, from the \DF32 directory, type .\USR\SETPATH at the command line. 3. You may start the DOS DataFlex runtime by entering FLEX or DFRUN. To start the console mode runtime, enter DFRUNCON. 4. At this point, the DataFlex Menu should appear. You may now test to see that DataFlex is working properly. Once in the DataFlex menu system, press Alt+F4 to return to the operating system.

Installation and Environment Guide


Bug Reporting Guidelines

1. Remember that a tester will attempt to reproduce your problem with the information you supply. 2. Clearly state the revision numbers of products that you are experiencing a bug with. 3. For each bug, state whether the effects can be seen - and reproduced - every time or sporadically. 4. Clearly document the steps to reproduce the problem. As stated, someone will try to reproduce the problem, using only the information you provide. 5. It is better to give too much information than too little. However, do avoid mentioning information that you know to be irrelevant. 6. Avoid reporting several issues in the same report. This is much harder to track properly. 7. Try to reduce the example you give into the smallest sample that demonstrates the problem. For example, do not send a program with two hundred objects when the same program reduced to one object, shows the same problem. The less work we have to do to reproduce the problem, the faster we can address it. 8. Try to be precise with your terminology and not use generic terms. 9. For each issue, state your expectations (what you thought should happen) and what actually happened. Be clear on what you are stating; avoid making statements that are questions. For instance, do not say: "type a letter and see what happens when you press the F5 key. Instead, tell us what happened and what you were expecting (see previous item). Clearly distinguish bugs (where the behavior differs from the documentation) from suggestions. If an issue differs from the documentation, state exactly where it is documented and what is different. If you have a suggestion for a better implementation of a feature,
34 DataFlex for DOS/UNIX/Win32

state what was wrong with the original feature and why your suggestion is better. This first point is very important. You may discover a valid failing in a feature, which needs attention, but your suggested correction may be inappropriate for technical reasons. You can report bugs and suggestions from the Support section of our Web site:

Installation and Environment Guide


Obtaining Technical Support

Who is eligible for Technical Support?
Data Access Corporation offers its customers 30 days of free technical support following the purchase and registration of a new Data Access Corporation product license. If you are installing a development license in the US, technical support for installing DataFlex is available via telephone, FAX, and the Internet at the numbers and names listed on the cover of this document. If you are installing a runtime license, please consult your application vendor for assistance. If you are outside the US, please refer to your local DataFlex distributor.

What areas does Technical Support cover?

Data Access Corporation supports our products in the following ways: We will clarify any issue discussed in our documentation. We will clarify any example code distributed with the product. We will assist in the tracking down/reporting of a product bug. We will provide current information regarding supported platforms and other revision information.

Getting Technical Support

For U.S. customers, dial for Technical Support. If you no longer qualify for free support, you will need to purchase a subscription to SupportNet (which provides a number of support incidents and a quarterly CD mailing). Additional incidents can be purchased at a reduced rate for SupportNet members. To view all the details of our product support and all information about SupportNet, visit our Support Home page at:
36 DataFlex for DOS/UNIX/Win32

International customers should contact their local distributor or Data Access subsidiary for support (our web site:, lists contact information for worldwide distributors and subsidiaries). Our hours of operation are AM - PM EST MondayFriday. Have your product information, serial number, and SupportNet contract number available. Give a complete concise account of the trouble you are experiencing and try to be at the machine with the problem so that our support representatives can work with you to resolve the problem.

Where to find us on-line


Where to write to us Data Access Corporation SW Avenue Miami, FL

Where to FAX us

Installation and Environment Guide


Источник: []

What’s New in the Visual DataFlex 7 Development System 7 serial key or number?

Screen Shot

System Requirements for Visual DataFlex 7 Development System 7 serial key or number

Add a Comment

Your email address will not be published. Required fields are marked *