Watch, Follow, &
Connect with Us
Public Report
Report From: Kylix/Database/dbExpress/TSQLStoredProc    [ Add a report in this area ]  
Report #:  6490   Status: Reported
No SchemaName property in TSQLStoredProc
Project:  Kylix Build #:  4.186
Version:    3.0 Submitted By:   Ramcor Industries Senior Programmer
Report Type:  Minor failure / Design problem Date Reported:  11/25/2003 8:39:11 AM
Severity:    Commonly encountered problem Last Updated: 11/25/2003 8:40:13 AM
Platform:    Kylix Pascal IDE Internal Tracking #:  
Resolution: None  Resolved in Build: : None
Duplicate of:  None
Voting and Rating
Overall Rating: (1 Total Rating)
4.00 out of 5
Total Votes: None
Description
The SchemaName property does not exist in the
TSQLStoredProc, causing problems with porting and DB access.

I believe this also contributes to why the TSQLStoredProc does not list any stored procedures in it's drop down list because it can't resolve which schema to retrieve them from, or at least the DB2 calls don't reference it.
Steps to Reproduce:
In Kylix:

Drop a TSQLStoredProc on a DataModule you can clearly see the SchemaName does not exist as a property.

For Porting:

1) Drop a TSQLStoredProc on a DataModule in a CLX project in windows
2) Save the DataModule
3) Try to open the DataModule on a Linux machine running Kylix
Workarounds
For porting purposes, open the .xfm as text (In the Kylix IDE) before trying to open it as a form.
Manually remove all the 'SchemaName=' lines
Attachment
None
Comments

None

Server Response from: ETNACODE01