|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
||||||||||||||||
|
|||||||||||||||||
|
|||||||||||||||||
|
|||||||||||||||||
|
|||||||||||||||||
|
|
||||||||
|
|||||||||
|
|
|
Delphi DocumentationSupport |
|
 DELPHI DEVELOPER SUPPORT
Delphi 3 update and patch
Areas of concentration under: database
Area: database\bde Problem: Cannot open a DecisionQuery whose SQL text is based on a FoxPro Table. Attempting to do so produces a 'Higher table level required.' message. =========================== This actually happens with the standard Query component as well and only occurs if the query contains an aggregate. Fixed in BDE 4.01. Area: database\bde Problem: BDE Filters on queries of Oracle tables where the filter involves a BCD field (i.e. Oracle NUMBER(*) or NUMBER(32, 15) specifically) may include incorrect rows or exclude correct rows. Fixed in BDE 4.01 Area: database\bde Problem: Access database driver does not work with the redist. DAO 3.0. It requires installation of Access 95 Due to IDDAO32.DLL looking into a registry entry that is specific for Access95. Area: database\cached updates Problem: Updating a Key Violation causes an "At end of Table error." Area: database\constraints Problem: If a table is not in the current dictionary, the 'Read From Dictionary' Button on the Constraints Editor is not enabled. But once the table is imported, user expects it to be enabled. The only way for it to be enabled is to restart BDE. Area: database\core classes Problem: Creating a multifield descending index always results in an ascending index. Area: database\data access controls\tclientdataset Problem: Locate using PartialKey does not work on the Company field of the Customer table. Area: database\data access controls\tclientdataset Problem: At run-time, if Client Data Set data is streamed to a form, the last field of the last record is not correct. Assign local data in a CDS. Toggle between form/text view (Alt-F12) Last field of last record will be incorrect. Area: database\data access controls\tclientdataset Problem: Master-detail ClientDataSet using local data. If the detail has no records to display you get an error "No data packet or provider". Area: database\data access controls\tclientdataset Problem: TClientDataSet can incorrectly raise an exception in a Master/Detail relationship when the detail table has no records that match the master record. If working in a briefcase model or flat-file model with no Provider property set, an exception 'Missing data provider or data packet' is raised. Area: database\data access controls\tclientdataset Problem: Resolver does not work correctly on fields that contain a blank string as opposed to a NULL value. Area: database\data access controls\tclientdataset Problem: An invalid error message is generated when attempting to insert a record into the detail table of a master/detail relationship. Area: database\data access controls\tclientdataset Problem: When a ClientDataSet is a detail, FetchOnDemand should work as follows. If it is True, detail records are automatically retrieved. If it is False, the user retrieves the records. (GetNextPacket would work to retrieve the current set of details.) Area: database\data access controls\tclientdataset Problem: TClientDataSet fails to remove itself from TRemoteServer.ClientDataSets when destroyed. It is only removed from the list if the TClientDataSet.RemoteServer property is set to nil. This can lead to an Access Violation if enough (usually nine) TCDS components are used. Area: database\data access controls\tclientdataset Problem: Setting PacketRecords to 0 and FetchOnDemand to true results in a "Mismatch in DataPacket" error message when a CDS is opened. Area: database\data access controls\tdatabase Problem: If an old style Paradox alias (with only TYPE and PATH in the alias declaration) is used with TDatabase, when trying to set connected to true, an exception 'object is not found' is raised. This is because an empty string is being passed into the driver type parameter for DbiAddAlias. BTW: This type of alias worked in Delphi 2. Area: database\data access controls\tfield Problem: TBooleanField.GetAsString can cause an AV if the value returned from the server is -1. Area: database\data access controls\tparam\tparamlist\tparams Problem: [MSSQL Stored Procedures] The SubType of a Blob Input Parameter does not seem to be passed to the BDE correctly. Area: database\data access controls\tprovider Problem: When the OnGetData event is used with partial pickles, an exception is raised when the second datapacket is retrieved. Area: database\data access controls\tprovider Problem: TDispatchProvider needs to support ISupportErrorInfo. Otherwise exceptions are not propagated on the client machine correctly when using the dispinterface. Area: database\data access controls\tprovider Problem: When refreshing from a TProvider on an active TTable, it is possible to have data returned that does not reflect the current updates. Area: database\data access controls\tquery Problem: FoxPro driver : UPPER(), LOWER(), SUBSTRING() and TRIM() do not work in Local-SQL statements if the table is a FoxPro table. Returns error : Invalid Parameter. Area: database\data access controls\tquery Problem: FoxPro Driver : Aggregate functions do not work in SELECT statements. They return Error 'Higher table level required'. AVG, SUM, COUNT will result in the same error Area: database\data access controls\tquery Problem: FoxPro Driver : The EXTRACT Date function does not work in Local-SQL statements. For example : SELECT EXTRACT(YEAR FROM datefld) FROM ALLTYPES Error - "Invalid Parameter" Area: database\data access controls\tquery Problem: Dropping an index that does not exist returns error 'Index does not exist. Table : DBASE'. It should display the table name, not the table type. Area: database\data access controls\tquery Problem: Access Violation; if BDE is not present for any reason and you try to activate a TQuery that has CachedUpdates set to true. The correct error message gets displayed (error loading BDE..) if CachedUpdates is false. Also happens for TTable and TDecisionQuery. Area: database\data access controls\tremoteserver Problem: There is no way to access the properties or to close the socket server under NT 3.51. Area: database\data access controls\tremoteserver Problem: Resourced string(s) in TP\DB\Scktmain.pas* and TP\DB\Midascon.pas need to be moved into a separate unit. Area: database\data access controls\tremoteserver Problem: [Socket Server] Cannot set port or thread cache values greater than 999. Error message "xxx is not a valid integer value." when you click on OK. Area: database\data access controls\tremoteserver Problem: Socket Server: The pickletters for "Listen on port" and "Thread cache size" don't work and the port number SpinEdit can't "scroll" to values greater than 100 (yet the default value is 211). Area: database\data access controls\tremoteserver Problem: Double clicking on the socket server's taskbar icon when the properties dialog is already being displayed generates the error "Cannot make a visible window modal". Area: database\data access controls\tsession Problem: TSession.IsAlias doesn't work with accented characters. Area: database\data access controls\ttable Problem: FoxPro Driver : FindKey and Locate methods go to the wrong record when a range is in effect. For example, find key of 'D' goes to 'H'. Area: database\data access controls\ttable Problem: Using a master / detail relationship with cached updates, occasionally error 'at end of table' appears. If two records are added to the master table and then one record is added to the second master record (leaving no detail records to the first master record), then applying updates, 'at end of table' occurs on the detail apply. Area: database\data access controls\ttable Problem: FoxPro Driver : The IndexFiles dialog does not display FoxPro CDX files as a file type in the Add... dialog box. Instead MDX file type is displayed, but these are not supported in FoxPro tables. Area: database\data access controls\ttable Problem: If an application continually changes a filter on a table, memory usage for the application continues to increase until an error 'Capability not supported' or 'Insufficient memory for operation' error occurs. Area: database\data aware controls\tdbedit Problem: DBEdit control's MaxLength property not getting set to the size of an associated string field as it did in Delphi 1 & 2. [Fixed by setting MaxLength of the DBEdit to the underlying fields size if the value is currently zero (the default), and the associated field is a string field. If the developer has set the MaxLength property directly to any value other than 0, then that value will be used instead of the size of the field.] Area: database\data aware controls\tdblookupcombobox Problem: TDBLookupCombobox doesn't display the lookup text when printed with Form.Print. Area: database\decision cube controls\tdecisioncube Problem: TDecisionCube rebuilds twice when changing the initial value for a dimension. It should only rebuild once. Area: database\decision cube controls\tdecisioncube Problem: Date binding on a dataset causes a Fatal Error in cache: 180. It looks like this ONLY happens with datasets and date ranges, although once it happens, it continues to occur even when the query is modified so that no dates are in the query. Area: database\decision cube controls\tdecisiongrid Problem: TDecicionGrid Dimension layout on a grid is not being preserved when going from design to run mode, making design time layout a useless procedure. Area: database\decision cube controls\tdecisiongrid Problem: It is possible to create multiple DecisionGrid Dimension property editors. Area: database\decision cube controls\tdecisionquery Problem: Tables fail to get listed when a database object is used to specify the alias/location of the tables. Note: same object works for TTable Area: database\decision cube controls\tdecisionsource Problem: Deleting a TDecisionSource component causes AV in DSS30.DLL Area: database\decision cube controls\tdecisionsource Problem: Setting ControlType always behaves as though set to xtCheck. Area: database\fields editor Problem: Field components created in the Fields Editor can easily have incorrect values for the Origin property. Area: database\form expert Problem: Creating a Master /detail with queries on Access and linking on an autoinc field generates an error. Area: database\sql explorer Problem: The DBExplorer displays the wrong index information. The fields that are displayed as information on what field the index is based on are wrong. Area: database\sql explorer Problem: Attempting to order a dBASE/Fox table by a descending index in DB Explorer yields 'DBTable has no index for fields 'xxx'' Area: database\sql explorer Problem: RI on MSACCESS tables: Get error message "Object < name > .DB does not exist." when trying to open the Referential Constraints branch. Area: database\sql explorer Problem: In Database Explorer, the Oracle TNSNAMES.ORA server name list generator doesn't look at the Oracle TNS_ADMIN key to find the TNSNAMES.ORA...It only looks in the default location, under the oracle home directory tree. Area: database\sql explorer Problem: The the buttons on SQL Script Error dialog box in SQL Explorer have an inconsistent tab order. Area: database\sql explorer Problem: SQL Explorer uses non-standard keystroke to switch focus to panels. The F12 function key is used, whereas the F6 function key is the Microsoft recommended key for switching focus to the next panel. Area: database\sql monitor Problem:
NOTE: These listings are for informational use only. It is not intended for use when calling Inprise's Developer Support Department.
|
|
||
|
|
|
|||
|
|||||
|
|
||||
 |
|||||
|
|||||
| Made in Borland® Copyright© 1994-2003 Borland Software Corporation. All rights reserved. Report Piracy, Legal Notices, Privacy Policy Last Modified Thursday, 22-Mar-2001 18:57:02 EST |
|||||
