Add SSRS 2000 Report Designer to VS 2005?

Is it possible to add the SSRS 2000 Report Designer to VS 2005 or is the
only choice to use it with VS 2003? I see that some people have sucessfully
done side by side implementations but we have already migrated our code to
.NET 2.0 and don't need VS 2003 around for other development work other than
possible SSRS reports if we can't use the 2000 designer in the VS 2005 IDE.
Thank you in advance.Nope. You need both. RS 2000 uses 1.1 Framework and the VS 2003 designers.
It is tightly integrated with it. RS 2005 uses 2.0 framework and is tightly
integrated with VS 2005.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Jim" <jim@.nospam.com> wrote in message
news:eDIwnuF7FHA.3588@.TK2MSFTNGP15.phx.gbl...
> Is it possible to add the SSRS 2000 Report Designer to VS 2005 or is the
> only choice to use it with VS 2003? I see that some people have
> sucessfully done side by side implementations but we have already migrated
> our code to .NET 2.0 and don't need VS 2003 around for other development
> work other than possible SSRS reports if we can't use the 2000 designer in
> the VS 2005 IDE.
> Thank you in advance.
>

Add mode problem on field setup with Foreign Key

Hello,

I have two tables (one-to-many relation) related thru a common key. I have setup the Relation using the Database Designer. The Form is populated using Drag-and-drop which automatically adds the BindingSource, TableAdapter, and Binding Navigator. The Relation works great in the change mode, and life is good.

In the Add mode the field setup with the Foreign Key is not automatically populated as it is in Change mode. The field can be updated manually, but that defeats the purpose of setting up the Relation.

Any ideas how to fix this?

I know this is difficult to visualize without seeing it.

Thank you for any ideas,

Tom

The detail grid (or some other graphic control) should be linked to the relation itself not the underlying detail database table. Master's PK should be FK in Detail.

See here on MSDN2:

One BindingSource is bound to the parent Customers table in the data set. This data is displayed in the master DataGridView control. The other BindingSource is bound to the first data connector. The DataMember property of the second BindingSource is set to the DataRelation name. This causes the associated detail DataGridView control to display the rows of the child Orders table that correspond to the current row in the master DataGridView control.