I have had no personal experience of Adsense but I have read a reasonable number of Blogs/Articles about their, sometimes, arbitrary application of their rules to cancel accounts, withhold payments etc. So do a great deal of research before signing up. A search for adsense problems, or similar might bear dividends. A search of the Messages on this site will also garner useful information Why Google sucks today[^], for example. Henry Minute Do not read medical books! You could die of a misprint. - Mark Twain Girl: (staring) "Why do you need an icy cucumber?" “I want to report a fraud. The government is lying to us all.”

Ask to the oracle or Yoda "Go for it!"

Well, during the user creation you can define the user by assignning it to a specific group, authentication type like windows or application, and roles. You may want to store them in the database and should be have normalize tables. Furthermore, You may perhaps have a group mainteance page or role maintenance where these could be maintained. So when the specific user is logged in to the system. You through the groups and roles and check what kinds of layout this user should be able to view.

I've done this in the past, but I never use the MS generated drivel, it always seems to end with hitting a brick wall unless you start by deciding your app will look and feel the way they decided it should. Perhaps you need to write your own permissions system ? It's not difficult. Christian Graus Driven to the arms of OSX by Vista. Read my blog to find out how I've worked around bugs in Microsoft tools and frameworks.

for the first question do you suggest to me to have a table design as suggested here http://social.msdn.microsoft.com/Forums/en-US/sqlgetstarted/thread/9b781fae-a12d-4405-9a6e-9dd5421b4fc4/[^] Fields FieldID FieldName 1 Website 2 Home Phone 3 MSN (the fieldnames will be user created) Field Values ContactID FieldID FieldValue X 1 Hotmail.com X 3 Abc Y 2 65766786786 Y 1 msn.com have I understook properly. or haven't I :confused: the solution for my second requirement works like a breeze :cool:(yikes why didnt I think of this) hi hi hi hi

jarajeshwaran wrote: The application will be very simple with not more than 20screens. The underlying database will contain not more that 25tables. That doesn't add up; I'd expect a "list"-form and a "details"-form for every entity, allowing you to browse the entire collection or edit a single entity. jarajeshwaran wrote: Even if it is a multiuser application the number of user will not be more than 5 at a time. The application will be used by a large number of people so bug fixing and introducing new features should be a breeze New features could be introduced with a plugin-system, you could opt to load an assembly dynamic. There are some articles on CP explaining how to do such a thing :) jarajeshwaran wrote: The app will be having basic CRUD screens and the Business logic involved will not be too complex. So a generic CRUD-form would suffice? jarajeshwaran wrote: The time to market of the resultant should be very less. I'd walk away as soon as this sentence drops, without any hesitation. The TTM should [b]never[/b] be confined by the manager. Imagine you selling a house with a limited TTM: would you sell it without a roof? --edit-- As I've been told, the houses are sometimes already sold before the drawings are even agreed upon. There seem to be special constructions to ensure that you get a roof. And that construction won't grind to a halt midterm. jarajeshwaran wrote: I would like to know which framework or design pattern should I use to achieve the above functionality with least coding. I don't want to go with any third party tools. The .NET framework, and databinding :) I are Troll :) modified on Friday, September 18, 2009 4:09 PM