Dúvida sobre o Delphi 3 Cliente?server Suite
Aqui informa os direitos que eu tenho sobre o Delphi 3 Client/Server Suite.
Porém não entendo plenamente para entender oque esta informando realmente.
Alguem pode me ajudar, nessa tradução.
Para eu saber os direitos que eu terei sobre esse software.
Ass: Max...
//////////////////////////////////////////
SOFTWARE LICENSE AGREEMENTE
BORLAND DELPHI
BORLAND NO-NONSENSE LICENSE STATEMENT AND LIMITED wARRANTY
Borland grants you the right to use this Borland software product (´Software´), including any accompanying documentation, in the manner provided below.
This Software is owned by Borland or its suppliers and is protected by copyright law and international copyright treaty. Therefore, you must treat this Software like any other copyrighted material (e.g., a book), except that you may either make one copy of the Software solely for backup or archival purposes or transfer the Software to a single hard disk provided you keep the original solely for backup or archival purposes.
You may transfer the Software and documentation on a permanent basis provided you retain no copies and the recipient agrees to the terms of this license statement.
Except as provided in this statement, you may not transfer, rent, lease, lend, copy, modify, translate, sublicense, time-share or electronically transmit or receive the
Software, media or documentation. You acknowledge that the Software in source code form remains a confidential trade secret of Borland and/or its suppliers and therefore you agree not to modify the Software or attempt to decipher, decompile, disassemble or reverse engineer the Software, except to the extent applicable laws specifically prohibit such restriction.
If you have purchased an upgrade version of the Software, it constitutes a single product with the Borland software that you upgraded. You may use or transfer the upgrade version of the Software only in accordance with this license statement.
This Software is subject to U.S. Commerce Department export restrictions, and is intended for use in the country into which Borland sold it (or in the EEC, if sold into the EEC).
ADDITIONAL LICENSE TERMS FOR BORLAND DELPHI
Borland grants to you as an individual, a personal, nonexclusive license to install and use the Software for the sole purposes of designing, developing, testing, and deploying application programs which you create. You may install a copy of the Software on a computer and freely move the Software from one computer to another, provided that you are the only individual using the Software. If you are an entity, Borland grants you the right to designate one individual within your organization (´Named User´) to have the right to use the Software in the manner provided above.
GENERAL TERMS THAT APPLY TO COMPILED PROGRAMS AND REDISTRIBUTABLES
You may write and compile your own application programs using the Software, including any libraries and source code included for such purpose with the Software. You may reproduce and distribute, in executable form only, programs which you create using the Software without additional license or fees, subject to all of the conditions in this statement.
Borland products may include certain files (´Redistributables´) intended for distribution by you to the users of programs you create. Redistributables include, for example, those files identified in the accompanying printed or on-line documentation as redistributable files, those files preselected for deployment by an install utility provided with the Software (if any), or those files pre-selected by a third party install utility which operates under control of an install script which Borland has certified (if any) for use by licensed users of this Software for deploying applications. In any event, the Redistributables for the Software are only those files specifically designated as such by Borland. From time to time, Borland may designate other files as Redistributables.
You should refer to the documentation, including any ´readme´ or ´deploy´ files included with the Software, for additional information.
Subject to all of the conditions in this statement, you may reproduce and distribute exact copies of the Redistributables, provided that such copies are made from the original copy of the Software or the copy transferred to the single hard disk. Copies of Redistributables may only be distributed with and for the sole purpose of executing
application programs permitted under this statement that you have created using the Software. Under no circumstances may any copies of Redistributables be distributed separately.
Only you as the Named User have the right to use the Redistributables for developing programs created with the Software; accordingly, you may not share copies of the Redistributables with other co-developers. You may not reproduce or distribute any Borland documentation without Borland´s permission.
The license granted in this statement for you to create your own compiled programs and distribute your programs and the Redistributables (if any) is subject to all of the following conditions: (i) all copies of the programs you create must bear a valid copyright notice, either your own or the Borland copyright notice that appears on the Software; (ii) you may not remove or alter any Borland copyright, trademark or other proprietary rights notice contained in any portion of Borland libraries, source code, Redistributables or other files that bear such a notice; (iii) Borland provides no warranty at all to any person, other than the Limited Warranty provided to the original purchaser of the Software, and you will remain solely responsible to anyone receiving your programs for support, service, upgrades, or technical or other assistance, and such recipients will have no right to contact Borland for such services or assistance; (iv) you will indemnify and hold Borland, its related companies and its suppliers harmless from and against any claims or liabilities arising out of the use, reproduction or distribution of your programs; (v) your programs must be written using a licensed, registered copy of the Software; (vi) your programs may not be merely a set or subset of any of the libraries, code, Redistributables or other files of the Software; and (vii) you may not use Borland´s or any of its suppliers´ names, logos, or trademarks to market your programs, except to state that your program was written using the Software.
All Borland libraries, source code, Redistributables and other files remain Borland´s exclusive property. Regardless of any modifications that you make, you may not distribute any files (particularly Borland source code and other non-executable files) except those that Borland has expressly designated as Redistributables. Nothing in this license statement permits you to derive the source code of files that Borland has provided to you in executable form only, or to reproduce, modify, use, or distribute the source code of such files. You are not, of course, restricted from distributing source code that is entirely your own. Code which you generate with a Borland code generator, such as AppExpert, is considered by Borland to be your code.
ADDITIONAL LICENSE TERMS FOR BORLAND DATABASE ENGINE
You may not redistribute any program which includes Redistributables of the Software identified as BORLAND DATABASE ENGINE (´BDE Redistributables´) that is a general purpose database program or otherwise generally competitive with or a substitute for Borland´s Paradox, dBASE, or the Borland Database Engine. Your programs must require your users to run an unmodified copy of the installation program created by the install utility provided with the Software (if any), or created by a third party install utility which operates under control of an install script which Borland has certified for deploying applications using the BDE Redistributables. Further, you may not redistribute a subset of the BDE Redistributables or circumvent any integrity and/or versioning checks required for correctly installing the BDE Redistributables.
ADDITIONAL LICENSE TERMS FOR DEPLOYING MULTI-TIER PROGRAMS
This version of the software may include redistributable files identified as ´Client Dataset Redistributables´ for creating multi-tier application programs for use in a Client/Server computer network. ´Client/Server computer network´ refers to end-user microcomputers (´Client Computers´) connected to another computer (´Server Computer´) dedicated to managing communications, storing or accessing common data in a database, and providing services requested by the Client Computer(s). Deployment of Client Dataset Redistributables at a Server Computer requires a Client Dataset Server Deployment License from Borland; please refer to the on-line documentation, including DEPLOY.TXT, for contact information. Note that the Client Dataset Server Deployment License is not required for deploying an application in which the Client Computer and the Server Computer are the same physical machine.
LIMITED WARRANTY
Except with respect to the Redistributables, which are provided ´as is,´ without warranty of any kind, Borland warrants that the Software, as updated and when properly used, will perform substantially in accordance with the accompanying documentation, and the Software media will be free from defects in materials and workmanship, for a period of ninety (90) days from the date of receipt. Any implied warranties on the Software are limited to ninety (90) days. Some states/jurisdictions do not allow limitations on duration of an implied warranty, so the above limitation may not apply to you.
Borland´s and its suppliers´ entire liability and your exclusive remedy shall be, at Borland´s option, either (a) return of the price paid, or (b) repair or replacement of the Software that does not meet Borland´s Limited Warranty and which is returned to Borland with a copy of your receipt. DO NOT RETURN ANY PRODUCT UNTIL YOU HAVE CALLED THE BORLAND CUSTOMER SERVICE DEPARTMENT AND OBTAINED A RETURN AUTHORIZATION NUMBER. This Limited Warranty is void if failure of the Software has resulted from accident, abuse, or misapplication. Any replacement Software will be warranted for the remainder of the original warranty period or thirty (30) days, whichever is longer. Outside the United States, neither these remedies nor any product support services offered by Borland are available without proof of purchase from an authorized non-U.S. source.
TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, BORLAND AND ITS SUPPLIERS DISCLAIM ALL OTHER WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE AND WARRANTIES OF NONINFRINGEMENT, WITH REGARD TO THE SOFTWARE AND THE ACCOMPANYING DOCUMENTATION. THIS LIMITED WARRANTY GIVES YOU SPECIFIC LEGAL RIGHTS. YOU MAY HAVE OTHERS, WHICH VARY FROM STATE/JURISDICTION TO STATE/JURISDICTION.
TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, IN NO EVENT SHALL BORLAND OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER (INCLUDING, WITHOUT LIMITATION, DAMAGES
FOR LOSS OF BUSINESS PROFITS, BUSINESS INTERRUPTION, LOSS OF BUSINESS INFORMATION, OR ANY OTHER PECUNIARY LOSS) ARISINGOUT OF THE USE OF OR INABILITY TO USE THIS BORLAND PRODUCT, EVEN IF BORLAND HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. BECAUSE SOME STATES/JURISDICTIONS DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES, THE ABOVE LIMITATION MAY NOT APPLY TO YOU.
HIGH RISK ACTIVITIES
The Software is not fault-tolerant and is not designed, manufactured or intended for use or resale as on-line control equipment in hazardous environments requiring fail-safe performance, such as in the operation of nuclear facilities, aircraft navigation or communication systems, air traffic control, direct life support machines, or weapons systems, in which the failure of the Software could lead directly to death, personal injury, or severe physical or environmental damage (´High Risk Activities´). Borland and its suppliers specifically disclaim any express or implied warranty of fitness for High Risk Activities.
U.S. GOVERNMENT RESTRICTED RIGHTS
The Software and documentation are provided with RESTRICTED RIGHTS. Use, duplication, or disclosure by the Government is subject to restrictions as set forth in subparagraphs (c)(1)(ii) of the Rights in Technical Data and Computer Software clause at DFARS 252.227-7013 or subparagraphs (c)(1) and (2) of the Commercial Computer Software-Restricted Rights at 48 CFR 52.227-19, as applicable. Manufacturer is Borland International, Inc., 100 Borland Way, Scotts Valley, CA 95066.
GENERAL PROVISIONS
This statement may only be modified in writing signed by you and an authorized officer of Borland. If any provision of this statement is found void or unenforceable, the remainder will remain valid and enforceable according to its terms.
If any remedy provided is determined to have failed for its essential purpose, all limitations of liability and exclusions of damages set forth in the Limited Warranty shall remain in effect.
This statement shall be construed, interpreted and governed by the laws of the State of California, U.S.A. This statement gives you specific legal rights; you may have others which vary from state to state and from country to country. Borland reserves all rights not specifically granted in this statement.
Install information
Please read this important installation information before continuing with the Delphi 3 Setup.
DELPHI 3 INSTALLATION NOTES
---------------------------
IMPORTANT:
--------------------------------------------------------
Before installing, you must un-install any previously installed version of Delphi 3. You should also back up your existing IDAPI32.CFG file before installation.
If you have installed any previous release of the MS Internet Control Pack, un-install that version before installing Delphi.
--------------------------------------------------------
Delphi 3 works with the last release of Delphi 2. However, be sure to back up important data, including projects you intend to share between versions 2 and 3, before attempting to install the new version.
Install Delphi from the Setup Launcher on the Delphi CD-ROM.
Under Windows 95 or Windows NT 4.0, the Setup Launcher starts automatically when you insert the CD in your CD drive. Under Windows NT 3.51, run INSTALL.EXE on the CD. To run the Setup Launcher on a network or shared drive, you must map a drive letter to the drive.
From the Setup Launcher, you can install Delphi 3, InstallShield Express, and other programs. You can also connect directly to Borland Online to register your copy of Delphi.
By default, Delphi installs into the \Program Files\Borland\Delphi 3 directory. If you install to a different location, make sure you do not install over any previous Delphi release. The README file and all other documentation assume that you have used the default directory structure.
This release of Delphi includes a new version of the Borland Database Engine. Unless you change the default setup directories, Delphi will overwrite existing 32-bit BDE and SQL Links installations.
After installing, reboot your system so it can replace any files that may have been locked during installation.
---------------------------------------------------------
Please review README.TXT once installation is complete.
Before distributing Delphi applications, please review your license agreement and DEPLOY.TXT (on the Delphi CD or in the Delphi 3 directory).
---------------------------------------------------------
README.TXT contains an overview of the directories on the Delphi CD-ROM.
About Sybase SQL Links (Delphi Client/Server)
---------------------------------------------
If you are installing Delphi and SQL Links for use with Sybase version 4.2 or lower, select DBLIB when prompted by the installation utility. CTLIB is recommended for use with Sybase System 10 and higher.
Minimum System Requirements
---------------------------
Delphi 3 requires Microsoft Windows 95, Windows NT, or a 100¬
compatible operating system; an 80486 or better processor;
8Mb of system memory (12 recommended) for Windows 95, and 16Mb of system memory for Windows NT; a monitor with VGA or higher resolution; a CD-ROM player; and a mouse or other pointing device.
This release is optimized for Windows 95 or Windows NT 4.0, but will also run under Windows NT 3.51 if Service Pack 5 or later is installed.
The table below shows the amount of hard disk space required for an installation of Delphi 3 and the Borland Database Engine. These figures include approximately 10 Mbytes of disk space that are used only during installation.
Version Full Compact
-------------- -------- --------
Standard 130Mb 50Mb
Professional 140Mb 55Mb
Client/Server 170Mb 60Mb
Custom Installation
-------------------
To conserve disk space, you can perform a Custom installation, selecting only the options you require.
If you are installing Delphi Client/Server and you plan to use the TMIDASConnection component, you must install the Internet Controls package.
Un-installing Delphi
--------------------
To remove Delphi from your computer, follow the directions below.
WINDOWS 95 or WINDOWS NT 4.0
Open the Control Panel folder, and double-click the Add/Remove Programs icon. Select Delphi 3 from the list displayed, then click the Add/Remove button. Follow the instructions that appear on the screen.
WINDOWS NT 3.51
Double-click the UnInstall icon in the Delphi program group. Follow the instructions that appear on the screen.
Remember that InterBase and other programs installed from the Setup Launcher require separate un-installation.
NOTE: If you run Delphi setup more than once, un-install remembers only the last-installed Delphi components. For example, suppose you choose not to install the Help filesduring your first setup, and then run setup again, this time selecting only the Help files for installation. If you try to un-install Delphi afterwards, only the Help files will be removed.
----------------------------------------------------------------
Unless otherwise noted, all materials provided in this release are Copyright 1983 - 1997 by Borland International.
----------------------------------------------------------------
---------------------------- END ----------------------------
Remote Dataset License
Please read this important installation information before continuing with the Dephi 3
ADDITIONAL LICENSE TERMS FOR DEPLOYING MULTI-TIER PROGRAMS
This version of the software may include redistributable files identified as ´Client Dataset Redistributables´ for creating multi-tier application programs for use in a Client/Server computer network. ´Client/Server computer network´ refers to end-user microcomputers (´Client Computers´) connected to another computer (´Server Computer´) dedicated to managing communications, storing or accessing common data in a database, and providing services requested by the Client Computer(s). Deployment of Client Dataset Redistributables at a Server Computer requires a Client Dataset Server Deployment License from Borland; please refer to the on-line documentation, including DEPLOY.TXT, for contact information. Note that the Client Dataset Server Deployment License is not required for deploying an application in which the Client Computer and the Server Computer are the same physical machine.
By choosing the AGREE button you accept the license terms above.
Readme Information
Please read this important information before completing the Delphi 3 Setup.
Welcome to the Delphi 3 Client/Server Suite
Contents:
WHERE TO FIND INFORMATION
CONTACTING BORLAND
CD-ROM DIRECTORY OVERVIEW
DEMO APPLICATIONS
INTRABUILDER TRIAL
C++BUILDER TRIAL
DOCUMENTATION UPDATES
KNOWN PROBLEMS
WHERE TO FIND INFORMATION
This file contains last-minute information about Delphi 3.
*********************************************************
Before distributing applications developed with Delphi, please read the guidelines in DEPLOY.TXT (on the Delphi CD or in the Delphi 3 directory).
*********************************************************
For installation instructions and minimum system requirements, see INSTALL.TXT (on the Delphi CD or in the Delphi 3 directory).
For an overview of Delphi and a list of new features, select Help|What´s New from the Delphi main menu.
For information about migrating from previous releases of Delphi, including maintenance of legacy applications and installation of third-party components, see the Compatibility With Version 2 topic in the online Help.
For detailed documentation, see the online Help and printed manuals that accompany this release. Additional documents are on the Delphi CD in the INFO\BORLAND directory. Check Borland´s Web site at http://www.borland.com/ for documentation updates and other information.
NOTE: All printed and online documentation assume that you have installed Delphi using the default directory structure.
Online Resources
----------------
You can get information from any of these online sources:
World Wide Web: http://www.borland.com/
FTP: ftp.borland.com
Technical documents available by anonymous ftp.
Listserv: To subscribe to electronic newsletters, use the online form at http://www.borland.com/feedback/listserv.html or, for Borland´s international listserver, http://www.borland.com/feedback/intlist.html.
TECHFAX 1-800-822-4269 (North America)
Technical documents available by fax.
World Wide Web
--------------
Check Borland´s Web site regularly. The Delphi Product Team will post white papers, competitive analyses, answers to frequently asked questions, sample applications, updated software, and information about new and existing products.
You may want to check these URLs in particular:
http://www.borland.com/delphi/
http://www.borland.com/techsupport/delphi/
http://www.borland.com/techsupport/delphi/downloads/
(updated Help, software, and other files)
http://www.borland.com/delphi/cpp/
(information for C++ programmers)
http://www.borland.com/delphi/vb/
(information for Visual Basic programmers)
http://www.borland.com/newsgroups/
(see below)
Newsgroups
----------
Borland Online hosts a variety of newsgroups where users can exchange information about Borland development tools and their use. For a complete list, see http://www.borland.com/newsgroups/.
In addition to the groups hosted by Borland Online, the following Usenet groups are devoted to Delphi and related programming issues. (These newsgroups are maintained by users and are not official Borland sites.)
news:comp.lang.pascal.delphi.misc
news:comp.lang.pascal.delphi.components
news:comp.lang.pascal.delphi.components.misc
news:comp.lang.pascal.delphi.components.usage
news:comp.lang.pascal.delphi.components.writing
news:comp.lang.pascal.delphi.databases
news:comp.lang.pascal.delphi.advocacy
news:comp.lang.pascal.delphi.announce
news:comp.lang.pascal.borland
CONTACTING BORLAND
Installation Assistance and Developer Support
---------------------------------------------
Borland offers a range of support services for Delphi and other tools. For information, see our World Wide
Web site at http://www.borland.com/.
For assistance outside of North America, contact your local Borland representative. For a list of offices and
distributors world-wide, see http://www.borland.com/bww/.
CD-ROM DIRECTORY OVERVIEW
The Delphi CD ROM includes the following files and directories.
[root] Contains files used for installation and registration as well as these important documents:
INSTALL.TXT Installation instructions.
README.TXT Release notes, last-minute documentation, and a list of known problems.
LICENSE.TXT The Delphi license agreement.
DEPLOY.TXT Information about deploying Delphi applications.
\INSTALL Contains the setup program and related files.
\IB95SRVR Contains the InterBase Server for Windows 95.
(Delphi Client/Server only.)
\INFO Contains subdirectories with information and third-party demo products. The \INFO\EXTRAS
directory contains source code and other files for JPEG and FIF graphics formats, and for data-compression algorithms; for more information, see INFO\EXTRAS\EXTRAS.TXT.
\IE3 Contains Microsoft´s Internet Explorer 3.02 and
Authenticode 2.0.
\TRIALS Contains trial versions of the IntraBuilder Web application development tool (in \TRIALS\INTRABLD) and of C++Builder, Borland´s rapid application development tool for C++ programmers (in \TRIALS\CBUILDER).
\ISXPRESS Contains InstallShield Express, a customized application deployment tool for Delphi 3, the BDE, and related software.
\LOCALIB Contains the Local InterBase software.
(Delphi Client/Server and Delphi Professional.)
\OLENT Contains the OLEnterprise setup program. OLEnterprise, with the Business Object Broker, provides an OLE/DCOM interface to any RPC or COM server. (Delphi Client/Server only.)
\RUNIMAGE Contains a complete Delphi installation. All files are unpacked and in the default directory structure.
\SQL16 Contains 16-bit SQL links for use with Delphi Client/Server. Run SETUP.EXE (in the \SQL16\DISK1 subdirectory) to install SQL Links. (Delphi Client/Server only.)
\DELPHI16 Contains the last 16-bit release of Delphi (version 1.02). Run SETUP.EXE (in the \DELPHI16\INSTALL subdirectory) to install.
DEMO APPLICATIONS
Sample programs, including the ones listed below, are Installed with Delphi in the Delphi 3\Demos\... directory. To build these demos, compile the appropriate .DPR file. With client/server applications, be sure to build and run the server program before building the client. DelCtrls (in ...\ActiveX\Delctrls) includes standard Delphi components in an ActiveX control.
PBag (in ...\ActiveX\PropBag) implements the IPersistPropertyBag interface in an ActiveX control, allowing the control´s properties to be set through HTML tags. TRegSvr (in ...\ActiveX\Tregsvr) is a utility that registers ActiveX servers and type libraries. Webbrows (in ...\Coolstuf) uses the new TToolBar, TCoolBar, and TAnimate components in a Web browser. (Another Web browser, also called Webbrows, is in ...\Internet\Html.) HTTPDemo (in ...\Internet\HTTP) implements a web browser that retrieves the contents of a document from an HTTP server. EmpEdit (in ...\Midas\EmpEdit) uses TClientDataSet to create an editable employee table. The client application is in EMPEDIT.DPR and the server application is in SERVER.DPR. Project Manager (in ...\Midas\Mstrdtl) uses TClientDataSet and TProvider in a master/detail application. The projects in ...\Midas\SetParam illustrate the IProvider SetParams method. The projects in ...\Midas\Adhoc perform ad hoc queries using the provider´s OnDataRequest event. ...\Midas\USQLProv shows a custom TProvider component that implements business rules. ...\Midas\ActiveFM contains an ActiveForm that uses client datasets. Ftp (in ...\Internet\Ftp) is a File Transfer Protocol component that displays and manipulates files on an FTP server. WebServ (in ...\Webserv) is an ISAPI Web-server database application that uses the new Internet components. The first Web page shows a list of customers and company names, with hypertext links to each company´s Web page. NNTPDemo (in ...\Internet\Nntp) is a Usenet newsgroup browser. SimpMail (in ...\Internet\Simpmail) is an SMTP/POP mail client. Chat (in ...\Internet\Chat) is an Internet Chat application that uses the Client and Server socket components. DChat (in ...\Internet\Tcp) is a ´talk´ program that uses the TCP component to transfer text from one computer to another. RichEdit (in ...\Richedit) demonstrates the TRichEdit control. ...\DEMOS\DB contains additional database sample projects. Data used by these examples is in ...\DEMOS\DATA. ...\DEMOS\DOC contains sample projects from the printed documentation. ...\DEMOS\DATA contains data used by sample programs. INTRABUILDER TRIAL
The Delphi CD includes a free 30-day trial edition of Borland´s IntraBuilder. IntraBuilder is a visual JavaScript toolset that has everything you need to build and maintain live, data-driven Web applications and run them on your Web server. To view a self-running demo, or to install the trial version of IntraBuilder, run SETUP.EXE in the \TRIALS\INTRABLD directory of the Delphi CD.
For more information about IntraBuilder, see http://www.borland.com/intrabuilder/.
C++BUILDER TRIAL
The Delphi CD includes a trial edition of C++Builder, Borland´s rapid application development tool for C++ programming. To install the trial version of C++Builder, run SETUP.EXE in the \TRIALS\CBUILDER\SETUP directory of the Delphi CD.
For more information about C++Builder, see http://www.borland.com/bcppbuilder/
DOCUMENTATION UPDATES
VCL documentation and online Help
---------------------------------
The VCL reference material in the online Help is more up to date than the printed version. The following methods are documented only online:
TApplication.NormalizeAllTopMosts TCustomForm.WantChildKey (overridden in TActiveForm) TOleContainer.SaveAsDocument
The correct syntax for the TApplication.MessageBox method is in the online Help. Help entries for the TTable, TImage, and TBDEDataSet objects, among others, have also been revised.
Due to limitations in the WinHelp compiler, Windows API Help topics do not appear in the Delphi Help index. However, these topics are available from the Delphi IDE´s context-sensitive Help system; if you select a Windows API function in the Code editor and press F1, the appropriate Windows Help topic will appear. To see an index of Windows API Help topics, access the Windows API Help directly. The easiest way to do this is to add a button to the speedbar: Right-click on the speedbar and select Properties to open the Speedbar editor; select Help from the Categories list and drag the Windows API Help icon from the Commands list to your speedbar; then close the Speedbar editor.
Components on the Win 3.1 palette page are not linked to the context-sensitive online Help system. For documentation on these legacy components, refer to the DELPHI.HLP file located in \Delphi16\Runimage\Delphi\Bin on your Delphi CD.
Two components on the ActiveX palette page are not linked to the context-sensitive online Help system. For documentation on the VtChart control, see Delphi 3\OCX\Vci\Impress\Vcfi.hlp. For documentation on the Graph Custom Control, see Delphi 3\OCX\Pinnacle\Graph.hlp.
Some database example programs contain hard-coded directory paths. To make these examples compile, you may need to change the directory paths.
Asian calendar eras
-------------------
RTL functions provide increased support for Asian calendar eras. Conversion functions like StrToDate and DateToStr now preserve information about eras.
COMCTL32
--------
Several of the components on the Win32 palette page function best with the latest version (4.70) of COMCTL32.DLL. TCoolBar and TDateTimePicker will not work at all unless version 4.70 or later is installed. In addition, the following properties require version 4.70:
TToolBar.DisabledImages
TToolBar.Flat
TToolBar.HotImages
TToolBar.Images
TTabControl.HotTrack
TTabControl.ScrollOpposite
TTabControl.TabPosition
TPageControl.HotTrack
TPageControl.ScrollOpposite
TPageControl.TabPosition
TListView.Checkboxes
TListView.HotTrack
TListView.GridLines
TListView.RowSelect
TListItem.Checked
The Min, Max, and Position properties of TProgressBar must fall within the range of 0 - 65535 if the installed version of COMCTL32.DLL is less than 4.70.
TRegistry
---------
Under Windows NT, TRegistry can now open and read from the registry even if the user does not have administrative rights.
TMIDASConnection
----------------
The MIDASCon unit, which implements the new TMIDASConnection component, is not contained in any of Delphi´s precompiled runtime packages. You can, however, compile a runtime package of your own that contains this unit.
OLEnterprise
------------
When you run OLEnterprise at design time, the Business Object Broker may connect repeatedly to the same middle-tier server. To test dynamic load balancing, shut down the Delphi IDE and run your application independently.
Free-threading COM servers
--------------------------
To create a free-threading COM server, call CoInitializeEx in the Initialization section of a unit, and list this unit first in your project´s Uses clause. Make sure that the unit does not use ComObj (or any unit that uses ComObj).
IOleCommandTarget
-----------------
The IOleCommandTarget interface now takes PGUID parameters, rather than const TGUID:
IOleCommandTarget = interface(IUnknown) [´{b722bccb-4e68-101b-a2bc-00aa00404770}´] function QueryStatus(CmdGroup: PGUID; cCmds: Cardinal; prgCmds: POleCmd; CmdText: POleCmdText): HResult; stdcall; function Exec(CmdGroup: PGUID; nCmdID, nCmdexecopt: DWORD; const vaIn: OleVariant; var vaOut: OleVariant): HResult; stdcall; end;
This allows IOleCommandTarget to access default standard OLE commands such as PRINT and SAVE. (These commands require that nil be the first parameter passed to the IOleCommandTarget method, but nil cannot be passed as a const TGUID parameter.) Any code that uses IOleCommandTarget should be recompiled. Code that calls the IOleCommandTarget methods must be changed to pass the address of the GUID constant or variable, instead of passing the GUID itself.
ActiveX and Remote Dataset distribution
---------------------------------------
If you deploy an application or library that (a) uses the StdVCL unit and the IStrings, IProvider, or IDataBroker interface, or (b) uses the Delphi font, color, strings, or picture property pages, you must also deploy the Borland standard VCL type library. This library comes in two forms: the STDVCL32.DLL library, and a stand-alone type library called STDVCL32.TLB. Both of these files are in your Windows\System directory. Applications and libraries that use the Delphi property pages must deploy STDVCL32.DLL, but applications and libraries that employ only the interfaces listed above may instead deploy STDVCL32.TLB. Once installed on the destination machine, STDVCL32.DLL or STDVCL32.TLB must be registered in the system registry. (The TRegSvr demo application provides an example of how to register DLL and TLB files.)
Win32 shell extensions
----------------------
Win32 shell extensions require that the threading model for the extension object be set to ´Apartment´ in the system registry. Since TComObjectFactory.UpdateRegistry doesn´t make this entry automatically, you can do it manually by inserting the Value Name ´ThreadingModel´ with the Value ´Apartment´ under the CLSID key for your control in the registry. You can also override TComObjectFactory.UpdateRegistry to do this work for you; the following example code is for a Copy Hook shell extension:
procedure TCopyHookFactory.UpdateRegistry(Register: Boolean);
var
ClsID: string;
begin
ClsID := GUIDToString(ClassID);
inherited UpdateRegistry(Register);
if Register then
begin
CreateRegKey(´CLSID\´ + ClsID, ´ThreadingModel´, ´Apartment´);
CreateRegKey(´directory\shellex\CopyHookHandlers\´ + ClassName,
´´, ClsID);
end
else
DeleteRegKey(´directory\shellex\CopyHookHandlers\´ + ClassName);
end;
Using OpenGL
------------
Applications or libraries that use the OpenGL graphics libraries must ensure that the 8087 control word is set to mask Overflow, Zero Divide, and Invalid Operation exceptions. This is done automatically in the OPENGL unit, but if your application does not use the OPENGL unit (for example, if you are using an ActiveX control that employs OpenGL), you can do this by including the following line in the initialization code of a unit:
Set8087CW($133F);
InterBase ODBC Driver
---------------------
All versions of InterBase now include an ODBC 2.50 driver which is installed with the software.
Borland Database Engine
-----------------------
A Driver Development Kit is available for the BDE. Contact Developer Relations at Borland for details.
SNoTableName and other constants have been moved to the BDEConst unit.
IDAPI functions such as DbiQExecProcDirect and DbiOpenSPParamList now support Access named queries, which the BDE treats as stored procedures.
You can now set the Access SystemDB (workgroup information file) on a per-database basis using the BDE Administrator.
The Access driver now supports referential integrity.
To switch a cursor´s Access locking protocol between pessimistic and optimistic, toggle the Boolean curPESSIMISTICLOCKS property with DbiSetProp.
If you use the Oracle 7.2 or Oracle 7.3 client drivers, open the BDE Administrator, select the Configuration page, and navigate to Configuration/Drivers/Native/ORACLE. Then set VENDOR INIT to ORA72.DLL or ORA73.DLL. Stored procedures that return a result set are supported only for Oracle 7.3.
Using the BDE in ActiveX Controls
---------------------------------
To use the BDE in an ActiveX control, deploy the BDEINST.CAB file. For details, see BDEINST.TXT (in the root directory on the Delphi CD).
Using JPEG Images
-----------------
To use JPEG images at design time, choose Component | Install Component, create a new package, select JPEG as the Unit File Name, and install the package. To use JPEGs in an application at runtime, include the JPEG unit in your unit´s ´uses´ clause.
VCL Help Files
--------------
The VCL Help file (VCL3.HLP) uses another file called VCL3JUMP.HLP to provide context-sensitive jump support. Do not delete this file. If you accidentally delete it, you´ll have to restore it from the Delphi CD.
Overriding Resource-Module Localization
---------------------------------------
At start-up, applications typically check the locale of the system and look for a resource module that matches
the language and country. If you want your application to use a different resource module from the one indicated, you can set an override in the registry: Under the HKEY_Current_User\Software\Borland\Delphi\Locales key, add your application´s path and filename as a string value and set the data value to the extension of your resource modules; at startup, your application will look for resource modules with this extension before using the system locale. For more information, see ´Using Resource Modules´ under the ´Localizing Resources´ Help topic.
Code Signing
------------
To use Delphi´s code-signing features, you must have Internet Explorer 3.02 with the Authenticode 2.0 update. Both of these products are available from the Delphi Setup Launcher. Code-signing options are not available under Windows NT 3.51.
KNOWN PROBLEMS
Installation and Un-installation
--------------------------------
Existing IDAPI32.CFG alias information is not changed by the Delphi 3 installation. Therefore it may be necessary to change the path in the DefaultDD alias to the Delphi 3 data dictionary.
Un-installing Delphi 2 or the C++Builder trial version can remove some Delphi 3 settings and delete components from the palette. We recommend reinstalling Delphi 3 after un-installation of Delphi 2 or C++Builder.
The NetManage Internet Control Pack installed with Delphi is also shipped with other applications, including Visual Basic and PowerBuilder. These components may be unregistered in the process of un-installing another product. If this happens, reinstall Delphi.
After installing the C++Builder trial version, you may need to reset some alias information in the default IDAPI32.CFG. Specifically, the SERVER NAME for the IBLOCAL alias should point to C:\Program Files\Borland\Delphi 3\Demos\Data\EMPLOYEE.GDB. It´s a good idea to back up your IDAPI32.CFG before installing C++Builder.
Integrated Development Environment and VCL
------------------------------------------
TToolButton components don´t resize properly when images in the TToolBar´s ImageList property are modified. To work around this problem, remove images from the ImageList before modifying them; then replace them in the ImageList.
Due to a problem in Microsoft´s COMCTL32.DLL, the Arrange method in TListView does not function. This makes it difficult to clean up the list´s alignment when ViewStyle is vsIcon or vsSmallIcon, but otherwise does not affect the behavior of the component.
Use check boxes in TListView only when ViewStyle is setto vsList or vsReport.
The TLabel.ParentFont property is not used under Windows NT 4.0.
The fsStayOnTop setting for TForm.FormStyle does not function correctly when one fsStayOnTop form launches another. In this case, neither form will consistently remain on top.
Due to an operating-system bug, the TImageList.ResourceLoad method does not load Icon or Cursor files.
If you set TOpenDialog.AllowMultiSelect to True under Windows NT 4.0, a maximum of 20 files are returned. This bug is fixed in Service Pack 2 (available from Microsoft).
Database
--------
The Database Desktop does not display automatically created aliases for ODBC datasources. Always use static, manually created aliases with the ODBC driver.
Due to a known bug in Microsoft´s ODBC 3.4, connecting to a database twice with this driver can cause Delphi to shut down. This problem is fixed in ODBC 3.5.
The BDE no longer supports DbiUseIdleTime. Use DbiSaveChanges instead.
Local SQL queries require a table qualifier or alias name if the field name is in quotation marks. Examples:
(BAD) select name AS ´First Name´ from customer (OK) select name AS customer.´First Name´ from customer (OK) select name AS c.´First Name´ from customer c
When you use cached updates, changes made to indexed table fields are not reflected until the updates are applied.
If you use cached updates with master/detail tables, TQuery will re-execute the detail query each time the master record moves.
Constraint properties for a TField object on a client dataset are ignored.
The floating-point format required for custom constraints is inconsistent with international Windows settings. Always use periods (.) for decimals in custom constraints.
Output BLOB parameters are not supported in stored procedures.
Drag-and-drop copying of tables in the Database Explorer copies only metadata. Data copying will be supported in future releases.
Date-grouping on TClientDataSet is not supported in this version.
If an exception occurs inside the FormCreate event of a remote data module, the exception is displayed interactively. We recommend including a ´try ... except´ clause to handle exceptions in these events.
Save table-level constraints in the Dictionary in the Database Explorer, then read them from Delphi. (Use UpdateDataSet in DRIntF.INT.) Saving constraints from Delphi will be supported in future releases.
The Database Explorer does not support DB2 on the MVS or AS/400 platform.
When setting the BLOB SIZE parameter in the BDE configuration for the Oracle SQL Links driver, add one to the size to prevent data loss. For example, to retrieve 32k of data, set BLOB SIZE to 33 instead of 32.
To execute a parameterized query on an Oracle CHAR field, pad the parameter with blanks. For example, if a query includes where charfld = :c the statement could be modified to where charfld = rpad(:c,20,´ ´) There is no need to do this when using VARCHAR fields.
Informix users should have the latest client DLLs (e.g. ISQLT07C.DLL) from Informix. Otherwise you may get occasional access violations when using the SQL Explorer.
If you open a BLOB field on an Informix 7.2 server, using the Next method to move to another record causes
the server to crash. This is a known problem with the Informix 7.2 software.
The CT-Lib driver works with Sybase version 10.0.4 EBF7033 or higher.
If you use Sybase drivers with cached updates or client data sets, and you use a NUMERIC or DECIMAL field, make sure ENABLE BCD is set to True in the BDE Administrator.
If you use the Sybase CT-Lib driver, you can´t use the pbBlank parameter to check whether a text field is blank; the parameter always returns False. Also, blank BLOBs are always shown as not blank.
To see Oracle Sequences with the Database Explorer, set ENABLE BCD to False in the BDE Administrator.
Due to a problem in Microsoft SQL Server Service Pack 3, BLOB I/O does not work on tables that contain a unique index. When you execute a query under these circumstances, you´ll get a ´Memo Too Large´ error. A fix should be available from Microsoft soon; check Borland´s Web site for details.
Decision Support Components
---------------------------
If you use the Decision Query editor to access tables that are not owned by the login user, the generated SQL statements may by syntactically incorrect. Specifically, you may see
´OwnerName.TableName´
where the correct syntax is
´OwnerName´.´TableName´
If this happens, use the String List editor to edit the dialect part of the query manually in the TDecisionQuery.SQL property. (If you open the Decision Cube editor again, however, your edited query will be overwritten with the incorrect one.)
The same syntax problem causes the Decision Query to display an error message when you run the Decision Cube. The message tells you that the query fields cannot be automatically mapped to dimensions and summaries. If you get this error message, run the Decision Cube editor and provide the necessary field name,
grouping, and dimension type manually.
For more information about using these components, see the Documentation Updates section above.
A bug in Intersolve´s ODBC-Oracle driver causes it to interpret ´--´ as a comment to the end of the file (rather than to the end of the line). If you are using the Intersolve driver, move lines that start with ´--´ to the bottom of the query. Do not remove the lines altogether, since the Decision Query component uses them.
Access Driver
-------------
Some functionality is not yet implemented in this release. BCD (binary coded decimal) support is not available. Key-violation tables cannot be created with DbiAddIndex. (All other DbiAddIndex functionality is supported.) QBE, heterogeneous queries, and queries using the local SQL engine are not supported. In the SDK, DbiDoRestructure and DbiRegenIndex are not available.
The Access driver does not support DAO 3.5 (Access 97). If you upgrade Access 95 to Access 97, DAO 3.0 still resides on your machine, so the driver will function correctly. If you install Access 97 with no prior version of Access 95, the driver will not function.
Because DAO 3.0 (Access 95) is not thread-safe, all database functions must occur in the application´s primary thread.
MS Access does not support opening a table that has already been opened exclusively. Hence opening a table
when TTable.Exclusive is set to True prevents the user from opening that table again, even in same session.
Use a BLOB as a parameter in a query only if the BLOB data is less than 256 bytes.
When the Database Desktop copies an InterBase table to Access, the table and data are copied without indexes. If the table includes an index, you´ll see an ´invalid parameter´ error. Use the Data Pump for this purpose instead.
When borrowing a structure from a Paradox table, the Database Desktop does not copy primary indexes to the resultant Access table. Use the Data Pump for this purpose instead.
AUTOINCREMENT fields do not update correctly when records are added to a table that has at least one other field with a default value.
Internet
--------
In order for the BDE to access paradox or dBASE tables from a Web server application, the Web server must have appropriate access privileges for the disk drive where the table resides. Access privileges may depend on your Web server and how it is configured. See your Web server´s documentation for details.
ActiveX
-------
After generating an ActiveX control, do not change the type library interface from dual interface to dispinterface. The ActiveX Class Framework does not support inheritance from dispinterface.
Delphi-created ActiveX controls and ActiveForms have been tested for use with the following containers: Delphi 3, Delphi 2.0, Borland C++Builder, Visual Basic 4, Visual Basic 5, Access 95, Access 97, ActiveX Control Pad 1.0, Visual C++ 4.2, Visual C++ 5.0, Internet Explorer 3.01 and later, and FrontPage 2.0. There are known problems with ActiveX controls hosted in Microsoft Access 95. Please check the Borland Web site for the most up-to-date information on supported containers.
If you are using ActiveForm controls with Visual Basic 4, remove the OLEMISC_SIMPLEFRAME flag from the factory constructor at the bottom of the ActiveForm unit. Because of a known problem in VB4, ActiveForm and other simple-frame ActiveX controls do not receive event notifications (e.g., for OnClick events) when used in VB4 applications.
Because of a known problem in Visual FoxPro 5.0, Delphi-created ActiveX controls must override the ObjQueryInterface() function to return a pointer to the control´s primary dispatch interface when IDispatch is requested:
function TMyCtl.ObjQueryInterface(const IID: TGUID; out Obj):
Integer;
begin
if IsEqualGuid(IID, IDispatch) then
begin
IMyCtl(Obj) := Self as IMyCtl;
Result := S_OK;
end
else
Result := inherited ObjQueryInterface(IID, Obj);
end;
Some ActiveX controls (such as the IE Pop-up Window from Microsoft) create a window handle as part of their minimal construction, but fail to destroy the handle when the instance is released. Importing such ActiveX controls can crash the IDE.
Because of a known problem with Internet Explorer, arrow keys don´t work inside some ActiveX controls when they are first activated in IE. If you tab out of the control and then tab back into it, the arrow keys will function normally.
Several ActiveX download and security problems were fixed in version 3.02 of Internet Explorer. IE 3.02 is available on the Delphi CD (in the IE3 directory). To determine which version you currently have installed, check the IEXPLORE.EXE date stamp; ´3:02am´ means version 3.02.
To change the name of an ActiveForm, you must perform these three steps in the following order:
1. Use the Object Inspector to change the form´s name. 2. Use the Type Library editor to change the coclass name.
3. Use the Code editor to modify Class_xx in the factory create call (in the form´s initialization section). For example, if you´ve changed the name of the form from MyForm to YourForm, you would change the create call from
TActiveFormFactory.Create(ComServer, TActiveFormControl, TYourForm, Class_MyForm, 1, ´´, OLEMISC_SIMPLEFRAME or OLEMISC_ACTSLIKELABEL);
to
TActiveFormFactory.Create(ComServer, TActiveFormControl, TYourForm, Class_YourForm, 1, ´´, OLEMISC_SIMPLEFRAME or OLEMISC_ACTSLIKELABEL);
The Type Library editor cannot create a property of the type TSafeArray or a function that returns a TSafeArray. Use the OleVariant type instead.
QuickReports
------------
Due to limitations in the conversion process, some complex reports from Delphi 2 may not load properly.
Dynamically Loaded Libraries
----------------------------
Windows NT sometimes incorrectly unloads a library when another library that depends on it fails to load. This problem occurs only when libraries are loaded dynamically under the conditions described below. It affects Windows NT 3.51; Service Pack 2 fixes the bug for Windows NT 4.0.
The problem arises when a dynamically loaded library uses two other libraries, each of which in turn uses another library. Suppose, for example, that an application uses five DLLs that are loaded dynamically in the following order: DLL1, DLL2, DLL3, DLL4, DLL5. Suppose that the following dependencies hold among the DLLs:
DLL5 uses DLL4; DLL4 uses DLL3.
DLL5 uses DLL2; DLL2 uses DLL1.
Suppose the first three DLLs (DLL1-3) load successfully, but DLL4 calls an entry point in DLL3 that has been removed. In this case, DLL5 will naturally fail to load. If a second attempt is made to load the library, Windows will unload
DLL1 and the application program may crash.
This problem can affect installation of packages within the Delphi IDE; it does not affect deployed applications, where packages are statically loaded. If you are using Delphi under Windows NT 3.51, the best way to avoid the problem is to make sure all required packages are updated before you recompile or install components.
----------------------------------------------------------------
Unless otherwise noted, all materials provided in this release are Copyright 1983 - 1997 by Borland International.
----------------------------- END ------------------------------
When you are ready to continue with the setup click the next button or press the Enter Key.
Porém não entendo plenamente para entender oque esta informando realmente.
Alguem pode me ajudar, nessa tradução.
Para eu saber os direitos que eu terei sobre esse software.
Ass: Max...
//////////////////////////////////////////
SOFTWARE LICENSE AGREEMENTE
BORLAND DELPHI
BORLAND NO-NONSENSE LICENSE STATEMENT AND LIMITED wARRANTY
Borland grants you the right to use this Borland software product (´Software´), including any accompanying documentation, in the manner provided below.
This Software is owned by Borland or its suppliers and is protected by copyright law and international copyright treaty. Therefore, you must treat this Software like any other copyrighted material (e.g., a book), except that you may either make one copy of the Software solely for backup or archival purposes or transfer the Software to a single hard disk provided you keep the original solely for backup or archival purposes.
You may transfer the Software and documentation on a permanent basis provided you retain no copies and the recipient agrees to the terms of this license statement.
Except as provided in this statement, you may not transfer, rent, lease, lend, copy, modify, translate, sublicense, time-share or electronically transmit or receive the
Software, media or documentation. You acknowledge that the Software in source code form remains a confidential trade secret of Borland and/or its suppliers and therefore you agree not to modify the Software or attempt to decipher, decompile, disassemble or reverse engineer the Software, except to the extent applicable laws specifically prohibit such restriction.
If you have purchased an upgrade version of the Software, it constitutes a single product with the Borland software that you upgraded. You may use or transfer the upgrade version of the Software only in accordance with this license statement.
This Software is subject to U.S. Commerce Department export restrictions, and is intended for use in the country into which Borland sold it (or in the EEC, if sold into the EEC).
ADDITIONAL LICENSE TERMS FOR BORLAND DELPHI
Borland grants to you as an individual, a personal, nonexclusive license to install and use the Software for the sole purposes of designing, developing, testing, and deploying application programs which you create. You may install a copy of the Software on a computer and freely move the Software from one computer to another, provided that you are the only individual using the Software. If you are an entity, Borland grants you the right to designate one individual within your organization (´Named User´) to have the right to use the Software in the manner provided above.
GENERAL TERMS THAT APPLY TO COMPILED PROGRAMS AND REDISTRIBUTABLES
You may write and compile your own application programs using the Software, including any libraries and source code included for such purpose with the Software. You may reproduce and distribute, in executable form only, programs which you create using the Software without additional license or fees, subject to all of the conditions in this statement.
Borland products may include certain files (´Redistributables´) intended for distribution by you to the users of programs you create. Redistributables include, for example, those files identified in the accompanying printed or on-line documentation as redistributable files, those files preselected for deployment by an install utility provided with the Software (if any), or those files pre-selected by a third party install utility which operates under control of an install script which Borland has certified (if any) for use by licensed users of this Software for deploying applications. In any event, the Redistributables for the Software are only those files specifically designated as such by Borland. From time to time, Borland may designate other files as Redistributables.
You should refer to the documentation, including any ´readme´ or ´deploy´ files included with the Software, for additional information.
Subject to all of the conditions in this statement, you may reproduce and distribute exact copies of the Redistributables, provided that such copies are made from the original copy of the Software or the copy transferred to the single hard disk. Copies of Redistributables may only be distributed with and for the sole purpose of executing
application programs permitted under this statement that you have created using the Software. Under no circumstances may any copies of Redistributables be distributed separately.
Only you as the Named User have the right to use the Redistributables for developing programs created with the Software; accordingly, you may not share copies of the Redistributables with other co-developers. You may not reproduce or distribute any Borland documentation without Borland´s permission.
The license granted in this statement for you to create your own compiled programs and distribute your programs and the Redistributables (if any) is subject to all of the following conditions: (i) all copies of the programs you create must bear a valid copyright notice, either your own or the Borland copyright notice that appears on the Software; (ii) you may not remove or alter any Borland copyright, trademark or other proprietary rights notice contained in any portion of Borland libraries, source code, Redistributables or other files that bear such a notice; (iii) Borland provides no warranty at all to any person, other than the Limited Warranty provided to the original purchaser of the Software, and you will remain solely responsible to anyone receiving your programs for support, service, upgrades, or technical or other assistance, and such recipients will have no right to contact Borland for such services or assistance; (iv) you will indemnify and hold Borland, its related companies and its suppliers harmless from and against any claims or liabilities arising out of the use, reproduction or distribution of your programs; (v) your programs must be written using a licensed, registered copy of the Software; (vi) your programs may not be merely a set or subset of any of the libraries, code, Redistributables or other files of the Software; and (vii) you may not use Borland´s or any of its suppliers´ names, logos, or trademarks to market your programs, except to state that your program was written using the Software.
All Borland libraries, source code, Redistributables and other files remain Borland´s exclusive property. Regardless of any modifications that you make, you may not distribute any files (particularly Borland source code and other non-executable files) except those that Borland has expressly designated as Redistributables. Nothing in this license statement permits you to derive the source code of files that Borland has provided to you in executable form only, or to reproduce, modify, use, or distribute the source code of such files. You are not, of course, restricted from distributing source code that is entirely your own. Code which you generate with a Borland code generator, such as AppExpert, is considered by Borland to be your code.
ADDITIONAL LICENSE TERMS FOR BORLAND DATABASE ENGINE
You may not redistribute any program which includes Redistributables of the Software identified as BORLAND DATABASE ENGINE (´BDE Redistributables´) that is a general purpose database program or otherwise generally competitive with or a substitute for Borland´s Paradox, dBASE, or the Borland Database Engine. Your programs must require your users to run an unmodified copy of the installation program created by the install utility provided with the Software (if any), or created by a third party install utility which operates under control of an install script which Borland has certified for deploying applications using the BDE Redistributables. Further, you may not redistribute a subset of the BDE Redistributables or circumvent any integrity and/or versioning checks required for correctly installing the BDE Redistributables.
ADDITIONAL LICENSE TERMS FOR DEPLOYING MULTI-TIER PROGRAMS
This version of the software may include redistributable files identified as ´Client Dataset Redistributables´ for creating multi-tier application programs for use in a Client/Server computer network. ´Client/Server computer network´ refers to end-user microcomputers (´Client Computers´) connected to another computer (´Server Computer´) dedicated to managing communications, storing or accessing common data in a database, and providing services requested by the Client Computer(s). Deployment of Client Dataset Redistributables at a Server Computer requires a Client Dataset Server Deployment License from Borland; please refer to the on-line documentation, including DEPLOY.TXT, for contact information. Note that the Client Dataset Server Deployment License is not required for deploying an application in which the Client Computer and the Server Computer are the same physical machine.
LIMITED WARRANTY
Except with respect to the Redistributables, which are provided ´as is,´ without warranty of any kind, Borland warrants that the Software, as updated and when properly used, will perform substantially in accordance with the accompanying documentation, and the Software media will be free from defects in materials and workmanship, for a period of ninety (90) days from the date of receipt. Any implied warranties on the Software are limited to ninety (90) days. Some states/jurisdictions do not allow limitations on duration of an implied warranty, so the above limitation may not apply to you.
Borland´s and its suppliers´ entire liability and your exclusive remedy shall be, at Borland´s option, either (a) return of the price paid, or (b) repair or replacement of the Software that does not meet Borland´s Limited Warranty and which is returned to Borland with a copy of your receipt. DO NOT RETURN ANY PRODUCT UNTIL YOU HAVE CALLED THE BORLAND CUSTOMER SERVICE DEPARTMENT AND OBTAINED A RETURN AUTHORIZATION NUMBER. This Limited Warranty is void if failure of the Software has resulted from accident, abuse, or misapplication. Any replacement Software will be warranted for the remainder of the original warranty period or thirty (30) days, whichever is longer. Outside the United States, neither these remedies nor any product support services offered by Borland are available without proof of purchase from an authorized non-U.S. source.
TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, BORLAND AND ITS SUPPLIERS DISCLAIM ALL OTHER WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE AND WARRANTIES OF NONINFRINGEMENT, WITH REGARD TO THE SOFTWARE AND THE ACCOMPANYING DOCUMENTATION. THIS LIMITED WARRANTY GIVES YOU SPECIFIC LEGAL RIGHTS. YOU MAY HAVE OTHERS, WHICH VARY FROM STATE/JURISDICTION TO STATE/JURISDICTION.
TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, IN NO EVENT SHALL BORLAND OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER (INCLUDING, WITHOUT LIMITATION, DAMAGES
FOR LOSS OF BUSINESS PROFITS, BUSINESS INTERRUPTION, LOSS OF BUSINESS INFORMATION, OR ANY OTHER PECUNIARY LOSS) ARISINGOUT OF THE USE OF OR INABILITY TO USE THIS BORLAND PRODUCT, EVEN IF BORLAND HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. BECAUSE SOME STATES/JURISDICTIONS DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES, THE ABOVE LIMITATION MAY NOT APPLY TO YOU.
HIGH RISK ACTIVITIES
The Software is not fault-tolerant and is not designed, manufactured or intended for use or resale as on-line control equipment in hazardous environments requiring fail-safe performance, such as in the operation of nuclear facilities, aircraft navigation or communication systems, air traffic control, direct life support machines, or weapons systems, in which the failure of the Software could lead directly to death, personal injury, or severe physical or environmental damage (´High Risk Activities´). Borland and its suppliers specifically disclaim any express or implied warranty of fitness for High Risk Activities.
U.S. GOVERNMENT RESTRICTED RIGHTS
The Software and documentation are provided with RESTRICTED RIGHTS. Use, duplication, or disclosure by the Government is subject to restrictions as set forth in subparagraphs (c)(1)(ii) of the Rights in Technical Data and Computer Software clause at DFARS 252.227-7013 or subparagraphs (c)(1) and (2) of the Commercial Computer Software-Restricted Rights at 48 CFR 52.227-19, as applicable. Manufacturer is Borland International, Inc., 100 Borland Way, Scotts Valley, CA 95066.
GENERAL PROVISIONS
This statement may only be modified in writing signed by you and an authorized officer of Borland. If any provision of this statement is found void or unenforceable, the remainder will remain valid and enforceable according to its terms.
If any remedy provided is determined to have failed for its essential purpose, all limitations of liability and exclusions of damages set forth in the Limited Warranty shall remain in effect.
This statement shall be construed, interpreted and governed by the laws of the State of California, U.S.A. This statement gives you specific legal rights; you may have others which vary from state to state and from country to country. Borland reserves all rights not specifically granted in this statement.
Install information
Please read this important installation information before continuing with the Delphi 3 Setup.
DELPHI 3 INSTALLATION NOTES
---------------------------
IMPORTANT:
--------------------------------------------------------
Before installing, you must un-install any previously installed version of Delphi 3. You should also back up your existing IDAPI32.CFG file before installation.
If you have installed any previous release of the MS Internet Control Pack, un-install that version before installing Delphi.
--------------------------------------------------------
Delphi 3 works with the last release of Delphi 2. However, be sure to back up important data, including projects you intend to share between versions 2 and 3, before attempting to install the new version.
Install Delphi from the Setup Launcher on the Delphi CD-ROM.
Under Windows 95 or Windows NT 4.0, the Setup Launcher starts automatically when you insert the CD in your CD drive. Under Windows NT 3.51, run INSTALL.EXE on the CD. To run the Setup Launcher on a network or shared drive, you must map a drive letter to the drive.
From the Setup Launcher, you can install Delphi 3, InstallShield Express, and other programs. You can also connect directly to Borland Online to register your copy of Delphi.
By default, Delphi installs into the \Program Files\Borland\Delphi 3 directory. If you install to a different location, make sure you do not install over any previous Delphi release. The README file and all other documentation assume that you have used the default directory structure.
This release of Delphi includes a new version of the Borland Database Engine. Unless you change the default setup directories, Delphi will overwrite existing 32-bit BDE and SQL Links installations.
After installing, reboot your system so it can replace any files that may have been locked during installation.
---------------------------------------------------------
Please review README.TXT once installation is complete.
Before distributing Delphi applications, please review your license agreement and DEPLOY.TXT (on the Delphi CD or in the Delphi 3 directory).
---------------------------------------------------------
README.TXT contains an overview of the directories on the Delphi CD-ROM.
About Sybase SQL Links (Delphi Client/Server)
---------------------------------------------
If you are installing Delphi and SQL Links for use with Sybase version 4.2 or lower, select DBLIB when prompted by the installation utility. CTLIB is recommended for use with Sybase System 10 and higher.
Minimum System Requirements
---------------------------
Delphi 3 requires Microsoft Windows 95, Windows NT, or a 100¬
compatible operating system; an 80486 or better processor;
8Mb of system memory (12 recommended) for Windows 95, and 16Mb of system memory for Windows NT; a monitor with VGA or higher resolution; a CD-ROM player; and a mouse or other pointing device.
This release is optimized for Windows 95 or Windows NT 4.0, but will also run under Windows NT 3.51 if Service Pack 5 or later is installed.
The table below shows the amount of hard disk space required for an installation of Delphi 3 and the Borland Database Engine. These figures include approximately 10 Mbytes of disk space that are used only during installation.
Version Full Compact
-------------- -------- --------
Standard 130Mb 50Mb
Professional 140Mb 55Mb
Client/Server 170Mb 60Mb
Custom Installation
-------------------
To conserve disk space, you can perform a Custom installation, selecting only the options you require.
If you are installing Delphi Client/Server and you plan to use the TMIDASConnection component, you must install the Internet Controls package.
Un-installing Delphi
--------------------
To remove Delphi from your computer, follow the directions below.
WINDOWS 95 or WINDOWS NT 4.0
Open the Control Panel folder, and double-click the Add/Remove Programs icon. Select Delphi 3 from the list displayed, then click the Add/Remove button. Follow the instructions that appear on the screen.
WINDOWS NT 3.51
Double-click the UnInstall icon in the Delphi program group. Follow the instructions that appear on the screen.
Remember that InterBase and other programs installed from the Setup Launcher require separate un-installation.
NOTE: If you run Delphi setup more than once, un-install remembers only the last-installed Delphi components. For example, suppose you choose not to install the Help filesduring your first setup, and then run setup again, this time selecting only the Help files for installation. If you try to un-install Delphi afterwards, only the Help files will be removed.
----------------------------------------------------------------
Unless otherwise noted, all materials provided in this release are Copyright 1983 - 1997 by Borland International.
----------------------------------------------------------------
---------------------------- END ----------------------------
Remote Dataset License
Please read this important installation information before continuing with the Dephi 3
ADDITIONAL LICENSE TERMS FOR DEPLOYING MULTI-TIER PROGRAMS
This version of the software may include redistributable files identified as ´Client Dataset Redistributables´ for creating multi-tier application programs for use in a Client/Server computer network. ´Client/Server computer network´ refers to end-user microcomputers (´Client Computers´) connected to another computer (´Server Computer´) dedicated to managing communications, storing or accessing common data in a database, and providing services requested by the Client Computer(s). Deployment of Client Dataset Redistributables at a Server Computer requires a Client Dataset Server Deployment License from Borland; please refer to the on-line documentation, including DEPLOY.TXT, for contact information. Note that the Client Dataset Server Deployment License is not required for deploying an application in which the Client Computer and the Server Computer are the same physical machine.
By choosing the AGREE button you accept the license terms above.
Readme Information
Please read this important information before completing the Delphi 3 Setup.
Welcome to the Delphi 3 Client/Server Suite
Contents:
WHERE TO FIND INFORMATION
CONTACTING BORLAND
CD-ROM DIRECTORY OVERVIEW
DEMO APPLICATIONS
INTRABUILDER TRIAL
C++BUILDER TRIAL
DOCUMENTATION UPDATES
KNOWN PROBLEMS
WHERE TO FIND INFORMATION
This file contains last-minute information about Delphi 3.
*********************************************************
Before distributing applications developed with Delphi, please read the guidelines in DEPLOY.TXT (on the Delphi CD or in the Delphi 3 directory).
*********************************************************
For installation instructions and minimum system requirements, see INSTALL.TXT (on the Delphi CD or in the Delphi 3 directory).
For an overview of Delphi and a list of new features, select Help|What´s New from the Delphi main menu.
For information about migrating from previous releases of Delphi, including maintenance of legacy applications and installation of third-party components, see the Compatibility With Version 2 topic in the online Help.
For detailed documentation, see the online Help and printed manuals that accompany this release. Additional documents are on the Delphi CD in the INFO\BORLAND directory. Check Borland´s Web site at http://www.borland.com/ for documentation updates and other information.
NOTE: All printed and online documentation assume that you have installed Delphi using the default directory structure.
Online Resources
----------------
You can get information from any of these online sources:
World Wide Web: http://www.borland.com/
FTP: ftp.borland.com
Technical documents available by anonymous ftp.
Listserv: To subscribe to electronic newsletters, use the online form at http://www.borland.com/feedback/listserv.html or, for Borland´s international listserver, http://www.borland.com/feedback/intlist.html.
TECHFAX 1-800-822-4269 (North America)
Technical documents available by fax.
World Wide Web
--------------
Check Borland´s Web site regularly. The Delphi Product Team will post white papers, competitive analyses, answers to frequently asked questions, sample applications, updated software, and information about new and existing products.
You may want to check these URLs in particular:
http://www.borland.com/delphi/
http://www.borland.com/techsupport/delphi/
http://www.borland.com/techsupport/delphi/downloads/
(updated Help, software, and other files)
http://www.borland.com/delphi/cpp/
(information for C++ programmers)
http://www.borland.com/delphi/vb/
(information for Visual Basic programmers)
http://www.borland.com/newsgroups/
(see below)
Newsgroups
----------
Borland Online hosts a variety of newsgroups where users can exchange information about Borland development tools and their use. For a complete list, see http://www.borland.com/newsgroups/.
In addition to the groups hosted by Borland Online, the following Usenet groups are devoted to Delphi and related programming issues. (These newsgroups are maintained by users and are not official Borland sites.)
news:comp.lang.pascal.delphi.misc
news:comp.lang.pascal.delphi.components
news:comp.lang.pascal.delphi.components.misc
news:comp.lang.pascal.delphi.components.usage
news:comp.lang.pascal.delphi.components.writing
news:comp.lang.pascal.delphi.databases
news:comp.lang.pascal.delphi.advocacy
news:comp.lang.pascal.delphi.announce
news:comp.lang.pascal.borland
CONTACTING BORLAND
Installation Assistance and Developer Support
---------------------------------------------
Borland offers a range of support services for Delphi and other tools. For information, see our World Wide
Web site at http://www.borland.com/.
For assistance outside of North America, contact your local Borland representative. For a list of offices and
distributors world-wide, see http://www.borland.com/bww/.
CD-ROM DIRECTORY OVERVIEW
The Delphi CD ROM includes the following files and directories.
[root] Contains files used for installation and registration as well as these important documents:
INSTALL.TXT Installation instructions.
README.TXT Release notes, last-minute documentation, and a list of known problems.
LICENSE.TXT The Delphi license agreement.
DEPLOY.TXT Information about deploying Delphi applications.
\INSTALL Contains the setup program and related files.
\IB95SRVR Contains the InterBase Server for Windows 95.
(Delphi Client/Server only.)
\INFO Contains subdirectories with information and third-party demo products. The \INFO\EXTRAS
directory contains source code and other files for JPEG and FIF graphics formats, and for data-compression algorithms; for more information, see INFO\EXTRAS\EXTRAS.TXT.
\IE3 Contains Microsoft´s Internet Explorer 3.02 and
Authenticode 2.0.
\TRIALS Contains trial versions of the IntraBuilder Web application development tool (in \TRIALS\INTRABLD) and of C++Builder, Borland´s rapid application development tool for C++ programmers (in \TRIALS\CBUILDER).
\ISXPRESS Contains InstallShield Express, a customized application deployment tool for Delphi 3, the BDE, and related software.
\LOCALIB Contains the Local InterBase software.
(Delphi Client/Server and Delphi Professional.)
\OLENT Contains the OLEnterprise setup program. OLEnterprise, with the Business Object Broker, provides an OLE/DCOM interface to any RPC or COM server. (Delphi Client/Server only.)
\RUNIMAGE Contains a complete Delphi installation. All files are unpacked and in the default directory structure.
\SQL16 Contains 16-bit SQL links for use with Delphi Client/Server. Run SETUP.EXE (in the \SQL16\DISK1 subdirectory) to install SQL Links. (Delphi Client/Server only.)
\DELPHI16 Contains the last 16-bit release of Delphi (version 1.02). Run SETUP.EXE (in the \DELPHI16\INSTALL subdirectory) to install.
DEMO APPLICATIONS
Sample programs, including the ones listed below, are Installed with Delphi in the Delphi 3\Demos\... directory. To build these demos, compile the appropriate .DPR file. With client/server applications, be sure to build and run the server program before building the client. DelCtrls (in ...\ActiveX\Delctrls) includes standard Delphi components in an ActiveX control.
PBag (in ...\ActiveX\PropBag) implements the IPersistPropertyBag interface in an ActiveX control, allowing the control´s properties to be set through HTML tags. TRegSvr (in ...\ActiveX\Tregsvr) is a utility that registers ActiveX servers and type libraries. Webbrows (in ...\Coolstuf) uses the new TToolBar, TCoolBar, and TAnimate components in a Web browser. (Another Web browser, also called Webbrows, is in ...\Internet\Html.) HTTPDemo (in ...\Internet\HTTP) implements a web browser that retrieves the contents of a document from an HTTP server. EmpEdit (in ...\Midas\EmpEdit) uses TClientDataSet to create an editable employee table. The client application is in EMPEDIT.DPR and the server application is in SERVER.DPR. Project Manager (in ...\Midas\Mstrdtl) uses TClientDataSet and TProvider in a master/detail application. The projects in ...\Midas\SetParam illustrate the IProvider SetParams method. The projects in ...\Midas\Adhoc perform ad hoc queries using the provider´s OnDataRequest event. ...\Midas\USQLProv shows a custom TProvider component that implements business rules. ...\Midas\ActiveFM contains an ActiveForm that uses client datasets. Ftp (in ...\Internet\Ftp) is a File Transfer Protocol component that displays and manipulates files on an FTP server. WebServ (in ...\Webserv) is an ISAPI Web-server database application that uses the new Internet components. The first Web page shows a list of customers and company names, with hypertext links to each company´s Web page. NNTPDemo (in ...\Internet\Nntp) is a Usenet newsgroup browser. SimpMail (in ...\Internet\Simpmail) is an SMTP/POP mail client. Chat (in ...\Internet\Chat) is an Internet Chat application that uses the Client and Server socket components. DChat (in ...\Internet\Tcp) is a ´talk´ program that uses the TCP component to transfer text from one computer to another. RichEdit (in ...\Richedit) demonstrates the TRichEdit control. ...\DEMOS\DB contains additional database sample projects. Data used by these examples is in ...\DEMOS\DATA. ...\DEMOS\DOC contains sample projects from the printed documentation. ...\DEMOS\DATA contains data used by sample programs. INTRABUILDER TRIAL
The Delphi CD includes a free 30-day trial edition of Borland´s IntraBuilder. IntraBuilder is a visual JavaScript toolset that has everything you need to build and maintain live, data-driven Web applications and run them on your Web server. To view a self-running demo, or to install the trial version of IntraBuilder, run SETUP.EXE in the \TRIALS\INTRABLD directory of the Delphi CD.
For more information about IntraBuilder, see http://www.borland.com/intrabuilder/.
C++BUILDER TRIAL
The Delphi CD includes a trial edition of C++Builder, Borland´s rapid application development tool for C++ programming. To install the trial version of C++Builder, run SETUP.EXE in the \TRIALS\CBUILDER\SETUP directory of the Delphi CD.
For more information about C++Builder, see http://www.borland.com/bcppbuilder/
DOCUMENTATION UPDATES
VCL documentation and online Help
---------------------------------
The VCL reference material in the online Help is more up to date than the printed version. The following methods are documented only online:
TApplication.NormalizeAllTopMosts TCustomForm.WantChildKey (overridden in TActiveForm) TOleContainer.SaveAsDocument
The correct syntax for the TApplication.MessageBox method is in the online Help. Help entries for the TTable, TImage, and TBDEDataSet objects, among others, have also been revised.
Due to limitations in the WinHelp compiler, Windows API Help topics do not appear in the Delphi Help index. However, these topics are available from the Delphi IDE´s context-sensitive Help system; if you select a Windows API function in the Code editor and press F1, the appropriate Windows Help topic will appear. To see an index of Windows API Help topics, access the Windows API Help directly. The easiest way to do this is to add a button to the speedbar: Right-click on the speedbar and select Properties to open the Speedbar editor; select Help from the Categories list and drag the Windows API Help icon from the Commands list to your speedbar; then close the Speedbar editor.
Components on the Win 3.1 palette page are not linked to the context-sensitive online Help system. For documentation on these legacy components, refer to the DELPHI.HLP file located in \Delphi16\Runimage\Delphi\Bin on your Delphi CD.
Two components on the ActiveX palette page are not linked to the context-sensitive online Help system. For documentation on the VtChart control, see Delphi 3\OCX\Vci\Impress\Vcfi.hlp. For documentation on the Graph Custom Control, see Delphi 3\OCX\Pinnacle\Graph.hlp.
Some database example programs contain hard-coded directory paths. To make these examples compile, you may need to change the directory paths.
Asian calendar eras
-------------------
RTL functions provide increased support for Asian calendar eras. Conversion functions like StrToDate and DateToStr now preserve information about eras.
COMCTL32
--------
Several of the components on the Win32 palette page function best with the latest version (4.70) of COMCTL32.DLL. TCoolBar and TDateTimePicker will not work at all unless version 4.70 or later is installed. In addition, the following properties require version 4.70:
TToolBar.DisabledImages
TToolBar.Flat
TToolBar.HotImages
TToolBar.Images
TTabControl.HotTrack
TTabControl.ScrollOpposite
TTabControl.TabPosition
TPageControl.HotTrack
TPageControl.ScrollOpposite
TPageControl.TabPosition
TListView.Checkboxes
TListView.HotTrack
TListView.GridLines
TListView.RowSelect
TListItem.Checked
The Min, Max, and Position properties of TProgressBar must fall within the range of 0 - 65535 if the installed version of COMCTL32.DLL is less than 4.70.
TRegistry
---------
Under Windows NT, TRegistry can now open and read from the registry even if the user does not have administrative rights.
TMIDASConnection
----------------
The MIDASCon unit, which implements the new TMIDASConnection component, is not contained in any of Delphi´s precompiled runtime packages. You can, however, compile a runtime package of your own that contains this unit.
OLEnterprise
------------
When you run OLEnterprise at design time, the Business Object Broker may connect repeatedly to the same middle-tier server. To test dynamic load balancing, shut down the Delphi IDE and run your application independently.
Free-threading COM servers
--------------------------
To create a free-threading COM server, call CoInitializeEx in the Initialization section of a unit, and list this unit first in your project´s Uses clause. Make sure that the unit does not use ComObj (or any unit that uses ComObj).
IOleCommandTarget
-----------------
The IOleCommandTarget interface now takes PGUID parameters, rather than const TGUID:
IOleCommandTarget = interface(IUnknown) [´{b722bccb-4e68-101b-a2bc-00aa00404770}´] function QueryStatus(CmdGroup: PGUID; cCmds: Cardinal; prgCmds: POleCmd; CmdText: POleCmdText): HResult; stdcall; function Exec(CmdGroup: PGUID; nCmdID, nCmdexecopt: DWORD; const vaIn: OleVariant; var vaOut: OleVariant): HResult; stdcall; end;
This allows IOleCommandTarget to access default standard OLE commands such as PRINT and SAVE. (These commands require that nil be the first parameter passed to the IOleCommandTarget method, but nil cannot be passed as a const TGUID parameter.) Any code that uses IOleCommandTarget should be recompiled. Code that calls the IOleCommandTarget methods must be changed to pass the address of the GUID constant or variable, instead of passing the GUID itself.
ActiveX and Remote Dataset distribution
---------------------------------------
If you deploy an application or library that (a) uses the StdVCL unit and the IStrings, IProvider, or IDataBroker interface, or (b) uses the Delphi font, color, strings, or picture property pages, you must also deploy the Borland standard VCL type library. This library comes in two forms: the STDVCL32.DLL library, and a stand-alone type library called STDVCL32.TLB. Both of these files are in your Windows\System directory. Applications and libraries that use the Delphi property pages must deploy STDVCL32.DLL, but applications and libraries that employ only the interfaces listed above may instead deploy STDVCL32.TLB. Once installed on the destination machine, STDVCL32.DLL or STDVCL32.TLB must be registered in the system registry. (The TRegSvr demo application provides an example of how to register DLL and TLB files.)
Win32 shell extensions
----------------------
Win32 shell extensions require that the threading model for the extension object be set to ´Apartment´ in the system registry. Since TComObjectFactory.UpdateRegistry doesn´t make this entry automatically, you can do it manually by inserting the Value Name ´ThreadingModel´ with the Value ´Apartment´ under the CLSID key for your control in the registry. You can also override TComObjectFactory.UpdateRegistry to do this work for you; the following example code is for a Copy Hook shell extension:
procedure TCopyHookFactory.UpdateRegistry(Register: Boolean);
var
ClsID: string;
begin
ClsID := GUIDToString(ClassID);
inherited UpdateRegistry(Register);
if Register then
begin
CreateRegKey(´CLSID\´ + ClsID, ´ThreadingModel´, ´Apartment´);
CreateRegKey(´directory\shellex\CopyHookHandlers\´ + ClassName,
´´, ClsID);
end
else
DeleteRegKey(´directory\shellex\CopyHookHandlers\´ + ClassName);
end;
Using OpenGL
------------
Applications or libraries that use the OpenGL graphics libraries must ensure that the 8087 control word is set to mask Overflow, Zero Divide, and Invalid Operation exceptions. This is done automatically in the OPENGL unit, but if your application does not use the OPENGL unit (for example, if you are using an ActiveX control that employs OpenGL), you can do this by including the following line in the initialization code of a unit:
Set8087CW($133F);
InterBase ODBC Driver
---------------------
All versions of InterBase now include an ODBC 2.50 driver which is installed with the software.
Borland Database Engine
-----------------------
A Driver Development Kit is available for the BDE. Contact Developer Relations at Borland for details.
SNoTableName and other constants have been moved to the BDEConst unit.
IDAPI functions such as DbiQExecProcDirect and DbiOpenSPParamList now support Access named queries, which the BDE treats as stored procedures.
You can now set the Access SystemDB (workgroup information file) on a per-database basis using the BDE Administrator.
The Access driver now supports referential integrity.
To switch a cursor´s Access locking protocol between pessimistic and optimistic, toggle the Boolean curPESSIMISTICLOCKS property with DbiSetProp.
If you use the Oracle 7.2 or Oracle 7.3 client drivers, open the BDE Administrator, select the Configuration page, and navigate to Configuration/Drivers/Native/ORACLE. Then set VENDOR INIT to ORA72.DLL or ORA73.DLL. Stored procedures that return a result set are supported only for Oracle 7.3.
Using the BDE in ActiveX Controls
---------------------------------
To use the BDE in an ActiveX control, deploy the BDEINST.CAB file. For details, see BDEINST.TXT (in the root directory on the Delphi CD).
Using JPEG Images
-----------------
To use JPEG images at design time, choose Component | Install Component, create a new package, select JPEG as the Unit File Name, and install the package. To use JPEGs in an application at runtime, include the JPEG unit in your unit´s ´uses´ clause.
VCL Help Files
--------------
The VCL Help file (VCL3.HLP) uses another file called VCL3JUMP.HLP to provide context-sensitive jump support. Do not delete this file. If you accidentally delete it, you´ll have to restore it from the Delphi CD.
Overriding Resource-Module Localization
---------------------------------------
At start-up, applications typically check the locale of the system and look for a resource module that matches
the language and country. If you want your application to use a different resource module from the one indicated, you can set an override in the registry: Under the HKEY_Current_User\Software\Borland\Delphi\Locales key, add your application´s path and filename as a string value and set the data value to the extension of your resource modules; at startup, your application will look for resource modules with this extension before using the system locale. For more information, see ´Using Resource Modules´ under the ´Localizing Resources´ Help topic.
Code Signing
------------
To use Delphi´s code-signing features, you must have Internet Explorer 3.02 with the Authenticode 2.0 update. Both of these products are available from the Delphi Setup Launcher. Code-signing options are not available under Windows NT 3.51.
KNOWN PROBLEMS
Installation and Un-installation
--------------------------------
Existing IDAPI32.CFG alias information is not changed by the Delphi 3 installation. Therefore it may be necessary to change the path in the DefaultDD alias to the Delphi 3 data dictionary.
Un-installing Delphi 2 or the C++Builder trial version can remove some Delphi 3 settings and delete components from the palette. We recommend reinstalling Delphi 3 after un-installation of Delphi 2 or C++Builder.
The NetManage Internet Control Pack installed with Delphi is also shipped with other applications, including Visual Basic and PowerBuilder. These components may be unregistered in the process of un-installing another product. If this happens, reinstall Delphi.
After installing the C++Builder trial version, you may need to reset some alias information in the default IDAPI32.CFG. Specifically, the SERVER NAME for the IBLOCAL alias should point to C:\Program Files\Borland\Delphi 3\Demos\Data\EMPLOYEE.GDB. It´s a good idea to back up your IDAPI32.CFG before installing C++Builder.
Integrated Development Environment and VCL
------------------------------------------
TToolButton components don´t resize properly when images in the TToolBar´s ImageList property are modified. To work around this problem, remove images from the ImageList before modifying them; then replace them in the ImageList.
Due to a problem in Microsoft´s COMCTL32.DLL, the Arrange method in TListView does not function. This makes it difficult to clean up the list´s alignment when ViewStyle is vsIcon or vsSmallIcon, but otherwise does not affect the behavior of the component.
Use check boxes in TListView only when ViewStyle is setto vsList or vsReport.
The TLabel.ParentFont property is not used under Windows NT 4.0.
The fsStayOnTop setting for TForm.FormStyle does not function correctly when one fsStayOnTop form launches another. In this case, neither form will consistently remain on top.
Due to an operating-system bug, the TImageList.ResourceLoad method does not load Icon or Cursor files.
If you set TOpenDialog.AllowMultiSelect to True under Windows NT 4.0, a maximum of 20 files are returned. This bug is fixed in Service Pack 2 (available from Microsoft).
Database
--------
The Database Desktop does not display automatically created aliases for ODBC datasources. Always use static, manually created aliases with the ODBC driver.
Due to a known bug in Microsoft´s ODBC 3.4, connecting to a database twice with this driver can cause Delphi to shut down. This problem is fixed in ODBC 3.5.
The BDE no longer supports DbiUseIdleTime. Use DbiSaveChanges instead.
Local SQL queries require a table qualifier or alias name if the field name is in quotation marks. Examples:
(BAD) select name AS ´First Name´ from customer (OK) select name AS customer.´First Name´ from customer (OK) select name AS c.´First Name´ from customer c
When you use cached updates, changes made to indexed table fields are not reflected until the updates are applied.
If you use cached updates with master/detail tables, TQuery will re-execute the detail query each time the master record moves.
Constraint properties for a TField object on a client dataset are ignored.
The floating-point format required for custom constraints is inconsistent with international Windows settings. Always use periods (.) for decimals in custom constraints.
Output BLOB parameters are not supported in stored procedures.
Drag-and-drop copying of tables in the Database Explorer copies only metadata. Data copying will be supported in future releases.
Date-grouping on TClientDataSet is not supported in this version.
If an exception occurs inside the FormCreate event of a remote data module, the exception is displayed interactively. We recommend including a ´try ... except´ clause to handle exceptions in these events.
Save table-level constraints in the Dictionary in the Database Explorer, then read them from Delphi. (Use UpdateDataSet in DRIntF.INT.) Saving constraints from Delphi will be supported in future releases.
The Database Explorer does not support DB2 on the MVS or AS/400 platform.
When setting the BLOB SIZE parameter in the BDE configuration for the Oracle SQL Links driver, add one to the size to prevent data loss. For example, to retrieve 32k of data, set BLOB SIZE to 33 instead of 32.
To execute a parameterized query on an Oracle CHAR field, pad the parameter with blanks. For example, if a query includes where charfld = :c the statement could be modified to where charfld = rpad(:c,20,´ ´) There is no need to do this when using VARCHAR fields.
Informix users should have the latest client DLLs (e.g. ISQLT07C.DLL) from Informix. Otherwise you may get occasional access violations when using the SQL Explorer.
If you open a BLOB field on an Informix 7.2 server, using the Next method to move to another record causes
the server to crash. This is a known problem with the Informix 7.2 software.
The CT-Lib driver works with Sybase version 10.0.4 EBF7033 or higher.
If you use Sybase drivers with cached updates or client data sets, and you use a NUMERIC or DECIMAL field, make sure ENABLE BCD is set to True in the BDE Administrator.
If you use the Sybase CT-Lib driver, you can´t use the pbBlank parameter to check whether a text field is blank; the parameter always returns False. Also, blank BLOBs are always shown as not blank.
To see Oracle Sequences with the Database Explorer, set ENABLE BCD to False in the BDE Administrator.
Due to a problem in Microsoft SQL Server Service Pack 3, BLOB I/O does not work on tables that contain a unique index. When you execute a query under these circumstances, you´ll get a ´Memo Too Large´ error. A fix should be available from Microsoft soon; check Borland´s Web site for details.
Decision Support Components
---------------------------
If you use the Decision Query editor to access tables that are not owned by the login user, the generated SQL statements may by syntactically incorrect. Specifically, you may see
´OwnerName.TableName´
where the correct syntax is
´OwnerName´.´TableName´
If this happens, use the String List editor to edit the dialect part of the query manually in the TDecisionQuery.SQL property. (If you open the Decision Cube editor again, however, your edited query will be overwritten with the incorrect one.)
The same syntax problem causes the Decision Query to display an error message when you run the Decision Cube. The message tells you that the query fields cannot be automatically mapped to dimensions and summaries. If you get this error message, run the Decision Cube editor and provide the necessary field name,
grouping, and dimension type manually.
For more information about using these components, see the Documentation Updates section above.
A bug in Intersolve´s ODBC-Oracle driver causes it to interpret ´--´ as a comment to the end of the file (rather than to the end of the line). If you are using the Intersolve driver, move lines that start with ´--´ to the bottom of the query. Do not remove the lines altogether, since the Decision Query component uses them.
Access Driver
-------------
Some functionality is not yet implemented in this release. BCD (binary coded decimal) support is not available. Key-violation tables cannot be created with DbiAddIndex. (All other DbiAddIndex functionality is supported.) QBE, heterogeneous queries, and queries using the local SQL engine are not supported. In the SDK, DbiDoRestructure and DbiRegenIndex are not available.
The Access driver does not support DAO 3.5 (Access 97). If you upgrade Access 95 to Access 97, DAO 3.0 still resides on your machine, so the driver will function correctly. If you install Access 97 with no prior version of Access 95, the driver will not function.
Because DAO 3.0 (Access 95) is not thread-safe, all database functions must occur in the application´s primary thread.
MS Access does not support opening a table that has already been opened exclusively. Hence opening a table
when TTable.Exclusive is set to True prevents the user from opening that table again, even in same session.
Use a BLOB as a parameter in a query only if the BLOB data is less than 256 bytes.
When the Database Desktop copies an InterBase table to Access, the table and data are copied without indexes. If the table includes an index, you´ll see an ´invalid parameter´ error. Use the Data Pump for this purpose instead.
When borrowing a structure from a Paradox table, the Database Desktop does not copy primary indexes to the resultant Access table. Use the Data Pump for this purpose instead.
AUTOINCREMENT fields do not update correctly when records are added to a table that has at least one other field with a default value.
Internet
--------
In order for the BDE to access paradox or dBASE tables from a Web server application, the Web server must have appropriate access privileges for the disk drive where the table resides. Access privileges may depend on your Web server and how it is configured. See your Web server´s documentation for details.
ActiveX
-------
After generating an ActiveX control, do not change the type library interface from dual interface to dispinterface. The ActiveX Class Framework does not support inheritance from dispinterface.
Delphi-created ActiveX controls and ActiveForms have been tested for use with the following containers: Delphi 3, Delphi 2.0, Borland C++Builder, Visual Basic 4, Visual Basic 5, Access 95, Access 97, ActiveX Control Pad 1.0, Visual C++ 4.2, Visual C++ 5.0, Internet Explorer 3.01 and later, and FrontPage 2.0. There are known problems with ActiveX controls hosted in Microsoft Access 95. Please check the Borland Web site for the most up-to-date information on supported containers.
If you are using ActiveForm controls with Visual Basic 4, remove the OLEMISC_SIMPLEFRAME flag from the factory constructor at the bottom of the ActiveForm unit. Because of a known problem in VB4, ActiveForm and other simple-frame ActiveX controls do not receive event notifications (e.g., for OnClick events) when used in VB4 applications.
Because of a known problem in Visual FoxPro 5.0, Delphi-created ActiveX controls must override the ObjQueryInterface() function to return a pointer to the control´s primary dispatch interface when IDispatch is requested:
function TMyCtl.ObjQueryInterface(const IID: TGUID; out Obj):
Integer;
begin
if IsEqualGuid(IID, IDispatch) then
begin
IMyCtl(Obj) := Self as IMyCtl;
Result := S_OK;
end
else
Result := inherited ObjQueryInterface(IID, Obj);
end;
Some ActiveX controls (such as the IE Pop-up Window from Microsoft) create a window handle as part of their minimal construction, but fail to destroy the handle when the instance is released. Importing such ActiveX controls can crash the IDE.
Because of a known problem with Internet Explorer, arrow keys don´t work inside some ActiveX controls when they are first activated in IE. If you tab out of the control and then tab back into it, the arrow keys will function normally.
Several ActiveX download and security problems were fixed in version 3.02 of Internet Explorer. IE 3.02 is available on the Delphi CD (in the IE3 directory). To determine which version you currently have installed, check the IEXPLORE.EXE date stamp; ´3:02am´ means version 3.02.
To change the name of an ActiveForm, you must perform these three steps in the following order:
1. Use the Object Inspector to change the form´s name. 2. Use the Type Library editor to change the coclass name.
3. Use the Code editor to modify Class_xx in the factory create call (in the form´s initialization section). For example, if you´ve changed the name of the form from MyForm to YourForm, you would change the create call from
TActiveFormFactory.Create(ComServer, TActiveFormControl, TYourForm, Class_MyForm, 1, ´´, OLEMISC_SIMPLEFRAME or OLEMISC_ACTSLIKELABEL);
to
TActiveFormFactory.Create(ComServer, TActiveFormControl, TYourForm, Class_YourForm, 1, ´´, OLEMISC_SIMPLEFRAME or OLEMISC_ACTSLIKELABEL);
The Type Library editor cannot create a property of the type TSafeArray or a function that returns a TSafeArray. Use the OleVariant type instead.
QuickReports
------------
Due to limitations in the conversion process, some complex reports from Delphi 2 may not load properly.
Dynamically Loaded Libraries
----------------------------
Windows NT sometimes incorrectly unloads a library when another library that depends on it fails to load. This problem occurs only when libraries are loaded dynamically under the conditions described below. It affects Windows NT 3.51; Service Pack 2 fixes the bug for Windows NT 4.0.
The problem arises when a dynamically loaded library uses two other libraries, each of which in turn uses another library. Suppose, for example, that an application uses five DLLs that are loaded dynamically in the following order: DLL1, DLL2, DLL3, DLL4, DLL5. Suppose that the following dependencies hold among the DLLs:
DLL5 uses DLL4; DLL4 uses DLL3.
DLL5 uses DLL2; DLL2 uses DLL1.
Suppose the first three DLLs (DLL1-3) load successfully, but DLL4 calls an entry point in DLL3 that has been removed. In this case, DLL5 will naturally fail to load. If a second attempt is made to load the library, Windows will unload
DLL1 and the application program may crash.
This problem can affect installation of packages within the Delphi IDE; it does not affect deployed applications, where packages are statically loaded. If you are using Delphi under Windows NT 3.51, the best way to avoid the problem is to make sure all required packages are updated before you recompile or install components.
----------------------------------------------------------------
Unless otherwise noted, all materials provided in this release are Copyright 1983 - 1997 by Borland International.
----------------------------- END ------------------------------
When you are ready to continue with the setup click the next button or press the Enter Key.
Maxsoftware
Curtidas 0
Respostas
Max2006
31/07/2004
[color=red:92ae5939e5]Texto editado por Massuda.[/color:92ae5939e5]
Aqui tem oque a licença diz..., alguem pode me ajudar...?
GOSTEI 0