Search

configure SQLdatasource wizard does not include schema name causing error by GeneWald

Closed
as Won't Fix Help for as Won't Fix

1
Sign in to vote
0
Sign in to vote
Sign in
to vote
Type: Bug
ID: 111150
Opened: 12/26/2005 11:08:58 AM
Access Restriction: Public
Primary Feedback Item: 115102
0
Workaround(s)
1
User(s) can reproduce this bug
Using the Configure SQLDataSource wizard to modify the selected columns produces an sql statement that does not include the schema qualifier which results in a statement that produces an error when test is selected.
Details (expand)
Product Language
English
Version
Visual Studio 2005
Category
Windows Forms and Controls
Operating System
Windows XP Professional
Operating System Language
US English
Steps to Reproduce
Place an SqlDataSource on a web form. Select Configure Data Source from the tasks context menu. Select a datasource that contains one or more schemas other than the default (blank) schema. Click next to specify the select statement. Select the radio button to Specify columns from a table or view. Select a table that exists in a schema (note that the schema is not identified in the selection list). As you pick columns to return in the select statement, note that the statement being built does not include the schema qualifier. After selecting columns, click next to display the test screen. Click on Test button.
Actual Results
Error indicating that the table name is an invalid object name. This is because the table name is not qualified with the schema name.
Expected Results
No error.
File Attachments
1 attachments
Sign in to post a comment.
Posted by Microsoft on 12/26/2005 at 9:18 PM
Thank you for your feedback. We are investigating this issue.

Thank you, VS2005 Product Team.
Posted by Microsoft on 1/25/2006 at 12:14 AM
Thanks for reporting the issue. This is a known issue and will be looked at for fixing in the future.

Thanks,
The Web Platform and Tools Team
Posted by Microsoft on 1/25/2006 at 12:30 AM
Thanks for reporting the issue. This is a known issue and will be looked at for fixing in the future.

Thanks,
The Web Platform and Tools Team