Data Access Worldwide Knowledge Base
Article Text
This article combines in one place information and files for all updates to DataFlex 3.2 for Windows/Console Mode since release.
*** Installation Instructions ***
1. Backup your existing DataFlex 3.2 installation. You can do so by simply copying or archiving the folder in which it is installed.
2. Unzip the files in DF32ConModeUpdates.zip with subdirectories over the existing DataFlex 3.2 installation.
This will add or replace the following files:
- \DF32\bin\conmode.dll
- \DF32\bin\dfquery.exe
- \DF32\doc\3.2_Fixed_Bug_List.pdf
- \DF32\doc\3.2_Language_Changes.pdf
- \DF32\doc\3.2_on_WinNT_and_2000.pdf
- \DF32\doc\DataFlex 3.2 Installation and Environment Guide.pdf
- \DF32\doc\Using_DDOs_in_3.2.pdf
- \DF32\doc\DFQ1025Changes.txt
- \DF32\lib\autogen.flx
- \DF32\lib\dfq.flx
- \DF32\lib\dfquery.flx
- \DF32\src\source\autogen.src
*** Update Info ***
Below is information on what individual updates are combined in this zip file and details on those updates.
1. conmode.dll
Updated console mode runtime that addresses the following issues:
- This console mode runtime fixes issues with data files using file numbers larger than 301, where finding and deleting records caused errors to occur under some circumstances.
- Fixed a problem with printing to printers and printer drivers with print buffers greater than 4 KB, which would cause error 32 "Can't open output file".
2. dfquery.exe, dfquery.flx
This adds the dfquery utility from prior DataFlex revisions back to DataFlex 3.2. This utility had been replaced by dfq, which can be used with databases other than the embedded (DataFlex) database. More information regarding this update can be found in Knowledge Base article 1550: http://www.dataaccess.com/kbasepublic/KBPrint.asp?ArticleID=1550
3. 3.2_Fixed_Bug_List.pdf, 3.2_Language_Changes.pdf, 3.2_on_WinNT_and_2000.pdf, "DataFlex 3.2 Installation and Environment Guide.pdf", Using_DDOs_in_3.2.pdf
Documentation for DataFlex 3.2 in PDF format. This includes the installation and environment guide, Using DDO's in 3.2, 3.2 Language Changes, 3.2 on Windows NT/2000, and the fixed bug list.
4. autogen.flx, autogen.src
Solves a problem where the code generated by DFAuto/Autogen prints the year 106 instead of 2006 in the comments and copyright text strings. This issue is also discussed in Knowledge Base article 2281: http://www.dataaccess.com/kbasepublic/KBPrint.asp?ArticleID=2281
5. dfq.flx
Version 1.025 of dfq, which includes numerous updates and bug fixes. Full details of the updates to dfq can be read in DFQ1025Changes.txt in the \doc folder.
This article is recommended reading for the following keywords and/or categories:
3.2 dfq dfquery dfauto conmode.dll console mode error 32 can't open output file 4 k print buffer
Web Links Related to this Article
BT 4181: Runtime generates 'Can't open output file' error when printer driver tries to declare buffer greater than 4K
URL=http://www.dataaccess.com/BugTracker/PrintBug.asp?ArticleID=4181
DAW Knowledge Base article 1550: INFO: Updated version of DFQuery for DataFlex 3.2
URL=http://www.dataaccess.com/kbasepublic/KBPrint.asp?ArticleID=1550
DAW Knowledge Base article 2281: UPDATE: Updated DataFlex 3.2 source code for DFAuto auto generate program that solves date issues
URL=http://www.dataaccess.com/kbasepublic/KBPrint.asp?ArticleID=2281
File DF32ConModeUpdates.zip
URL=http://www.dataaccess.com/KBasePublic/Files/2291.DF32ConModeUpdates.zip
Email this Article
Email this Article to a Colleague
Send Feedback on this Article to Data Access Worldwide
Copyright ©2010 Data Access Corporation. All rights reserved.
| The information provided in the Data Access Technical Knowledge Base is provided "as is" without warranty of any kind. Data Access Corporation disclaims all warranties, either express or implied, including the warranties of merchantability and fitness for a particular purpose. In no event shall Data Access Corporation or its suppliers be liable for any damages whatsoever including direct, indirect, incidental, consequential, loss of business profits or special damages, even if Data Access Corporation or its suppliers have been advised of the possibility of such damages. Some states do not allow the exclusion or limitation of liability for consequential or incidental damages so the foregoing limitation may not apply. |