Accounting Systems students inexperienced in ASP in need of some help. Our current task is building any website incorporating ASP; we chose a recipe website. Our problem occurs in the Addition of new data to the database. Here's the premise:
tblRecipeHeader
RecipeID, auto-number, PK
RecipeName, text
RecipeAuthor, text
Recipe Category, text
tblIngredients
RecipeID, number, FK
IngreLine, auto-number, PK
Measure, text
Ingredient, memo
tblSteps
RecipeID, number, FK
Line, auto-number, PK
Instruction, memo
This allows us to piece together the recipe based on the RecipeID of the RecipeHeader. On the website, this uses 3 database results on one ASP page and looks great!
However, being able to add data is the problem. In Access (where most of my experience lies) it is very easy to add the recipe in 3 sections on one form by turning them into queries and then by incorporating subforms and linking the RecipeID fields in each of them. Piece of cake! In ASP, I'm finding you just can't do it that way.
My next idea was breaking up the "Add a recipe" section into three different pages (let's say similar to how you create a resume on Monter.com). Would that work? Any suggestions? How would the primary key of the Header section feed into the 2nd and 3rd pages where ingredients and steps are added?
Then, in doing research, I found postings saying auto-number fields where duplicate values are set to "No" will create errors when trying to post the data from the form to the database. I'm finding this not to be the case in using simple ASP with single-line form field. But, if I begin using SQL incorporating INSERT then I hit problems where the errors include "use an updatable query" and "object is read-only."
I/We desperately need some insight on how to proceed. Any suggestions anyone can provide would be greatly appreciated!!!
Thanks again!!!
tblRecipeHeader
RecipeID, auto-number, PK
RecipeName, text
RecipeAuthor, text
Recipe Category, text
tblIngredients
RecipeID, number, FK
IngreLine, auto-number, PK
Measure, text
Ingredient, memo
tblSteps
RecipeID, number, FK
Line, auto-number, PK
Instruction, memo
This allows us to piece together the recipe based on the RecipeID of the RecipeHeader. On the website, this uses 3 database results on one ASP page and looks great!
However, being able to add data is the problem. In Access (where most of my experience lies) it is very easy to add the recipe in 3 sections on one form by turning them into queries and then by incorporating subforms and linking the RecipeID fields in each of them. Piece of cake! In ASP, I'm finding you just can't do it that way.
My next idea was breaking up the "Add a recipe" section into three different pages (let's say similar to how you create a resume on Monter.com). Would that work? Any suggestions? How would the primary key of the Header section feed into the 2nd and 3rd pages where ingredients and steps are added?
Then, in doing research, I found postings saying auto-number fields where duplicate values are set to "No" will create errors when trying to post the data from the form to the database. I'm finding this not to be the case in using simple ASP with single-line form field. But, if I begin using SQL incorporating INSERT then I hit problems where the errors include "use an updatable query" and "object is read-only."
I/We desperately need some insight on how to proceed. Any suggestions anyone can provide would be greatly appreciated!!!
Thanks again!!!