Watch, Follow, &
Connect with Us
Public Report
Report From: Delphi-BCB/IDE/Project Management/Project Options    [ Add a report in this area ]  
Report #:  104322   Status: Closed
TSQLConnection triggers Access Violation in MDI Application when starting
Project:  C++Builder Build #:  16.0.4429.46931
Version:    16.4 Submitted By:   Bob grove
Report Type:  Crash / Data loss / Total failure Date Reported:  3/21/2012 5:42:02 AM
Severity:    Critical / Show Stopper Last Updated: 9/8/2013 8:17:04 PM
Platform:    All versions Internal Tracking #:   26932
Resolution: Fixed (Resolution Comments) Resolved in Build: : XE4 Update1
Duplicate of:  None
Voting and Rating
Overall Rating: No Ratings Yet
0.00 out of 5
Total Votes: None
Description
Placing a TSQLConnection on an MDI Application triggers a $C0000005 Access Violation when starting.

Added by Sysop
<<<<<<<<
Please see comments of QC for more information.
>>>>>>>>
Steps to Reproduce:
1) Create new MDI Application - File | New | Other | C++Builder | MDI Application

2) Select dbExpress TSQLConnection object from Tool Palette and place on any unit in project

3) Set TSQLConnection properties - Driver = Interbase, ConnectionName = IBCONNECTION, Connected = TRUE

4) Press F9 to compile and run

5) Application causes $C0000005 Access Violation
Workarounds
None found.  Needs resolution.
Attachment
None
Comments

Tomohiro Takahashi at 3/21/2012 1:28:41 PM -
What version(and Build no) of C++Builder do you use, for example C++Builder XE2 Update 4(16.0.4429.46931)?

and, could you please attach sample project to reproduce your issue by using Windows Native QC Client?
the standalone client comes with C++Builder.

Bob grove at 3/22/2012 5:55:04 AM -
Embarcadero® C++Builder® XE2 Version 16.0.4276.44006
Installed Updates: RAD Studio XE2 Delphi and C++ Builder Update 1

I'm not familiar with Windows Native QC Client.  Please provide usage instructions and I will upload project; or can email zipped project if preferred.

Tomohiro Takahashi at 3/22/2012 1:13:35 PM -
Does your issue still occur with C++Builder XE2 Update 4(16.0.4429.46931)?

> ... in MDI Application
and, does your issue occurs only when building MDI project?
What about simple VCL form application?

>  Please provide usage instructions ...
1. please download QC client from
  http://qc.codegear.com/qualitycentral.zip
2. open your existing report
3. activate [Attachments] tab
4. show popup menu
5. select [Add Attachment...]
6. select a .zip file

Bob grove at 3/24/2012 3:00:41 PM -
Yes, error still occurs with Update 4.  I've isolated the error to the following line in the mdiapp.cproj generated by File | New | Other | MDI Application.

<PackageImports>rtl.bpi;vcl.bpi;vclx.bpi;$(PackageImports)</PackageImports>

If the above is replaced by the following line, Access Violation goes away.



<PackageImports>IPIndyImpl;bindcompfmx;fmx;rtl;dbrtl;IndySystem;DbxClientDriver;bindcomp;inetdb;DBXInterBaseDriver;DataSnapCommon;DataSnapClient;DataSnapServer;DataSnapProviderClient;xmlrtl;DbxCommonDriver;IndyProtocols;DBXMySQLDriver;dbxcds;soaprtl;bindengine;DBXOracleDriver;dsnap;DBXInformixDriver;IndyCore;fmxase;DBXFirebirdDriver;inet;fmxobj;inetdbxpress;DBXSybaseASADriver;fmxdae;dbexpress;DataSnapIndy10ServerTransport;$(PackageImports)</PackageImports>

Tomohiro Takahashi at 3/25/2012 12:53:14 PM -
As another possible workaround, please try to turn off 'Link with runtime packages' in your MDI project option.

Tomohiro Takahashi at 4/3/2012 7:27:49 PM -
This report was opened with valid Internal Tracking Number.
Thanks.

Tomohiro Takahashi at 7/15/2013 6:03:47 PM -
Does this issue still occur with C++Builder XE4 Update1?

Tomohiro Takahashi at 9/8/2013 8:18:50 PM -
This issue should be fixed(or not be reproduced) with C++Builder XE4 Update1 at least.

Maggie Cao at 9/8/2013 5:51:44 PM -
This problem can be easily re-produced on C++Builder XE4 Update1. Please contact with me if you need more details. Please also let me know how soon this issue can be solved.

Tomohiro Takahashi at 9/8/2013 6:14:44 PM -
What RDBMS(and version) do you use?

Server Response from: ETNACODE01