README.1ST July 1996 Welcome to the CA-Visual Objects 1.0C-2 service pack. Read this information carefully before updating your CA-Visual Objects 1.0C, or 1.0C-1 version installation to CA-Visual Objects 1.0C-2 version. This patch fixes 22 priority issues that have been identified after releasing 1.0C. Applying the patch ================== In order to apply the patch you need to have the CA-Visual Objects 1.0C or 1.0C-1 version installed. This can be the Full, Lite or International versions, but NOT a language specific version (ex. German). Make sure CA-Visual Objects is not running before you apply the patch. PATCH.EXE : Patch Utility. P10C-C2.RTP : Patch file to upgrade from 1.0C or 1.0C-1 to 1.0C-2. README.1ST : This file currently being viewed. These files are used to upgrade your current release of CA-Visual Objects 1.0C or 1.0C-1 to 1.0C-2. The patch requires PATCH.EXE which is on this disk. To apply the patch to your existing version of CA-Visual Objects 1.0C or 1.0C-1: 1. Set your default directory to the CA-Visual Objects 1.0C or 1.0C-1 root directory. For Example: C:\CAVO 2. Copy the files PATCH.EXE and P10C-C2.RTP into the above directory. You can find out what Build you have by checking the date stamp of the files listed in the "Changed files and fixes for 1.0C-1" section. If the files have a date stamp of 1-9-96, this is version 1.0C. If the they have a date stamp of 4-25-96, this is version 1.0C-1. You MUST make sure that you have CA-Visual Objects 1.0C or 1.0C-1 installed BEFORE applying the patch. 3. BEFORE EXECUTING THE PATCH, YOU NEED TO BE AT THE DOS PROMPT. IT IS RECOMMENDED THAT YOU DO NOT EXECUTE THE PATCH PROCESS FROM A DOS SHELL OF MS-WINDOWS BECAUSE OF THE INTENSE MEMORY USAGE OF THIS PROCESS. FROM YOUR CA-VISUAL OBJECTS DIRECTORY execute the following command: PATCH P10C-C2 > PATCH.LOG 4. If you are low on disk space, try the /NOBACKUP option. It eliminates the backup of your original system. For Example : PATCH P10C-C2 /NOBACKUP > PATCH.LOG 5. View PATCH.LOG to verify the patch was applied correctly. NOTE: For Lite users upgrading from 1.0C, 1 error will result on CAVO.EXE. This is normal. See "Changed files and fixes for 1.0C-1" below. You may delete PATCH.EXE and the patch file (*.RTP) from your CA-Visual Objects directory after the successful completion of the patch process. For Full and International versions ----------------------------------- If you are upgrading from 1.0C, 7 files will be updated, with the date/time stamps changed to 4-25-96 1:35AM: CAVO.EXE, CAVORDD.DLL, CAVORDD.LIB, CAVORDDB.DLL, CGGB74MW.DLL, GLCV32MW.DLL, and REPOMNGR.EXE. 8 files will be updated, with the date/time stamps changed to 7-22-96 1:36AM: _DBFCDX.RDD, CAVONT10.DLL, CAVORT10.DLL, CAVORT10.LIB, CGCV74MW.DLL, DBF.RDD, DBFMDX.RDD, and DBFNTX.RDD. All other files will not be changed. When you restart CA-Visual Objects, the HELP ABOUT splash screen will read CA-Visual Objects 1.0c-1 if you upgraded from 1.0c, and will also read CA-Visual Objects 1.0c-1 if you upgraded from 1.0c-1. For Lite version ---------------- If you are upgrading from 1.0C, 6 files will be updated, with the date/time stamps changed to 4-25-96 1:35AM: CAVORDD.DLL, CAVORDD.LIB, CAVORDDB.DLL, CGGB74MW.DLL, GLCV32MW.DLL, and REPOMNGR.EXE. 8 files will be updated, with the date/time stamps changed to 7-22-96 1:36AM: _DBFCDX.RDD, CAVONT10.DLL, CAVORT10.DLL, CAVORT10.LIB, CGCV74MW.DLL, DBF.RDD, DBFMDX.RDD, and DBFNTX.RDD. All other files will not be changed. When you restart CA-Visual Objects, the HELP ABOUT splash screen will still read CA-Visual Objects 1.0c. Changed files and fixes for 1.0C-1 ================================== The following files will be updated by the patch: - CAVO.EXE This change updates the version number. (Does not apply to Lite version) - CAVORDD.DLL (CAVORDD.LIB) The problem of RDDs not being properly unloaded when running multiple CA-Visual Objects applications has been addressed. - CAVORDDB.DLL The problem of RDDs not being properly unloaded when running the DBServer Editor from within the IDE. - CAVORT10.DLL (CAVORT10.LIB) The memory consumption of index creation and the evaluation of macro compiled code blocks has been dramatically reduced. Val() function behavior for decimal separator different from "." corrected. - CGCV74MW.DLL The Windows 95 menu locking problem has been fixed. - CGGB74MW.DLL The behaviour of the SingleEdit:Modified flag has been corrected. - DBFMDX.RDD The problem of RDDs not being properly unloaded when running multiple CA-Visual Objects applications has been addressed. Truncation of memo fields of length 1017-1023 has been fixed. Problem seeking keys beginning with uppercase accented characters has been corrected. - DBFNTX.RDD The problem of RDDs not being properly unloaded when running multiple CA-Visual Objects applications has been addressed. Problem seeking keys beginning with uppercase accented characters has been corrected. - GLCV32MW.DLL MultiLineEdit controls now work correctly with fieldspecs / picture clauses. A memory leak on the usage of custom fonts for controls has been addressed. An ordinal has been changed for compliance with International versions of Windows. - REPOMNGR.EXE Prefixed libraries will be automatically prefixed again after a pack operation. The repository manager will now automatically look for the backup copy of the atom table, if the original atom table file does not exsist. Changed files and fixes for 1.0C-2 ================================== The following files will be updated by the patch: - CAVORT10.DLL (CAVORT10.LIB) Address the problem of using ArrayNew() with the macro compiler. Address the problem of using expressions with aliases with the macro compiler. - CAVONT10.DLL Fixed problems when indexing using the Descend() function. (In general, Descend() only works for OEM DBFs and SetAnsi(.F.). For SetAnsi(.T.) and ANSI DBFs it only works if the Windows-Language is set to English (US).) - CGCV74MW.DLL This address a resource loss problem when using Control:Override() to install a custom event handler. - DBFMDX.RDD Now has improved OEM support for SetAnsi(.T.) Addresses the assertion failed problem. ANSI flag now returns the correct value. - DBFNTX.RDD Now has improved OEM support for SetAnsi(.T.) - _DBFCDX.RDD Now has improved OEM support for SetAnsi(.T.) Addresses problems opening index files. - DBF.RDD Fixed the index corruption problem. Addresses problems using OEM/ANSI replaces with accented characters. Addresses the assertion failed problem.