I was wondering if I should use the profile or not. Part of the membership is going to be requiring a lot of information about the user. Their are two types of users and between both of them combined there is between 80-90 questions. Which I think is to much for one table, it might be okay while the site has low traffic but once it starts picking up traffic, won't that slow it down alot? I was thinking that many questions to group them up 6-7 tables.
I've been working on these table most of the day without any luck. From what I can gather, you can't write to aspnetdb, if you add another table. Atleast everytime I go to Detailsview or Formsview, or even just the connection I made for aspnedtdb, it won't allow to set the Insert option, under advance it's grayed out and of course, there is no options on the details or formviews. So if this is the case, I assume I'm going to have to make an entire new DB, and just get rid of aspnetdb? The reason I ask th ...
Go to the complete details ...