I have an Access table made up of various "ingredients". From this table by selecting various "ingredients" i want to create another table (or just create new entries in another table) of "recipe" names and store this table in the same or another Access file.
I am connecting to the ingredients table and filling a dataset with it, through a DataAdapter, then i'm displaying the contents in a DataGrid in which i've added a CheckBox column. I'm planning to use this checkbox column to select the ingredients for the various recipes.
I know i can link such tables by using a column in the ingredients table which will specify a recipe name for each ingredient. However my problem is that some of the recipes will share the same ingredients so i can't use such a column to create the relationship.
I think i posted this one in the wrong Forum, so i posted it in the SQL/ADO/ADO.NET forum and got my answer thanks to ToddHileHoffer.
Will use three tables, one for the "recipes", one for the "ingredients" and one for the "recipeingredients" and the relation will be between the recipes table and the recipeingredients table. Just in case anyone else was wandering.
I'm trying to create a class that I don't want anyone to be able to create a handle to, aside from another specific class. In native c++, I could this by just declaring the creator class as a friend to the class I'm restricting creation for. However, in C++/CLI, it won't allow me to have friends for a managed type.
Does anyone know how I could get around this problem?
The absence of friend classes is a real problem in .NET, IMO. I'm not sure there's a way around it, if you want the actual class visible, but not the ability to create. Does your class derive from anything right now ?
Christian Graus - Microsoft MVP - C++ Metal Musings - Rex and my new metal blog
Last Visit: 31-Dec-99 19:00 Last Update: 20-Jan-21 10:40