QualityCentral

Public Report

Report From: Delphi-BCB/AddOn/Interbase components [ Add a report in this area ]

Report #: 91355

Status: Open

XE IBSqlMonitor failure

Project: Delphi

Build #: Del XE, IB XE

Version: 15.0

Submitted By: Patrick Moloney

Report Type: Basic functionality failure

Date Reported: 2/6/2011 8:31:22 AM

Severity: Commonly encountered problem

Last Updated: 3/20/2012 2:24:39 AM

Platform: All platforms

Internal Tracking #: 281823

Resolution: None (Resolution Comments)

Resolved in Build: : None

Duplicate of: None

Voting and Rating

Overall Rating: No Ratings Yet

0.00 out of 5

Total Votes: 6

Description

The output of IBSqlMonitor is degraded in Delphi XE and IB Xe. Although basically working as it did in previous versions, output statements are truncated and run together. User data is missing in the output, an appears to have more parameter names than parameter values.

Added by Sysop
<<<<<<<<<
Until recently upgrading both Delphi and Interbase to XE I was using Delphi 7 and IB 2007, which I have running on another machine. Running the same test in both, the output looks much better in D7, while in XE the output is run together with missing and broken words.
>>>>>>>>>

Steps to Reproduce:

A new IBSqlMonitor Delphi project application was built as described in the Interbase Developer manual, appendix. This functioned immediately without basic problem.

This IBSqlMonitor application was used to monitor a Delphi/IBX for which displays records selected by a stored procedure. The table includes only 3 short records and the stored procedure is basically "Select * from table". The application being tested worked perfectly with all 3 records displayed in a listbox. However, the information provided by IBSqlMonitor was not very helpful.

The IbSqlMonitor output displayed only the Identifier of the 3rd record and no Description fields (Identifier, Description).
Statements in the output contained broken words and truncated sentences, often run together.

An additional test of a related maintenance form which displays 1 record for editting (Identifier and Description), showed even less results and was useless.

IBSqlMonitor has been difficult in previous versions but it appears broken in this situation.

The environment is a new Windows 7 Dell computer, Delphi Xe and InterBase XE Developer version.
The database in use was freshly built from DDL with a default character set of UTF8. Only select application system tables are populated, which was accomplished from DML files. The application is working properly, but IBSQLMonitor does not appear to be working as previous.

Workarounds

None

Attachment

None

Comments

Tomohiro Takahashi at 2/6/2011 7:50:07 PM -

> ... basically working as it did in previous versions,
What previous version of Delphi have you used?
And, what previous version of InterBase have you used?

Is your issue similar to(related to) QC#73248,74144, or 85010?
Could you please attach sample project(including sample database file) to confirm your issue?

Patrick Moloney at 2/7/2011 1:28:48 PM -

Until recently upgrading both Delphi and Interbase to XE I was using Delphi 7 and IB 2007, which I have running on another machine. Running the same test in both, the output looks much better in D7, while in XE the output is run together with missing and broken words.

The problem may not be in the IBSqlMonitor component but in the TMemo that displays the data. I prepared a small project as described for IBSqlMonitor at the end of the Developer manual to use IBSqlMonitor.

Just now I generated an IBSqlMonitor Test, copied the output, and pasted it into a text editor so I could attach it to this comment. Although it was somewhat garbled in the Delphi TMemo, it looked good in the text editor, which seemed to "fix" what I had copied. Perhaps the instructions for how to use IBSqlMonitor need to be revised, or there may be an incompatibility with TMemo.

Running the same test in Delphi 7 and IB2007 showed well formatted output in the Tmemo.

The "related" QC reports you mention look like they refer to different components. #73248 refers to TSqlMonitor, not TIBSqlMonitor, which does not seem to be related. Unfortunately, it looks like at least one of the other reports was closed out based on that first report (referring to a different component) being fixed. None of these reports look like the same problem, although they could be related.

I believe this problem can be repeated with any sample database and the IBSqlMonitor application as described in the documentation. The resulting report should be poorly formatted, contain broken and missing words.

Developer Tools

Database Tools