Upgrading to DataFlex 3.2: Difference between revisions
m
Added note about the DataFlex debugger
Hsymington (talk | contribs) m (→Implementation of Y2K-Enhanced Features: removed ref to DAC) |
Hsymington (talk | contribs) m (Added note about the DataFlex debugger) |
||
(2 intermediate revisions by the same user not shown) | |||
Line 4: | Line 4: | ||
The content of this page is based on a whitepaper originally written in May 1998 by Dennis Piccioni from Data Access Worldwide. Updates were made to the content up until 2002, but nothing after that, so some references will be dated. | The content of this page is based on a whitepaper originally written in May 1998 by Dennis Piccioni from Data Access Worldwide. Updates were made to the content up until 2002, but nothing after that, so some references will be dated. | ||
'''Note:''' One very good reason to upgrade is that if you are using DataFlex 3.2, you can use the '''[https://docs.google.com/document/d/1a7DOX7bULiEqAkNXmKA-T91n0RfLFzh8V-CjXwMW0x0/edit#heading=h.mxjauxfaio71 DataFlex Debugger]''' to run your programs in debug mode with features such as single stepping, variable inspection, call stack and record buffer inspection. Read the help and get the DataFlex Debugger download, from the [https://www.dataaccess.eu/resources/downloads/download-category/download-subcategory-842?dagapsg=64 DataFlex Debugger download page]. | |||
== Why Upgrade? == | == Why Upgrade? == | ||
Line 624: | Line 627: | ||
DataFlex 2.3 was designed in simpler days of computing. Hard disks were smaller, less memory was available and applications were generally smaller and did fewer things. Developers usually had relatively few development tools (and revisions thereof) installed on their PCs. Those times have changed. Today, it seems one can never have enough hard disk space or RAM and most applications do a gazillion things, whether they are needed or not. | DataFlex 2.3 was designed in simpler days of computing. Hard disks were smaller, less memory was available and applications were generally smaller and did fewer things. Developers usually had relatively few development tools (and revisions thereof) installed on their PCs. Those times have changed. Today, it seems one can never have enough hard disk space or RAM and most applications do a gazillion things, whether they are needed or not. | ||
For programmers things have changed as well. It is common for application designers to develop with many different tools, even for a single application | For programmers things have changed as well. It is common for application designers to develop with many different tools, even for a single application. | ||
In DataFlex 2.3b, many developers kept the runtime files in the same directory as the application files (i.e. data and .flx files). In order to successfully upgrade to DataFlex 3.2, or to run the two (or more) versions of DataFlex simultaneously, these files need to be separated. Runtime files from the two versions will interfere with each other. | In DataFlex 2.3b, many developers kept the runtime files in the same directory as the application files (i.e. data and .flx files). In order to successfully upgrade to DataFlex 3.2, or to run the two (or more) versions of DataFlex simultaneously, these files need to be separated. Runtime files from the two versions will interfere with each other. | ||
Line 712: | Line 715: | ||
#Make sure c:\df23 is in your PATH environment variable | #Make sure c:\df23 is in your PATH environment variable | ||
#Run DataFlex (dfrun ProgramName, dfcomp, dfquery, etc.) | #Run DataFlex (dfrun ProgramName, dfcomp, dfquery, etc.) | ||
== Appendix A: Directory Listing of a DataFlex 2.3b Development License == | == Appendix A: Directory Listing of a DataFlex 2.3b Development License == |