![]() Formula One 6.1 Version Read MeThank you for your interest in this version of Formula One. This document provides general information about this version of Formula One. Please read this document completely before using Formula One. Contents
About the Installation ProgramFormula One was developed for Windows 95, Windows 98 and NT 4.0 machines. The installation program will only install on Windows 95, Windows 98 and Windows NT 4.0 machines. Previous major versions of Formula One (eg. 3.0, 4.0, 5.0) can reside on the same machine as this release of Formula One, however Tidestone does recommend uninstalling Formula One 6.0 before installing Formula One 6.1. Back to Table of Contents Installing the ProductThe installation program creates new directories and copies product files to your hard disk. To install a Tidestone ActiveX control on your hard disk:
Back to Table of Contents What Does The Installation Program Do?The installation program performs the following tasks during the installation process:
Back to Table of Contents New Features in Formula One 6.1
Back to Table of Contents International versions of Formula One 6.1Localized versions of Formula One are available for the following languages: German, Italian, French, and Spanish. If you have a copy of the CD, the information about the localized versions can be found in the Readme located in each language's subdirectory of the Localize folder. The CD also contains a Korean-enabled DLL which enables Formula One 6 to be used with Korean Windows. If you do not have a copy of the CD, please refer to www.tidestone.com for more information. Back to Table of Contents List of bugs fixed in Formula One 6.1
Back to Table of Contents List of Installed FilesThe following files are installed in the Formula One program directory (C:\Tidestone\FormOne6 by default):
In addition, the following subdirectories are created in the program directory to hold sample code or redistributable files.
Redistributing ApplicationsThe table below shows all the files necessary for Formula One to operate properly. If you have purchased Formula One and are deploying an application, you must ensure that the first three groups of files listed below exist on your client's machine and are the proper version. The correct versions of these files are provided on the product CD. If your client's machine has older versions of these files, you should update them.
This first group of files are the Formula One redistributable files. These files may be in the Windows system directory, or on the computer's path. The .OCX file must be registered on each user's machine. The Formula One Setup program registers the OCX on your development machine. To register the OCX on the user machines, use the REGSVR32.EXE utilities. These utilities are available from Microsoft. To run these utilities type the following at the command prompt on each user's machine: regsvr32 filename
The second group of files are Microsoft redistributable files necessary for this ActiveX control to operate. Your programming environment should have installed and registered these files. If they were not installed, or they are older versions, the Formula One installer updated and registered them. These files were then copied to the REDIST32 directory in the installation directory, depending on which installation options were chosen. Copy these files from your development machine to your users machines. You may run the installer again and install only these files. These files must be present on your user's machines. Our ActiveX controls require OLE2 support to be installed on a machine. In order to run an application containing one of our controls you must ensure OLE2 has been installed on the user's machine. The third group of files in the table list the OLE2 files accessed by Formula One. Normally, copying these files to the user machine is all that is required. However, some older Windows machines do not have the new OLE2 files installed. You must then install full OLE2 support and ensure that these files are properly registered on the machine. OLE2 files can be downloaded from Microsoft. Microsoft's installer should handle registration for you, but you can also register the files manually using the REGSVR32.EXE. The result code from REGSVR32 will indicate whether any of the files need to be registered. The fourth group of files should be present on any system running Windows. You should not remove or update these files. They are included only to form a complete list of filed needed to use this ActiveX control. Special Note:Some developers develop an application on one machine and then move it to another to build an executable. If you are building an executable containing one of our components, you must be sure that the component is properly installed on the make machine, and that it is the same version as on the development machine. * AXDist.exe is a Microsoft program that installs the URLMon.dll and dependencies in the Windows System directory. It makes the required registry settings on Windows NT 4.0 and Windows 95 machines. These files are needed in order to use the URL property on machines running IE 3 or earlier. You do not need to redistribute the AXDist.exe if you are not planning to use the URL property or if you are deploying to a machine that has IE 4 or later on it. Please note that Microsoft Corporation has found a problem with the AXDist.exe program in IE 4. For more information, see article Q185375 on the Microsoft Support web pages. Tidestone's installer deals with this potential problem by checking to see if IE 4 is on the machine. This is accomplished by searching for Urlmon.dll in the Window's System directory. If Urlmon.dll is not located in the Windows System directory, then IE 3 or earlier (or no version of IE) is on the machine, and the Tidestone installer asks if you want to run AXDist.exe. You only need to run AXDist.exe if you are planning to us the URL property. If Urlmon.dll is located in the Windows System directory, then IE 4 or later is on the machine, and the Tidestone installer does not prompt if you want to run AXDist.exe. Please be aware of these issues if you are planning to redistribute your software with these dlls to end-uses who may be using different versions of IE. Back to Table of Contents Moving the ActiveX ControlDuring the installation process, the ActiveX control and the directory in which it is installed are registered in the Windows Registration Database in Windows 95, Windows 98 and Windows NT. This makes the ActiveX control visible and available to your development environment. However, if you move the ActiveX control to a different directory, or rename the directory that contains it, the information in the registry is no longer valid. This may cause the ActiveX control to be unable to locate its help file. If you find it necessary to move the ActiveX control or rename its directory, use the REGSVR32.EXE utilities provided with most Microsoft development products to reregister the ActiveX control in its new location. The ActiveX control and HLP files must always be in the same directory. Back to Table of Contents Using the UnInstallerFormula One files can be removed from your system with the Add\Remove Programs item or by double-clicking the UnInstaller icon in the Tidestone folder in the Start menu. Using the UnInstaller will remove all files and Registration Database entries made during the installation. If you are using Visual Basic, it will create a support cache file (TTF16.OCA) that must be removed manually. The UnInstaller creates a log of operations during the installation which it "undoes" to "uninstall" the product. You should run the UnInstaller before running the installation program additional times. If you run the installation program a second time without using the UnInstaller first, only the options selected in the second install will be written to the UnInstall log and later be uninstalled. For the UnInstaller to work properly, you should reinstall your original options in addition to the options you wish to install. The operating system does not always immediately update the Windows Start menu. This means that sometimes uninstalled shortcuts do not always disappear right away. Because of this limitation, an uninstalled shortcut can temporarily continue to appear in the Start menu even though it really has been uninstalled. If you wait for a while, run some other programs, or restart the system, the shortcut should eventually disappear from the Start menu. To verify that the program has been uninstalled:
Back to Table of Contents Upgrading Formula One 2 and Excel 4 Files to Formula One 6 File FormatFormula One 2.x workbooksIn order to convert Formula One 2.0 VBX workbooks, you must perform the following steps after successfully installing Formula One 6.1:
Note: You can no longer read in a Formula One 2.x file programmatically. You must use the standalone Workbook Designer to import it, as described above. Excel 4.x filesIn order to convert Excel 4.x files, you must perform the following steps after successfully installating Formula One 6.1:
Note: You can no longer read in an Excel 4 file programmatically. You must use the standalone Workbook Designer to import it, as described above. Back to Table of Contents Compatibility with ExcelWhile Formula One's file format is 100% compatible with the Microsoft Excel file format, certain Formula One feature are not supported by Excel and vice versa. Specifically, Formula One's graphical object (arc, line, oval, polygon, and rectange) are supported by Excel 95 but not by Excel 97. Formula One's form objects (button, check box, and dropdown listbox) and Formula One's picture objects are not supported by Excel. Validation rules created in Formula One are not supported by Excel. Back to Table of Contents Visual Basic Programmers Please NoteProjects created using previous versions of Formula OneIn order to use any projects created with versions earlier than Formula One 6, you need to perform the following steps after successfully installing Formula One 6.1:
For more information about upgrading from previous versions of Formula One, check Tidestone's website at http://www.tidestone.com Multiple versions of Formula One present on a Visual Basic formIf you want to keep multiple versions of Formula One installed as components in Visual Basic, you will need to ensure that code that refers to objects specifies which version of Formula One you want to use. This is because of the names of the objects are the same in both versions so Visual Basic has no way of knowing which version of Formula One you want to use. The following example, which uses the F1RangeRef object, specifies that version 6 of the object should be used: Dim Range as TTF160Ctl.F1RangeRef Another way to fix this problem is to use either the 5.0 or the 6.1 version of the software, but not both. Back to Table of Contents Visual C++ Programmers Please NoteIn order to use any projects created with a previous version of the Formula One ActiveX control, you need to perform the following steps after successfully installing Formula One:
Back to Table of Contents Stand-Alone ApplicationsIn order for drag-and-drop functionality to work in stand-alone applications, you will need to add OleInitialize and OleUninitialize to your stand-alone application. The OleInitialize and OleUninitialize functions need to be added to any C++ application that uses Formula One. Specifically, you should call ::OleInitialize(NULL) in the start up code. ::OleUninitialize() should be called in the exit code of the application. Back to Table of Contents PowerBuilder Programmers Please NoteA keyword name collision currently exists in PowerBuilder with events that have a cancel parameter. PowerBuilder generates an informational error message during compile for applications with OLE controls using such events. The PowerBuilder error message is as follows:
(0006) Information C0148: The identifier 'cancel' conflicts with an existing property with this name. The new definition of 'cancel' will take precedence and the prior value will be ignored until this version of 'cancel' goes out of scope. Action: This is a just a warning; it will not affect the execution of your code. PowerBuilder PTrack Number 343867 Back to Table of Contents Contact Us
Back to Table of Contents |