C# shopping basket, trying to remove an item...

You see the way that I bring back the info for all items. Create something similar to just bring back the items you want..

So i created a link table

Id, SpecId, ProductId
int, int, int

What this is you can have say 1 product that falls into many specs and this allows you to set that up.

So when you have your Id of your spec you get the products that are associated with that, similar to get all products execpt you get only the ones that are belonging to that spec.

Bind that list of products to a repeater similar to how i have done it in Catalog.aspx and then you are laughing because everything else works the same once you have the basic list.

Originally I was going to put that in the same page but I wanted to show how its done first so people can see it working in its own way.

You will need to set the Primary Key on Products to the ID field before running this script

SET ANSI_NULLS ON
GO
SET QUOTED_IDENTIFIER ON
GO
CREATE TABLE [dbo].[SpecProduct](
	[ID] [int] IDENTITY(1,1) NOT NULL,
	[SpecID] [int] NOT NULL,
	[ProductID] [int] NOT NULL
) ON [PRIMARY]
GO
/****** Object:  StoredProcedure [dbo].[usp_select_specProduct]    Script Date: 05/08/2009 12:38:59 ******/
SET ANSI_NULLS ON
GO
SET QUOTED_IDENTIFIER ON
GO
CREATE PROCEDURE [dbo].[usp_select_specProduct]
(
@SpecID INT
)
AS
SELECT Product.Id, Product.Name, Product.Description, Product.Cost
FROM Product INNER JOIN SpecProduct ON Product.Id = SpecProduct.ProductID
WHERE SpecProduct.SpecID = @SpecID
GO
/****** Object:  ForeignKey [FK_SpecProduct_Product]    Script Date: 05/08/2009 12:39:00 ******/
ALTER TABLE [dbo].[SpecProduct]  WITH CHECK ADD  CONSTRAINT [FK_SpecProduct_Product] FOREIGN KEY([ProductID])
REFERENCES [dbo].[Product] ([Id])
GO
ALTER TABLE [dbo].[SpecProduct] CHECK CONSTRAINT [FK_SpecProduct_Product]
GO
/****** Object:  ForeignKey [FK_SpecProduct_Spec]    Script Date: 05/08/2009 12:39:00 ******/
ALTER TABLE [dbo].[SpecProduct]  WITH CHECK ADD  CONSTRAINT [FK_SpecProduct_Spec] FOREIGN KEY([SpecID])
REFERENCES [dbo].[Spec] ([ID])
GO
ALTER TABLE [dbo].[SpecProduct] CHECK CONSTRAINT [FK_SpecProduct_Spec]
GO

You will then need to make sure that all your products have a spec (and its just numbers)

Next thing is you will need to create a method in the data access layer that accepts an int and returns a list of products

Same in the business layer

Once you have that, you can copy the repeater and its code to get yourself up and running

Same same, just remember to add the keys and also change the stored proc...

make sure you look at how tho join is done as i did it in previous script. I thought i included a stored proc as well. The event idea is simply that. You tell the said that you are doing something ie an event. Most things are events such as the index changing or a button press or a post back for example. I will be offline tho for the next few days but i will probably have all this written for another blog post by monday

see thats the thing you dont need a button you just need to bind the data to a repeater just like how catalog does it. In fact just copy out the repeater and related events to the dropdown file and databind it in the selectedindex changed event of the spec dropdown using the selected value in spec to get the correct products. Because the repeater is set up to add to the shopping cart and its in session it will carry across pages easily as long as you add cart items to it. Make sense

Ehhh sounds like you copied in namespaces and everything

Copy in the repeater first from the source of Catalog.aspx

then copy in the in the bits such as RepeaterEvent

then add the Event handler in the init part...

Ok

I just finished adding the Dropdowns and all that to the Catalog page and showing how to bind the information correctly etc.

I will be putting that up later today if I get a chance along with a post explaining how it all works

In the one I have it works fine, I just changed it now so that the first 2 specs have a subcatid of 1 and they work fine.

Did you use my particular code or your own?

Also the data for all the products is in the script, so you dont required the adventureworks database

When you run the page, view the source of it and see what values are being applied to the dropdown Specialisation. If all the value are 0, its a problem in the stored proc to get all the specialisations