Copyright: ©1998, FarPoint Technologies, Inc.


Additional Information for C and C++ Users

Using the Spread VBX Control in C++

Using the Spread 32-Bit DLL Control in Borland C

Using the Spread 32-Bit ActiveX Control in MSVC 4.0

Using the Spread 32-Bit ActiveX Control in MSVC 5.0


Using the Spread VBX Control in C++

Due to the complexity of the Spread control, the C++ implementation files are large. To use the Spread VBX control in C++, you might have to break the SSVBXMFC.CPP or SSVBXOWL.CPP files into two files if your C++ compiler cannot handle large files.


Using the Spread 32-Bit DLL Control in Borland C

To use the Spread 32-bit DLL control in Borland C, you must use version 5.0 or later of Borland C's IMPLIB.EXE to generate a valid SPR32D30.LIB. The IMPLIB command does not generate a backward-compatible library for earlier versions of Borland C (that is, for versions previous to version 5.0).


Using the Spread ActiveX Control in MSVC 4.0

To use the Spread ActiveX control in MSVC 4.0, you must generate wrapper classes for the controls.

To generate a wrapper class, you must use an existing application that supports OLE controls, or you must create such an application.

Complete the steps in the following section to create an application that supports OLE controls. If you already have such an application, proceed to the section "Generating a C++ Wrapper for the Spread Control in MSVC 4.0."

Creating a New Application That Supports OLE Controls

To generate a new application that supports OLE controls

1.	In MSVC 4.0, choose New from the File menu.

2.	In the New dialog box, select Project Workspace from the New list.

3.	Choose the OK button.

4.	In the New Project Workspace dialog box,

a.	Select the default item (MFC AppWizard (exe)) from the Type list.

b.	Type a project name into the Name box.

c.	Type a location for your project files in the Location box or choose the Browse button to select a drive and directory.

d.	Choose the Create button.

5.	In the MFC AppWizard - Step 1 dialog box, choose the Next button.

6.	In the MFC AppWizard - Step 2 of 6 dialog box, choose the Next button.

7.	In the MFC AppWizard - Step 3 of 6 dialog box, select the OLE controls check box and choose the Finish button. This accepts the defaults for all other choices.

8.	In the New Project Information dialog box, choose the OK button. MSVC 4.0 generates an application that supports OLE controls.

Generating a C++ Wrapper for the Spread Control in MSVC 4.0

There are two methods for generating C++ wrappers in MSVC 4.0. You can place the control on a dialog, or you can add the control as an application component.

To generate a C++ wrapper with the control on a dialog

1.	Open an existing dialog or create a new dialog in MSVC 4.0. To create a new dialog, select Resource from the Insert menu. Then, in the Insert Resource dialog box, select Dialog from the Resource type list, and then choose the OK button.

2.	Click the right mouse button in the dialog to display the pop-up menu.

3.	Choose Insert OLE Control.

4.	In the Insert OLE Control dialog box, select FarPoint Spread 3.0 from the OLE control list.

5.	Choose the OK button.

6.	Click the right mouse button in the dialog to display the pop-up menu.

7.	Choose ClassWizard.

8.	If you are creating a new dialog, create a C++ class for the dialog using the following steps:

a.	In the Adding a Class dialog box, choose the OK button.

b.	In the Create New Class dialog box under Class Information, type the new name in the Name box.

c.	Choose the Create button.

9.	Create a member variable for the control you inserted into your dialog using the following steps:

a.	In the MFC ClassWizard window on the Member Variables tab, select the control ID of the OLE control you added to the dialog from the Control IDs list.

b.	Choose the Add Variable button.

c.	Choose the OK button in the Microsoft Developer Studio message that explains that a class wrapper will be generated for you.

10.	In the Confirm Classes dialog box, you can modify the class name, implementation file name, and the declaration header file name or accept the defaults provided.

11.	Choose the OK button.

12.	In the Add Member Variable dialog box, type a variable name in  the Member variable name box.

13.	Choose the OK button. ClassWizard generates a wrapper class to support the Spread control.

To generate a C++ wrapper with the control as an application component

1.	In MSVC 4.0, choose Component from the Insert menu.

2.	In the Component Gallery dialog box, choose the OLE Controls tab.

3.	Select the FarPoint Spread 3.0 from the list.

4.	Choose the Insert button.

5.	In the Confirm Classes dialog box, you can modify the class name, implementation file name, and the declaration header file name or accept the defaults provided.

6.	Choose the OK button.

7.	In the Component Gallery dialog box, choose the Close button. ClassWizard generates a wrapper class to support the Spread control.


Using the Spread ActiveX Control in MSVC Version 5.0

To use the Spread ActiveX control in MSVC 5.0, you must generate a wrapper class for the control.

To generate a wrapper class, you must use an existing application that supports ActiveX controls, or you must create such an application.

Complete the steps in the following section to create an application that supports ActiveX controls. If you already have such an application, proceed to the section "Generating a C++ Wrapper in MSVC 5.0."

Creating a New Application That Supports ActiveX Controls

To generate a new application that supports ActiveX controls

1.	In MSVC 5.0, choose New from the File menu.

2.	In the New dialog box, on the Projects tab,

a.	Choose MFC AppWizard (exe).

b.	Provide the project file name and path.

c.	Choose the OK button.

3.	In the MFC AppWizard - Step 1 dialog box, choose the Finish button. This accepts the defaults for all choices.

4.	In the New Project Information dialog box, choose the OK button.

MSVC 5.0 generates an application that supports ActiveX controls.

Generating a C++ Wrapper in MSVC 5.0

There are two methods for generating C++ wrappers in MSVC 5.0. You can place the control on a dialog, or you can add the control as an application component.

To generate a C++ wrapper with the control on a dialog

1.	Open an existing dialog or create a new dialog in MSVC 5.0.

To create a new dialog, select Resource from the Insert menu. Then, in the Insert Resource dialog box, select Dialog from the Resource type list, and then choose the New button.

2.	Click the right mouse button in the dialog to display the pop-up menu.

3.	Choose Insert ActiveX Control.

4.	In the Insert ActiveX Control dialog box,

a.	Select FarPoint Spread 3.0 from the ActiveX control list.

b.	Choose the OK button.

5.	Click the right mouse button in the dialog to display the pop-up menu.

6.	Choose ClassWizard.

7.	If you are creating a new dialog, create a C++ class for the dialog using the following steps:

a.	In the Adding a Class dialog box, choose the OK button.

b.	In the New Class dialog box under Class Information, type the new name in the Name box.

c.	Choose the OK button.

8.	Create a member variable for the control you inserted into your dialog using the following steps:

a.	In the MFC ClassWizard window on the Member Variables tab, select the control ID of the ActiveX control you added to the dialog from the Control IDs list.

b.	Choose the Add Variable button.

c.	Choose the OK button in the Microsoft Developer Studio message that explains that a class wrapper will be generated for you.

9.	In the Confirm Classes dialog box, you can modify the class name, the implementation file name, and the declaration header file name or accept the defaults provided.

10.	Choose the OK button.

11.	In the Add Member Variable dialog box, type a variable name in the Member variable name box, and then choose the OK button.

12.	Choose the OK button.

ClassWizard generates a wrapper class to support the Spread control.

To generate a C++ wrapper with the control as an application component

1.	In MSVC 5.0, from the Projects menu, choose Add to Project, Components and Controls.

2.	In the Components and Controls Gallery dialog box, choose the Registered ActiveX Controls folder.

3.	Select FarPoint Spread 3.0 from the list.

4.	Choose the Insert button, then choose OK to insert the component.

5.	In the Confirm Classes dialog box,

a.	Modify the class name, the implementation file name, and the declaration header file name or accept the defaults provided.

b.	Choose the OK button.

6.	In the Components and Controls Gallery dialog box, choose the Close button.

ClassWizard generates a wrapper class to support the Spread control.


Spread Comment Form
Spread 3.0 Comment Form

If you encounter a problem with this product, or if you would like to share your comments with FarPoint Technologies, please complete and send this form to FarPoint Technologies. Contact us using one of the methods listed in Contacting FarPoint Technologies, Inc.

If you are reporting a problem, please include a detailed description of the problem along with the steps necessary to reproduce it. The preferred method is a sample application that reproduces the problem. If you have a sample, please send it to our Internet address (fpsupport@fpoint.com or FTP to ftp://ftp.fpoint.com); please be sure to include the name of the .ZIP file.

Today's date: ___________________

Customer name: ____________________	Company name: _______________________

Phone number: (_____)_______________	Fax number: (_____)____________________

E-mail address: _____________________	Sample application file name: _____________

Version Number: ________	Control Date: _________________

Control Type (circle one or more):	16-bit DLL	32-bit DLL	VBX	32-bit ActiveX (ADO or DAO)

Development environment: ______________	Version: ______
(for example, Visual Basic, Visual C++, Borland C++)

Description of the problem:

Steps necessary to reproduce the problem:

Comments/Documentation suggestions:


Contacting FarPoint Technologies, Inc.

If you discover a problem with either the software or the accompanying documentation, or if you would like to send us your thoughts about this product, please send us a completed comment form.

Send us the comment form using one of the following methods, or if you call, please provide the information requested on the form to our technical support representative. For additional assistance, contact our Technical Support department.

To contact FarPoint Technologies, Inc.

Call our Technical Support department at (919) 460-1887.

FarPoint Technologies' Technical Support department is available between the hours of 9:00 a.m. and 5:30 p.m. eastern time, Monday through Friday.

Note	If you are using the trial installation, you are provided one support call to our Technical Support department. After you have used your one call, if you need additional technical support you may fax or e-mail our Technical Support department.

Fax us at (919) 460-7606.

Visit our World Wide Web site (http://www.fpoint.com).

Send e-mail to us at farpoint@fpoint.com (general mail), fpsupport@fpoint.com (technical support), or fpdocs@fpoint.com (documentation).

Contact our FTP site (ftp://ftp.fpoint.com).

Write us at:

FarPoint Technologies, Inc.
175 Southport Drive
Suite 900
Morrisville, NC 27560


Installing Spread

Use the installation program to install Spread™. You cannot copy the contents of the distribution files to your hard disk because the information is compressed. Program files must be decompressed and installed in the appropriate directories to run properly.

If you receive an error message while running the installation program, exit Windows, restart it, and run the installation program again. If the installation program still returns an error message after you exit and restart Windows, call FarPoint Technologies' Technical Support department at (919) 460-1887 between the hours of 9:00 a.m. and 5:30 p.m. eastern time, Monday through Friday.

Caution	If you previously purchased and installed a fully licensed version of Spread without the Software Secure technology, we recommend that you do not install the trial version. If you install the trial version of Spread, the 30-day trial version will overwrite the licensed version. Should this occur, you must call our Sales department at (800) 645-5913 to get a serial number to unlock the trial and give you a fully licensed version.

Installing Spread from a downloaded trial version

Installing Spread from the FarPoint Products CD

Installing Spread manually from the FarPoint Products CD

Spread Installed Files


To install Spread from a downloaded trial version

1.	Unzip the distribution file (SPRTRIAL.ZIP) into a temporary directory.

2.	Perform the following steps, depending on your operating environment:

For Windows® 3.1 or Windows NT® (version 3.5 and earlier)

In Program Manager, from the File menu choose Run and type

[drive]:\[directory]\SETUP.EXE

designating the temporary directory used in step 1.

For Windows 95, Windows NT (version 4.0 or later), or Windows 98

a.	Choose the Start button.

b.	Choose Run and type

[drive]:\[directory]\SETUP.EXE

designating the temporary directory used in step 1.

3.	Follow the instructions on the screen to complete the installation.


To install Spread from the FarPoint Products CD

1.	Place the compact disc in the drive.

2.	Perform the following steps, depending on your operating environment:

For Windows® 3.1 or Windows NT® (version 3.5 and earlier)

Run FPDEMO16.EXE or FPDEMO32.EXE, depending on your operating environment.

For Windows 95, Windows NT (version 4.0 or later), or Windows 98

The CD will automatically start and run the FPDEMO32.EXE program.

3.	Choose Install.

4.	Do one of the following:

If you are installing the licensed version of Spread, type your Product Key and Serial Number in the fields provided, then choose the Install button.

If you are installing the trial version of Spread, choose the Install button.

5.	Follow the instructions on the screen to complete the licensed or the trial installation.


To install Spread manually from the FarPoint Products CD

1.	Place the compact disc in the drive.

2.	Perform the following steps, depending on your operating environment:

For Windows® 3.1 or Windows NT® (version 3.5 and earlier)

In Program Manager, from the File menu choose Run and type

[drive]:\PRODUCTS\SPREAD\SETUP.EXE

designating the drive containing the compact disc.

For Windows 95, Windows NT (version 4.0 or later), or Windows 98

a.	Choose the Start button.

b.	Choose Run and type

[drive]:\PRODUCTS\SPREAD\SETUP.EXE

designating the drive containing the compact disc.

3.	Follow the instructions on the screen to complete the licensed or the trial installation.


Spread Installed Files

If you choose the default installation, the Spread installation program copies the following files into your Windows system directory (for example, \WINDOWS\SYSTEM). The installation program also creates a \SPREAD30 directory on your hard disk and copies into it several subdirectories and files. The following table lists the files added to your Windows system directory and to the created directories. Items marked with an asterisk (*) are not installed by the trial installation.

Directory	Files Installed	Description
Your Windows system	SPREAD30.HLP	Help file
directory	SPREAD30.CNT	Help contents file
	SD16D30.EXE	Spread Designer (16-bit)
	SD32D30.EXE	Spread Designer (32-bit)
	MFC42.DLL	Microsoft Foundation Class library file
	MSVCRT.DLL	C run-time libraries
	MSVCRT40.DLL	C run-time libraries
\SPREAD30	SPREADME.HLP	Read Me help file (this file)
	UNWISE.EXE	Uninstall program
\SPREAD30\BIN	SPR16D30.DLL*	Spread 16-bit DLL control
	SPR32D30.DLL*	Spread 32-bit DLL control
	FPSPR30.OCX	Spread 32-bit ActiveX control with ADO support
	SPR32X30.OCX	Spread 32-bit ActiveX control with DAO support
	SPRVBX30.VBX	Spread VBX control
	FPRSPR30.DEP	Visual Basic 5.0/6.0 dependencies file with ADO support
	SPR32X30.DEP	Visual Basic 5.0/6.0 dependencies file with DAO support
	SS30PP.DLL	fpSpreadPreview control property pages
\SPREAD30\DOCS	SPR30UG.PDF*	PDF version of the User's Guide
\SPREAD30\INCLUDE	SSDLL.H	C constant definitions
	SSDLLX.H	Message crackers for C (DLL) users
	SSDLLMFC.H	C++ declarations for MFC users
	SSDLLMFC.CPP	C++ implementation
	SSDLLOWL.H	C++ declarations for OWL users
	SSDLLOWL.CPP	C++ implementation
	SSOCX.H	Constants for C for ActiveX controls
	SSOCX.BAS	Constants for Visual Basic® for ActiveX controls
	SSVBX.H	Constants for VBX control
	SSVBXMFC.H	Header file for MFC for VBX control
	SSVBXMFC.CPP	C++ implementation
	SSVBXOWL.H	Header file for OWL for VBX control
	SSVBXOWL.CPP	C++ implementation
	SSVBX.BAS	Constants for Visual Basic
\SPREAD30\LIB\MS	SPR16D30.LIB*	DLL library (16-bit)
and \BC	SPR32D30.LIB*	DLL library (32-bit)
\SPREAD30\SAMPLES		Contains sample applications for different development environments


Documentation
Documentation—Spread 3.0

Spread provides a User's Guide, an ActiveX/VBX Reference Guide, and a DLL Reference Guide.

User's Guide

The User's Guide is included in the online help file, and for licensed users, it is provided as a PDF file. To view the PDF version of the User's Guide, you must use Adobe® Acrobat® Reader 3.0. You can download the Acrobat Reader free of charge from FarPoint Technologies' web site (www.fpoint.com) or from the Adobe web site (www.adobe.com). The PDF version of the User's Guide is not provided with the trial installation.

If you would like a printed version of the User's Guide, you can purchase a printed copy if you unlock and purchase Spread from the trial version or buy Spread electronically and you do not receive a software package. To do so, please call our sales department at (800) 645-5913 or (919) 460-4551 between 9 a.m. and 5:30 p.m. eastern time, Monday through Friday.

Note	Changes have been made to the User's Guide since the book was printed. For the most up-to-date information, refer to the online help file or the PDF file.

ActiveX/VBX Reference Guide and DLL Reference Guide

The ActiveX/VBX and DLL Reference Guides are included in the online help file. If you are using Windows 95, Windows NT (version 4.0 or later), or Windows 98, you can print the online Reference Guide topics from the Contents page in the online help.

To print the online Reference Guides

1.	Display the Contents page by running the online help file, or if it is already running, by clicking the Contents button.

2.	Select the book labeled Reference Guides.

3.	Click the Print button.

4.	In the Print dialog box, change the settings as you require, then click the OK button.

The topics listed under the Reference Guides book are sent to the specified printer.

Note for Users of Visual Basic 3 and Visual Basic 4 (16-bit)

There are several known problems with accessing our supplied FarPoint help file from VB3 and VB4 16-bit. If you are encountering problems and you are using our VBX control, please place a copy of the VBX control in the same directory as the supplied help file (your Windows system directory, if you performed the default installation). If this does not fix the problem, please contact our Technical Support department at (919) 460-1887 between the hours of 9 a.m. and 5:30 p.m. eastern time, Monday through Friday.


Release Notes
Spread 3.0 Release Notes

Please note the following class name differences:

For the VBX control, the class name is vaSpread.

For the Spread 3.0 DAO ActiveX control, the class name is vaSpread.

For the Spread 3.0 ADO ActiveX control, the class name is fpSpread.

You can enhance the drop-down list portion of the Spread 3.0 combo box cell by using the List Pro version 2.1 fpCombo control. To purchase or download a trial version of List Pro version 2.1, visit our web site at www.fpoint.com.

Spread 3.0 is apartment threaded.

Our HTML export is intended to create a browser-independent HTML table. The HTML tables created by the export feature comply to the HTML 3.2 standard.

There is a new URL function. When you use this formula in a cell, the complete URL address will be exported in the HTML file.

A sample project using the fpSpreadPreview control is provided in the \Spread30\Samples directory.

if your printer does not support the fonts that are used in the spreadsheet and shown on the preview page, Windows will substitute another font. Consequently, the printed spreadsheet will not be the same as what you see on the preview page. To avoid this problem, use TrueType® fonts.

If you are using virtual mode, the fpSpreadPreview control displays only the number of rows that are in the virtual buffer.

If you use the Spread 3.0 ADO ActiveX control, please note that Access 2.0 databases do not seem to be compatible with ADO. Access 7.0 databases are.

If you are upgrading from existing projects that used previous versions of Spread, see Upgrading Existing Projects to Spread Version 3.0 for more information.

If you are using the Spread control in either C or C++, see Additional Information for C and C++ Users for more information about using the controls.

If you use or plan on using the Spread 32-bit ActiveX control, please review the information in Notes for 32-bit ActiveX Users.

Notes for users of the Spread 3.0.00 Beta Release

The GrayAreaMarginType property setting 0 changed from Based on Normal (SS_GRAYAREAMARGINTYPE_BASEDONNORMAL) to Scaled (SS_GRAYAREAMARGINTYPE_SCALED).

The ZoomState property setting 0 changed from Undefined (SS_ZOOMSTATE_UNDEFINED) to Indeterminate (SS_ZOOMSTATE_INDETERMINATE).

Two new values were added to the ButtonDrawMode property, 8 (Always Button) and 16 (Always Combo).

The ClipboardOptions property was changed to include column headers. The new settings are now 0 (No Headers), 1 (Copy Row Headers), 2 (Paste Row Headers), 4 (Copy Column Headers), 8 (Paste Column Headers), 15 (Copy/Paste All Headers). You can combine the 1, 2, 4, and 8 values using the Or operator in code or by adding the values at design time to customize how column and row headers are handled in Clipboard operations.


Notes for 32-bit ActiveX Users

If you use or plan on using the Spread 32-bit ActiveX control in Visual Basic 4 , Visual Basic 5, Visual C++ 4, or Visual C++ 5, please read this important information.

If you have been using Spread releases previous to Spread 2.5.35, before you install Spread 3.0.00 we strongly recommend that you back up your project entirely along with the old Spread OCX files in case you need to revert back to the old version.

Spread was originally developed using Visual C++ 2. At that time, containers serialized controls using property sets. With the advent of Visual Basic 4 (VB4) and Visual C++ 4, Microsoft introduced property bags.

For both property sets and property bags, VB4 stores most properties in the FRM file as a property name and a property value. For blob properties (for example, Spread Designer information), VB4 stores the property name in the FRM file and the property value in the FRX file. However, the blob properties are stored in a different format depending on whether or not property sets or property bags are used. When VB4 reloads the blob from the FRX file, VB4 does not check which method was used to store the blob. This means that blobs stored with property sets will not reload with property bags and blobs stored with property bags will not reload with property sets. Because property bags had no advantage over property sets in VB4 and VB4 has a problem switching between the two, for Spread 2.5.00, we continued to provide only property sets.

When Visual Basic 5 was released, we found that VB5 stores property sets and property bags in a completely different format. VB5 stores property bags the same way as VB4 stores them.  For property sets, VB5 stores the entire property set in the FRX file. But, only the property set values are stored; the property names are not stored. This meant that for future versions of Spread we could not add new features to the property set or remove obsolete features from the property set.

Due to this serious limitation of property sets in VB5, for the 32-bit ActiveX control (SPR32X30.OCX and FPSPR30.OCX), we have switched from property sets to property bags. We are able to work around the VB4 problem of switching from property sets to property bags (our control patches the blob which VB4 sends us).

You can upgrade from previous versions of Spread that use property sets to the new version of Spread  (2.5.35 or later) that uses property bags. However,

•	ONCE YOU UPGRADE YOUR PROJECT TO SPREAD 2.5.35 OR LATER, YOU CANNOT USE A PREVIOUS VERSION OF THE SPREADSHEET.

•	ONCE YOU CONVERT A PROJECT FROM THE SPREAD 16-BIT OCX CONTROL TO THE SPREAD 32-BIT ACTIVEX CONTROL, YOU CANNOT CONVERT BACK TO 16-BIT.


Upgrading Existing Projects to Spread Version 3.0

Upgrading Spread Version 2.5 Projects to Spread Version 3.0

Upgrading Spread/VBX Projects to Spread Version 3.0

Upgrading Spread/VBX++ Projects to Spread Version 3.0


Upgrading Spread Version 2.5 Projects to Spread Version 3.0

Visual Basic

Upgrading Projects that Use the 2.5 VBX Control to Use the 3.0 VBX Control

Upgrading Projects that Use the 2.5 VBX Control to Use the 3.0 DAO ActiveX Control

Converting Projects that Use the 2.5 VBX Control to Use the 3.0 ADO ActiveX Control

Upgrading Projects that Use the 2.5 ActiveX Control to Use the 3.0 DAO ActiveX Control

Converting Projects that Use the 2.5 ActiveX Control to Use the 3.0 ADO ActiveX Control

C++

Upgrading Projects that Use the 2.5 VBX Control to Use the 3.0 VBX Control

Upgrading Projects that Use the 2.5 ActiveX Control to Use the 3.0 DAO ActiveX Control

Upgrading Projects that Use the 2.5 DLL Controls to Use the 3.0 DLL Controls

C

Upgrading Projects that Use the 2.5 DLL Controls to Use the 3.0 DLL Controls


Upgrading Spread/VBX Projects to Spread Version 3.0

Upgrading Visual Basic Projects that Use Spread/VBX Version 2.1to Use the 3.0 VBX Control

Upgrading Visual Basic Projects that Use Spread/VBX Version 2.1 to Use the 3.0 DAO ActiveX Control

Converting Visual Basic Projects that Use Spread/VBX Version 2.1 to Use the 3.0 ADO ActiveX Control


Upgrading Spread/VBX++ Projects to Spread Version 3.0

Upgrading Projects that Use Spread/VBX++ Version 2.0 to Use the 3.0 VBX Control

Upgrading Projects that Use Spread/VBX++ Version 2.0 to Use the 3.0 DAO ActiveX Control


Upgrading Visual Basic Projects that Use the 2.5 VBX Control to Use the 3.0 VBX Control

1.	Open your existing project.

2.	Save the project file and form files as text.

3.	If the project used the file SSVBX.BAS, be sure to use the updated SSVBX.BAS file instead.

To use the updated version of the file, change the path to the location of the updated SSVBX.BAS file.

4.	Edit the project file (.MAK or .VBP) in a text editor to change the following references:

Change . . .	To . . .
SSVBX25.VBX	SPRVBX30.VBX
Also check to make sure that references to SPRVBX30.VBX use the correct path.

5.	Load your project and verify your changes.

6.	If your project used any of the following properties, you must replace the obsolete properties with the new properties provided, as follows:

Property	Instead use . . .
AllowResize	UserResizeCol and UserResizeRow properties
AllowSelBlock	SelectBlockOptions property
CalcDependencies	No replacement. Spread refreshes the dependencies tables automatically as needed.
DataConnect	No replacement. The Q+E Database Library is no longer supported.
DataSelect	No replacement. The Q+E Database Library is no longer supported.
GrayAreaForeColor	No replacement
GridLines	GridShowHoriz and GridShowVert properties
LoadTabFile	SpreadLoadTabFile function
TypeEditCase	TypeEditCharCase property
TypeEditAlign	TypeHAlign property
TypeEditLen	TypeMaxEditLen property
TypeTextAlignHoriz	TypeHAlign property


Upgrading Visual Basic Projects that Use the 2.5 ActiveX Control to Use the 3.0 DAO ActiveX Control

If you formerly used Spread version 2.5 16-bit or 32-bit ActiveX control and now want to use the version 3.0 DAO ActiveX control (32-bit), complete the following steps.

1.	Open your existing project.

2.	Save the project file and form files as text.

3.	If the project used the file SSOCX.BAS, be sure to use the updated SSOCX.BAS file instead.

To use the updated version of the file, change the path to the location of the updated SSOCX.BAS file.

4.	Edit the project file (.MAK or .VBP) in a text editor to change the following references:

Change . . .	To . . .
SS16X25.OCX	SPR32X30.OCX
or

Change . . .	To . . .
SS32X25.OCX	SPR32X30.OCX
5.	If you are using Visual Basic 5, also edit the form files (.FRM) to change the following references:

Change . . .	To . . .
SS16X25.OCX	SPR32X30.OCX
or

Change . . .	To . . .
SS32X25.OCX	SPR32X30.OCX
6.	Load your project and verify your changes.

7.	If your project used any of the following properties, you must replace the obsolete properties with the new properties provided, as follows:

Property	Instead use . . .
AllowResize	UserResizeCol and UserResizeRow properties
AllowSelBlock	SelectBlockOptions property
CalcDependencies	No replacement. Spread refreshes the dependencies tables automatically as needed.
DataConnect	No replacement. The Q+E Database Library is no longer supported.
DataSelect	No replacement. The Q+E Database Library is no longer supported.
GrayAreaForeColor	No replacement
GridLines	GridShowHoriz and GridShowVert properties
LoadTabFile	SpreadLoadTabFile function
TypeEditCase	TypeEditCharCase property
TypeEditAlign	TypeHAlign property
TypeEditLen	TypeMaxEditLen property
TypeTextAlignHoriz	TypeHAlign property


Upgrading Visual Basic Projects that Use the 2.5 VBX Control to Use the 3.0 DAO ActiveX Control

If you formerly used Spread version 2.5 VBX control and now want to use the version 3.0 DAO ActiveX control, complete the following steps.

1.	Open your existing project.

2.	If the project used the file SSVBX.BAS, use the file SSOCX.BAS in place of it.

3.	Save the project file and form files as text.

4.	Edit the project file (.MAK or .VBP) in a text editor to change the following references:

Change . . .	To . . .
SSVBX25.VBX	SPRVBX30.VBX
Also check to make sure that references to SPRVBX30.VBX use the correct path.

5.	Load your project and verify your changes.

6.	Save the project to rewrite the binary data in the .FRX file.

7.	Start Visual Basic 4.0 (32-bit) or Visual Basic 5.0, and load the project file (.MAK or .VBP).

Visual Basic prompts you to upgrade your project to use the Spread 3.0 DAO ActiveX control. The setup program for Spread 3.0 modifies the VB.INI file "VBX Conversions32" section to facilitate this.

8.	Within your project file, update the event parameters as needed. Review the event parameters in the Event Reference in the online Reference Guide.

9.	For each program file (.FRM) containing a spreadsheet, you must change the functions to methods. Compare the following code:

Visual Basic code using Spread 2.5 VBX control

bSuccess = SpreadAddCustomFunction (Spread1, "Cube", 1)
bValid = SpreadIsFormulaValid (Spread1, "a1+b1")
SpreadSetText (Spread1, Col, Row, "Text")

Visual Basic code using the Spread 3.0 DAO ActiveX control

bSuccess = Spread1.AddCustomFunction ("Cube", 1)
bValid = Spread1.IsFormulaValid ("a1+b1")
Spread1.SetText Col, Row, "Text"

10.	Load your project and verify your changes.

11.	If your project used any of the following properties, you must replace the obsolete properties with the new properties provided, as follows:

Property	Instead use . . .
AllowResize	UserResizeCol and UserResizeRow properties
AllowSelBlock	SelectBlockOptions property
CalcDependencies	No replacement. Spread refreshes the dependencies tables automatically as needed.
DataConnect	No replacement. The Q+E Database Library is no longer supported.
DataSelect	No replacement. The Q+E Database Library is no longer supported.
GrayAreaForeColor	No replacement
GridLines	GridShowHoriz and GridShowVert properties
LoadTabFile	SpreadLoadTabFile function
TypeEditCase	TypeEditCharCase property
TypeEditAlign	TypeHAlign property
TypeEditLen	TypeMaxEditLen property
TypeTextAlignHoriz	TypeHAlign property


Upgrading C++ Projects that Use the 2.5 VBX Control to Use the 3.0 VBX Control

If you formerly used the Spread version 2.5 VBX control and now want to use the version 3.0 VBX control, complete the following steps.

1.	Open your existing project.

2.	If the project used the file SSVBX.H, be sure to use the updated SSVBX.H file instead.

To use the updated version of the file, change the path to the location of the updated SSVBX.H file.

3.	If you used a resource editor to put a Spread control on a dialog, open the .RC file as text in a text editor and make the following changes:

Change:	To:
CONTROL "SSVBX25.VBX;vaSpread;	CONTROL "SPRVBX30.VBX;vaSpread;
4.	If you created the control at run time, make the following changes in your .CPP file:

Change:	To:
Create("SSVBX25.VBX;vaSpread;" . . . )	Create("SPRVBX30.VBX;vaSpread;" . . . )
5.	In your project, where you loaded the VBX file, change the following reference:

Change . . .	To . . .
SSVBX25.VBX	SPRVBX30.VBX
6.	If you have linked to either of the following files, be sure to link instead to the updated version of the file provided with Spread 3.0:

If you are using . . .	Use . . .
MFC	SSVBXMFC.CPP
OWL	SSVBXOWL.CPP
7.	Rebuild your project and run it.

8.	If your project used any of the following properties, you must replace the obsolete properties with the new properties provided, as follows:

Property	Instead use . . .
AllowResize	UserResizeCol and UserResizeRow properties
AllowSelBlock	SelectBlockOptions property
CalcDependencies	No replacement. Spread refreshes the dependencies tables automatically as needed.
DataConnect	No replacement. The Q+E Database Library is no longer supported.
DataSelect	No replacement. The Q+E Database Library is no longer supported.
GrayAreaForeColor	No replacement
GridLines	GridShowHoriz and GridShowVert properties
LoadTabFile	SpreadLoadTabFile function
TypeEditCase	TypeEditCharCase property
TypeEditAlign	TypeHAlign property
TypeEditLen	TypeMaxEditLen property
TypeTextAlignHoriz	TypeHAlign property


Converting Visual Basic Projects that Use the 2.5 ActiveX Control to Use the 3.0 ADO ActiveX Control

You cannot upgrade existing projects to use the Spread ADO ActiveX control, but you can convert them by completing the steps in the following topics. The process involves converting your project to use the DAO ActiveX control, and then converting again to use the ADO ActiveX control. You will have to re-create your data binding setup using the ADO Data Control and the ADO ActiveX control.

If you formerly used Spread version 2.5 16-bit or 32-bit ActiveX control and now want to use the version 3.0 ADO ActiveX control (32-bit), complete the following steps.

1.	Open your existing project.

2.	Save the project file and form files as text.

3.	If the project used the file SSOCX.BAS, be sure to use the updated SSOCX.BAS file instead.

To use the updated version of the file, change the path to the location of the updated SSOCX.BAS file.

4.	Edit the project file (.MAK or .VBP) in a text editor to change the following references:

Change . . .	To . . .
SS16X25.OCX	FPSPR30.OCX
or

Change . . .	To . . .
SS32X25.OCX	FPSPR30.OCX
5.	If you are using Visual Basic 5, also edit the form files (.FRM) to change the following references:

Change . . .	To . . .
SS16X25.OCX	FPSPR30.OCX
or

Change . . .	To . . .
SS32X25.OCX	FPSPR30.OCX
6.	Start Visual Basic 6.0 and load the project file (.MAK or .VBP).

When loading the project, you will be prompted to upgrade the controls to their newer versions. Respond OK to have Visual Basic 6.0 upgrade the control from the VBX control to the DAO ActiveX control.

7.	Save and close the project.

8.	Edit the form files (.FRM) in a text editor to change all Spread control references as follows:

Change:

Object="{B02F3647-766B-11CE-AF28-C3A2FBE76A13}#3.0#0"; "SPR32X30.OCX"

To:

Object="{F13C99C0-4D73-11D2-B8B2-0000C00A958C}#3.0#0"; "FPSPR30.OCX"

You will also need to change the class name in the .FRM file as follows:

Change . . .	To . . .
FPSpread.vaSpread	FPSpreadADO.fpSpread
9.	Save the changes to the .FRM files.

10.	Edit the project file (.MAK or .VBP) in a text editor to change the Spread control reference as follows:

Change:

Object={B02F3647-766B-11CE-AF28-C3A2FBE76A13}#3.0#0; SPR32X30.OCX

To:

Object={F13C99C0-4D73-11D2-B8B2-0000C00A958C}#3.0#0; FPSPR30.OCX

11.	Save the changes to the .MAK or .VBP files.

12.	Load the project into Visual Basic 6 and bind the ADO ActiveX control to the ADO Data control.

For instructions and information about binding to the ADO Data control, see Chapter 12, "Binding to Databases," in the User's Guide.

13.	If your project used any of the following properties, you must replace the obsolete properties with the new properties provided, as follows:

Property	Instead use . . .
AllowResize	UserResizeCol and UserResizeRow properties
AllowSelBlock	SelectBlockOptions property
CalcDependencies	No replacement. Spread refreshes the dependencies tables automatically as needed.
DataConnect	No replacement. The Q+E Database Library is no longer supported.
DataSelect	No replacement. The Q+E Database Library is no longer supported.
GrayAreaForeColor	No replacement
GridLines	GridShowHoriz and GridShowVert properties
LoadTabFile	SpreadLoadTabFile function
TypeEditCase	TypeEditCharCase property
TypeEditAlign	TypeHAlign property
TypeEditLen	TypeMaxEditLen property
TypeTextAlignHoriz	TypeHAlign property


Converting Visual Basic Projects that Use the 2.5 VBX Control to Use the 3.0 ADO ActiveX Controls

You cannot upgrade existing projects to use the Spread ADO ActiveX control, but you can convert them by completing the steps in the following topics. The process involves converting your project to use the DAO ActiveX control, and then converting again to use the ADO ActiveX control. You will have to re-create your data binding setup using the ADO Data Control and the ADO ActiveX control.

If you formerly used Spread version 2.5 VBX control and now want to use the version 3.0 ADO ActiveX control, complete the following steps.

1.	Open your existing project.

2.	If the project used the file SSVBX.BAS, use the file SSOCX.BAS in place of it.

3.	Save the project file and form files as text.

4.	Edit the project file (.MAK or .VBP) in a text editor to change the following references:

Change . . .	To . . .
SSVBX25.VBX	SPRVBX30.VBX
Also check to make sure that references to SPRVBX30.VBX use the correct path.

5.	Start Visual Basic 6.0 and load the project file (.MAK or .VBP).

When loading the project, Visual Basic prompts you to upgrade the controls to their newer versions. Respond OK to have Visual Basic 6.0 upgrade the control from the VBX control to the DAO ActiveX control.

6.	Within your project file, update the event parameters as needed. Review the event parameters in the Event Reference in the online Reference Guide.

7.	For each program file (.FRM) containing a spreadsheet, you must change the functions to methods. Compare the following code:

Visual Basic code using Spread 2.5 VBX control

bSuccess = SpreadAddCustomFunction (Spread1, "Cube", 1)
bValid = SpreadIsFormulaValid (Spread1, "a1+b1")
SpreadSetText (Spread1, Col, Row, "Text")

Visual Basic code using the Spread 3.0 DAO ActiveX control

bSuccess = Spread1.AddCustomFunction ("Cube", 1)
bValid = Spread1.IsFormulaValid ("a1+b1")
Spread1.SetText Col, Row, "Text"

8.	Save and close the project.

9.	Edit the form files (.FRM) in a text editor to change all Spread control references as follows:

Change:

Object="{B02F3647-766B-11CE-AF28-C3A2FBE76A13}#3.0#0"; "SPR32X30.OCX"

To:

Object="{F13C99C0-4D73-11D2-B8B2-0000C00A958C}#3.0#0"; "FPSPR30.OCX"

You will also need to change the class name in the .FRM file as follows:

Change . . .	To . . .
FPSpread.vaSpread	FPSpreadADO.fpSpread
10.	Save the changes to the .FRM files.

11.	Edit the project file (.MAK or .VBP) in a text editor to change the Spread control reference as follows:

Change:

Object={B02F3647-766B-11CE-AF28-C3A2FBE76A13}#3.0#0; SPR32X30.OCX

To:

Object={F13C99C0-4D73-11D2-B8B2-0000C00A958C}#3.0#0; FPSPR30.OCX

12.	Save the changes to the .MAK or .VBP files.

13.	Load the project into Visual Basic 6 and bind the ADO ActiveX control to the ADO Data control.

For instructions and information about binding to the ADO Data control, see Chapter 12, "Binding to Databases," in the User's Guide.

14.	If your project used any of the following properties, you must replace the obsolete properties with the new properties provided, as follows:

Property	Instead use . . .
AllowResize	UserResizeCol and UserResizeRow properties
AllowSelBlock	SelectBlockOptions property
CalcDependencies	No replacement. Spread refreshes the dependencies tables automatically as needed.
DataConnect	No replacement. The Q+E Database Library is no longer supported.
DataSelect	No replacement. The Q+E Database Library is no longer supported.
GrayAreaForeColor	No replacement
GridLines	GridShowHoriz and GridShowVert properties
LoadTabFile	SpreadLoadTabFile function
TypeEditCase	TypeEditCharCase property
TypeEditAlign	TypeHAlign property
TypeEditLen	TypeMaxEditLen property
TypeTextAlignHoriz	TypeHAlign property


Upgrading C++ Projects that Use the 2.5 ActiveX Control to Use the 3.0 DAO ActiveX Control

If you formerly used the Spread version 2.5 32-bit ActiveX control and now want to use the version 3.0 DAO ActiveX control, complete the following steps.

1.	Open your existing project.

2.	Remove the wrapper classes for the old version controls from your project. You will need to regenerate these files using the new ActiveX control.

3.	Delete the CLW file for your project. The ClassWizard will regenerate this file when it cannot find it. This step is necessary to force the wrapper classes to be regenerated.

4.	If you used a resource editor to put a Spread control on a dialog, open the .RC file as text in a text editor and make the following change:

Change:	{B02F3641-766B-11CE-AF28-C3A2FBE76A13}
To:	{E2454650-4D87-11D2-B8B2-0000C00A958C}

5.	Open the ClassWizard and allow it to regenerate the CLW file based on the files in your project.

6.	Use the ClassWizard tool to change the class for each member variable for the Spread control. Remove the variable and re-add it, using the same name. ClassWizard will regenerate the wrapper classes for the new ActiveX control the first time an instance of the control is mapped to a member variable.

7.	Rebuild your project and run it.

8.	If your project used any of the following properties, you must replace the obsolete properties with the new properties provided, as follows:

Property	Instead use . . .
AllowResize	UserResizeCol and UserResizeRow properties
AllowSelBlock	SelectBlockOptions property
CalcDependencies	No replacement. Spread refreshes the dependencies tables automatically as needed.
DataConnect	No replacement. The Q+E Database Library is no longer supported.
DataSelect	No replacement. The Q+E Database Library is no longer supported.
GrayAreaForeColor	No replacement
GridLines	GridShowHoriz and GridShowVert properties
LoadTabFile	SpreadLoadTabFile function
TypeEditCase	TypeEditCharCase property
TypeEditAlign	TypeHAlign property
TypeEditLen	TypeMaxEditLen property
TypeTextAlignHoriz	TypeHAlign property


Upgrading C or C++ Projects that Use the 2.5 DLL Controls to Use the 3.0 DLL Controls

If you formerly used Spread version 2.5 DLL controls and now want to use Spread version 3.0 DLL controls, complete the following steps.

1.	Open your existing project.

2.	Update the include path so that the new version of SSDLL.H is included in the project.

3.	Update the include path so that the new versions of SSDLLMFC.H and SSDLLMFC.CPP or SSDLLOWL.H and SSDLLOWL.CPP are included in the project.

4.	If you hard coded the class name of the Spread control in your project, make the following changes:

a.	Either use the define (SS_CLASSNAME) or

b.	Make the following changes as needed:

Change . . .	To . . .
va16Spread25	fp16Spread30 (16-bit DLL)
va32Spread25	fpSpread30 (32-bit DLL)
5.	If you explicitly load the file SS16D25.DLL using the LoadLibrary command, load the file SS16D30.DLL instead.

6.	If your project links to SS16D25.LIB, change the project to link to SPR16D30.LIB instead.

Visual C++ users link Spread30\LIB\MS\SPR16D30.LIB
Borland C++ user link Spread30\LIB\BC\SPR16D30.LIB

7.	If your projects use the SSPrint function SS_PRINTFUNC callback function, you must change the callback function to include the following additional parameter: lpPrintInfo. For more information, refer to the SSPrint function topic in the online DLL Reference Guide.

8.	Rebuild your project and run it.

Note:	To find the class names for 16- or 32-bit controls, search for the define SS_CLASSNAME in the SSDLL.H file.


Upgrading Visual Basic Projects that Use Spread/VBX Version 2.1 to Use the 3.0 VBX Control

If you formerly used Spread/VBX version 2.1 and now want to use the version 3.0 VBX control, complete the following steps.

1.	Open your existing project.

2.	If the project used the file VB_CONST.TXT,use the file SSVBX.BAS in place of it.

3.	Save the project file and form files as text.

4.	Edit the project file (.MAK or .VBP) in a text editor to change the following references:

Change . . .	To . . .
SPREAD20.VBX	SPRVBX30.VBX
Also check to make sure that references to SPRVBX30.VBX use the correct path.

5.	Edit the form files (.FRM) in a text editor to change all Spread class references as follows:

Change . . .	To . . .
Spreadsheet	vaSpread
6.	Load your project and verify your changes.

7.	If your project used any of the following properties, you must replace the obsolete properties with the new properties provided, as follows:

Property	Instead use . . .
AllowResize	UserResizeCol and UserResizeRow properties
AllowSelBlock	SelectBlockOptions property
CalcDependencies	No replacement. Spread refreshes the dependencies tables automatically as needed.
DataConnect	No replacement. The Q+E Database Library is no longer supported.
DataSelect	No replacement. The Q+E Database Library is no longer supported.
GrayAreaForeColor	No replacement
GridLines	GridShowHoriz and GridShowVert properties
LoadTabFile	SpreadLoadTabFile function
TypeEditCase	TypeEditCharCase property
TypeEditAlign	TypeHAlign property
TypeEditLen	TypeMaxEditLen property
TypeTextAlignHoriz	TypeHAlign property


Upgrading Visual Basic Projects that Use Spread/VBX Version 2.1 to Use the 3.0 DAO ActiveX Control

If you formerly used Spread/VBX version 2.1 and now want to use the version 3.0 ActiveX control, complete the following steps.

1.	Open your existing project.

2.	If the project used the file VB_CONST.TXT,use the file SSOCX.BAS in place of it.

3.	Save the project file and form files as text.

4.	Edit the project file (.MAK or .VBP) in a text editor to change the following references:

Change . . .	To . . .
SPREAD20.VBX	SPRVBX30.VBX
Also check to make sure that references to SPRVBX30.VBX use the correct path.

5.	Edit the form files (.FRM) in a text editor to change all Spread class references as follows:

Change . . .	To . . .
Spreadsheet	vaSpread
6.	Load your project and verify your changes.

7.	Save the project to rewrite the binary data in the .FRX file.

8.	Start Visual Basic 4.0 (32-bit) or Visual Basic 5.0 and load the project file (.MAK or .VBP).

Visual Basic prompts you to upgrade your project to the Spread 3.0 DAO ActiveX control. The setup program for Spread 3.0 modifies the VB.INI file "VBX Conversions32" section to facilitate this.

9.	Within your project file, update the event parameters as needed. Review the event parameters in the Event Reference in the online Reference Guide.

10.	For each program file (.FRM) containing a spreadsheet, you must change the functions to methods. Compare the following code:

Visual Basic code using Spread/VBX 2.0

bSuccess = SpreadAddCustomFunction (Spread1, "Cube", 1)
bValid = SpreadIsFormulaValid (Spread1, "a1+b1")
SpreadSetText (Spread1, Col, Row, "Text")

Visual Basic code using the Spread 3.0 ActiveX control

bSuccess = Spread1.AddCustomFunction ("Cube", 1)
bValid = Spread1.IsFormulaValid ("a1+b1")
Spread1.SetText Col, Row, "Text"

11.	Load your project and verify your changes.

12.	If your project used any of the following properties, you must replace the obsolete properties with the new properties provided, as follows:

Property	Instead use . . .
AllowResize	UserResizeCol and UserResizeRow properties
AllowSelBlock	SelectBlockOptions property
CalcDependencies	No replacement. Spread refreshes the dependencies tables automatically as needed.
DataConnect	No replacement. The Q+E Database Library is no longer supported.
DataSelect	No replacement. The Q+E Database Library is no longer supported.
GrayAreaForeColor	No replacement
GridLines	GridShowHoriz and GridShowVert properties
LoadTabFile	SpreadLoadTabFile function
TypeEditCase	TypeEditCharCase property
TypeEditAlign	TypeHAlign property
TypeEditLen	TypeMaxEditLen property
TypeTextAlignHoriz	TypeHAlign property


Converting Visual Basic Projects that Use Spread/VBX Version 2.1 to Use the 3.0 ADO ActiveX Control

You cannot upgrade existing projects to use the Spread ADO ActiveX control, but you can convert them by completing the steps in the following topics. The process involves converting your project to use the DAO ActiveX control, and then converting again to use the ADO ActiveX control. You will have to re-create your data binding setup using the ADO Data Control and the ADO ActiveX control.

If you formerly used used Spread/VBX version 2.1 and now want to use the version 3.0 ADO ActiveX control, complete the following steps.

1.	Open your existing project.

2.	If the project used the file VB_CONST.TXT,use the file SSOCX.BAS in place of it.

3.	Save the project file and form files as text.

4.	Edit the project file (.MAK or .VBP) in a text editor to change the following references:

Change . . .	To . . .
SPREAD20.VBX	SPRVBX30.VBX
Also check to make sure that references to SPRVBX30.VBX use the correct path.

5.	Edit the form files (.FRM) in a text editor to change all Spread class references as follows:

Change . . .	To . . .
Spreadsheet	vaSpread
6.	Load your project and verify your changes.

7.	Save the project to rewrite the binary data in the .FRX file.

8.	Start Visual Basic 6.0 and load the project file (.MAK or .VBP).

When loading the project, Visual Basic prompts you to upgrade the controls to their newer versions. Respond OK to have Visual Basic 6.0 upgrade the control from the VBX control to the DAO ActiveX control.

9.	Within your project file, update the event parameters as needed. Review the event parameters in the Event Reference in the online Reference Guide.

10.	For each program file (.FRM) containing a spreadsheet, you must change the functions to methods. Compare the following code:

Visual Basic code using Spread/VBX 2.1 control

bSuccess = SpreadAddCustomFunction (Spread1, "Cube", 1)
bValid = SpreadIsFormulaValid (Spread1, "a1+b1")
SpreadSetText (Spread1, Col, Row, "Text")

Visual Basic code using the Spread 3.0 DAO ActiveX control

bSuccess = Spread1.AddCustomFunction ("Cube", 1)
bValid = Spread1.IsFormulaValid ("a1+b1")
Spread1.SetText Col, Row, "Text"

11.	Close and save the project.

12.	Edit the form files (.FRM) in a text editor to change all Spread control references as follows:

Change:

Object="{B02F3647-766B-11CE-AF28-C3A2FBE76A13}#3.0#0"; "SPR32X30.OCX"

To:

Object="{F13C99C0-4D73-11D2-B8B2-0000C00A958C}#3.0#0"; "FPSPR30.OCX"

You will also need to change the class name in the .FRM file as follows:

Change . . .	To . . .
FPSpread.vaSpread	FPSpreadADO.fpSpread
13.	Save the changes to the .FRM files.

14.	Edit the form files (.VBP) in a text editor to change the Spread control reference as follows:

Change:

Object={B02F3647-766B-11CE-AF28-C3A2FBE76A13}#3.0#0; SPR32X30.OCX

To:

Object={F13C99C0-4D73-11D2-B8B2-0000C00A958C}#3.0#0; FPSPR30.OCX

15.	Save the changes to the .VBP files.

16.	Load the project into Visual Basic 6 and bind the ADO ActiveX control to the ADO Data control.

For instructions and information about binding to the ADO Data control, see Chapter 12, "Binding to Databases," in the User's Guide.

17.	If your project used any of the following properties, you must replace the obsolete properties with the new properties provided, as follows:

Property	Instead use . . .
AllowResize	UserResizeCol and UserResizeRow properties
AllowSelBlock	SelectBlockOptions property
CalcDependencies	No replacement. Spread refreshes the dependencies tables automatically as needed.
DataConnect	No replacement. The Q+E Database Library is no longer supported.
DataSelect	No replacement. The Q+E Database Library is no longer supported.
GrayAreaForeColor	No replacement
GridLines	GridShowHoriz and GridShowVert properties
LoadTabFile	SpreadLoadTabFile function
TypeEditCase	TypeEditCharCase property
TypeEditAlign	TypeHAlign property
TypeEditLen	TypeMaxEditLen property
TypeTextAlignHoriz	TypeHAlign property


Upgrading Projects that Use Spread/VBX++ Version 2.0 to Use the 3.0 VBX Control

If you formerly used Spread/VBX++ version 2.0 and now want to use the Spread version 3.0 VBX control, complete the following steps.

1.	Open your existing project.

2.	If the project used the file SSPP.H, use the file SSVBX.H in place of it.

3.	If you used AppStudio to put a Spread control on a dialog, open the .RC file as text in a text editor and make the following changes:

Change:	To:
CONTROL "SSPP20.VBX;Spreadsheet;	CONTROL "SPRVBX30.VBX;vaSpread;
4.	If you created the control at run time, make the following changes in your .CPP file:

Change:	To:
Create("SSPP20.VBX;Spreadsheet;" . . . )	Create("SPRVBX30.VBX;vaSpread;" . . . )
5.	In your project, where you loaded the VBX file, change the following reference:

Change . . .	To . . .
SSPP20.VBX	SPRVBX30.VBX
6.	If you have linked to the file SSPP.CPP, link instead to the following file as appropriate:

If you are using . . .	Use . . .
MFC	SSVBXMFC.CPP
OWL	SSVBXOWL.CPP
7.	Rebuild your project and run it.

8.	If your project used any of the following properties, you must replace the obsolete properties with the new properties provided, as follows:

Property	Instead use . . .
AllowResize	UserResizeCol and UserResizeRow properties
AllowSelBlock	SelectBlockOptions property
CalcDependencies	No replacement. Spread refreshes the dependencies tables automatically as needed.
DataConnect	No replacement. The Q+E Database Library is no longer supported.
DataSelect	No replacement. The Q+E Database Library is no longer supported.
GrayAreaForeColor	No replacement
GridLines	GridShowHoriz and GridShowVert properties
LoadTabFile	SpreadLoadTabFile function
TypeEditCase	TypeEditCharCase property
TypeEditAlign	TypeHAlign property
TypeEditLen	TypeMaxEditLen property
TypeTextAlignHoriz	TypeHAlign property


Upgrading Projects that Use Spread/VBX++ Version 2.0 to Use the 3.0 DAO ActiveX Control

If you formerly used Spread/VBX++ version 2.0 and now want to use the Spread version 3.0 DAO ActiveX control, complete the following steps.

1.	Open your existing project.

2.	If the project used the file SSPP.H, use the file SSOCX.H in place of it.

3.	If you used AppStudio to put a Spread control on a dialog, open the .RC file as text in a text editor and make the following changes:

Change:	To:
CONTROL "SSPP20.VBX;Spreadsheet;	CONTROL "SPR32X30.OCX;vaSpread;
4.	If you created the control at run time, make the following changes in your .CPP file:

Change:	To:
Create("SSPP20.VBX;Spreadsheet;" . . . )	Create("SPR32X30.VBX;vaSpread;" . . . )
5.	In your project, where you loaded the VBX file, change the following reference:

Change . . .	To . . .
SSPP20.VBX	SPR32X30.OCX
6.	If you have linked to the file SSPP.CPP, you must instead generate the class wrappers for the ActiveX control using the instructions provided in Additional Information for C and C++ Users.

7.	Rebuild your project and run it.

8.	If your project used any of the following properties, you must replace the obsolete properties with the new properties provided, as follows:

Property	Instead use . . .
AllowResize	UserResizeCol and UserResizeRow properties
AllowSelBlock	SelectBlockOptions property
CalcDependencies	No replacement. Spread refreshes the dependencies tables automatically as needed.
DataConnect	No replacement. The Q+E Database Library is no longer supported.
DataSelect	No replacement. The Q+E Database Library is no longer supported.
GrayAreaForeColor	No replacement
GridLines	GridShowHoriz and GridShowVert properties
LoadTabFile	SpreadLoadTabFile function
TypeEditCase	TypeEditCharCase property
TypeEditAlign	TypeHAlign property
TypeEditLen	TypeMaxEditLen property
TypeTextAlignHoriz	TypeHAlign property


Welcome
Welcome to Spread 3.0

Contacting FarPoint Technologies Installation Trial Information  Documentation Release Notes Upgrade Information Redistribution Information  Notes for 32-bit ActiveX Users Additional Information for C and C++ Users Troubleshooting Comment Form	Choose from the topics on the left to find out more about this release of Spread™. Version: 3.0.05


Trial Information

The trial installation provides you with a 30-day trial version of Spread. After you install the trial version, you may use it for up to 30 days. The time remaining in the trial period is displayed each time you use one of the Spread controls in a project.

This trial version installs the following portions of Spread:

•	ActiveX control

•	VBX control

•	Header files

•	Property pages for the fpSpreadPreview control

•	Spread Designer (16- and 32-bit versions)

•	Online help

•	Samples for ActiveX and VBX controls

•	Additional explanatory files

You can purchase Spread at any time by choosing the Purchase button found on the trial screen or the About Box screen. Follow the instructions provided to contact FarPoint Technologies. Your order is processed while you wait. After your order is processed, you will be given a serial number that will unlock the trial software immediately, giving you a fully licensed version of Spread. This unlocking capability is made possible by our new proprietary SoftwareSecure ™ technology .

After you purchase Spread, you can reinstall the product (Instructions) and install the following portions:

•	DLL controls

•	DLL library files

•	Samples for the DLL controls

•	User's Guide (PDF version)

If you decide not to purchase Spread, we recommend that you uninstall the trial version from your system. To do so, run UNWISE.EXE from the \SPREAD30 directory on your system.

Caution	If you have created projects using the trial version, after the trial version expires if you do not uninstall the trial version you cannot open those projects. To open projects containing expired trial versions of the Spread control, you must uninstall Spread from your system, and then open your project. If you intend to purchase Spread, however, we recommend that you do not open your project until after you purchase and install Spread so as not to lose any settings you set at design time for the Spread control.

Important Note for Visual C++ Developers Using Our 32-Bit ActiveX Controls

If you use the trial version of Spread in projects in Visual C++ and then purchase the licensed version of Spread, you must perform the following steps to use the licensed controls in your existing projects:

1.	Install the licensed version of Spread on your system.

2.	Open your project in Visual C++.

3.	Select the Spread control in your dialog and cut it to the Clipboard to preserve its property settings.

4.	Paste the control back into your dialog.

5.	Perform steps 3 and 4 for each Spread control on dialogs in your project.

6.	Save your project.

You must perform these steps to update the licensing information that is saved with your project at the time you originally created it. If you do not perform these steps, your project will not recognize that you are now using licensed versions of the control.


Troubleshooting

I'm having problems installing the product. What do I do?

How do I redistribute the Spread control with my application?

I've used the trial version, and now I would like to purchase Spread. What do I do?

How do I upgrade from the VBX control to the ActiveX control?

What files does Spread install on my machine?

I am using Windows NT and received a message about access privileges. What does it mean?

My trial version has expired. What do I do?


Windows NT Access Privileges Message

If you are using Windows NT and received a message about access privileges, you do not have sufficient access privileges to modify the SoftwareSecure license information.

You are attempting to modify SoftwareSecure license information, and this product was installed by someone with higher access privileges. (Modifications consist of installing maintenance releases, updates, upgrades, or licensed versions of the product after initially installing the trial version of the product.)

To remedy this situation, have the person who initially installed this product (or someone with the same access privileges as the person who installed it) attempt to perform the task you just tried. If that person receives the same message, contact FarPoint Technologies' Technical Support department at (919) 460-1887 between the hours of 9:00 a.m. and 5:30 p.m. eastern time, Monday through Friday.


Purchasing Spread

1.	Go to the license screen or the About box for Spread.

2.	Call our Sales Department at (800) 645-5913 or (919) 460-4551 between 9 a.m. and 5:30 p.m. eastern time, Monday through Friday, to place your order.

Your order is processed while you wait. After your order is processed, you will be given a serial number that will unlock the trial software, giving you a fully licensed version of Spread.

3.	Type the serial number in the field provided, then choose OK to continue.


Problems with installation

Be sure that you are following the appropriate instructions provided in Installing Spread. Separate instructions are provided depending on how your received the product and which operating environment you are using.

If you are installing a licensed version of the product, make sure that you have entered the correct Product Key and Serial Number. Type the Product Key and Serial Number in the provided fields exactly as they are provided to you, including all punctuation and using uppercase or lowercase letters as appropriate.

If you continue to have problems, contact our Technical Support department at (919) 460-1887 between the hours of 9:00 a.m. and 5:30 p.m. eastern time, Monday through Friday.


Trial Version Expired

If you have installed a trial version of Spread and the trial has expired, you can purchase Spread and unlock your trial version by following the instructions in Purchasing Spread.

If you have decided not to purchase Spread, we recommend that you uninstall the trial version from your system. To do so, run UNWISE.EXE from the \Spread30 directory on your system.

Caution	If you have created projects using the trial version, after the trial version expires if you do not uninstall the trial version you cannot open those projects. To open projects containing expired trial versions of the Spread control, you must uninstall Spread from your system, and then open your project. If you intend to purchase Spread, however, we recommend that you do not open your project until after you purchase and install Spread so as not to lose any settings you set at design time for the Spread control.


Redistributing FarPoint Controls

If you are redistributing a FarPoint control with your application, review the following information concerning the files you must distribute with your application.

ActiveX Controls

DLL Controls

VBX Controls


ActiveX Controls

Before an ActiveX control can be used in your distributed application, it must be included in the Windows registration database. As a developer, you are responsible for registering the ActiveX control files, as well as any files noted below. If the files are already present on the target system, they need not be registered.

Your setup program can register controls and files directly. Use the LoadLibrary Windows API to load the control's DLL or the DLL file, then use GetProcAddress to obtain the address of the "DLLRegisterServer" function, and then call that function.

For additional information, consult your development environment's documentation.

You must include the following files, based on your development environment.

To redistribute the Spread 32-bit ActiveX control, include the following files:

File	Description
SPR32X30.OCX* or FPSPR30.OCX*	Spread 32-bit ActiveX control
MFC42.DLL*	Microsoft Foundation Class library
MSVCRT.DLL	C run-time libraries
MSVCRT40.DLL†	C run-time libraries
* Must be registered on target system.

† If you are developing your application in Visual C++ 4.0 or 4.1, you might need to redistribute this DLL. For more information, refer to Microsoft Knowledge Base articles Q154591 and Q165282.

If you are redistributing the Spread 32-bit ActiveX controls with an international application, include the following files in addition to the preceding files as appropriate:

File	Description
MFC40CHS.DLL	Chinese
MFC40DEU.DLL	German
MFC40ESP.DLL	Spanish
MFC40FRA.DLL	French
MFC40ITA.DLL	Italian
MFC40JAP.DLL	Japanese
MFC40KOR.DLL	Korean


DLL Controls

To redistribute the Spread 16-bit DLL control, include the following file:

File	Description
SPR16D30.DLL	Spread 16-bit DLL control
To redistribute the Spread 32-bit DLL control, include the following file:

File	Description
SPR32D30.DLL	Spread 32-bit DLL control


VBX Controls

To redistribute the Spread VBX control, include the following file:

File	Description
SPRVBX30.VBX	Spread VBX control