database design quagmire

[ski2sun]

can someone explain a design issue here...any and all input would help...which argument is better for the following...
We need a db that collects chain organizations (corporate chains that own a variety of store brand names), then a table to collect all the stores in the US. One point of view is that the user should be ultimately responsible for their entry with no tie-in to a 'store name table' that would limit the user to select from 'acceptable brand store names' as a store name once they have selected the chain organization. Example, if they choose chain 'abc corporation', then store names Alpha Inc, Beta Store Mart, and Charlie Bakery would appear. Which ever they select would go into the store name table in the store table. The 2 arguments I hear is that it is better to let the user enter the store name into the store table rather than looking at the store name list in which case they 'could possibly' select the wrong store brand name, making it bad data....but ISNT allowing free form entry of any kind in a universe of 100,000 more subject to entry inconsistencies more flawed than at least assigning a consistent, standardized convention to at least 60% of the store names....If not a chain, the user would enter the independent name. But I still feel that standardizing the chain brand names is a better solution...Oh, please offer any suggestions...viewpoints, probabilities, pros/cons..etc... a real interesting flashpoint...

 

[LittleSmudge]

The chance of a user typing in the wrong data Eg
WallMart
WalMart
Wall Mart
WallMert
etc..

is FAR GREATER than the chance of someone selecting the desired organisation from the list and clicking on the wrong line AND not noticing it.

List the options in a Combo Box.
Set the AutoExpand to YES
Set the Limit To List to YES

Then in the OnNotInList event put some code that sends a message to the effect that "Dyslexic Monkeys are able to use this system - why can't you manage it ?" ( Or maybe not )
You might need some code that says - "This store name is not a valid store name - Do you REALLY want to add it to the list of available stores ?"
This will cover you when ABC Corporation starts up a new ( fourth )chain of stores called BetaSeconds Mart


Allowing Free text entry is TOTALLY against the whole principles of Relational Database data integrity concepts.




'ope-that-'elps.

G LS

 

[PPSAG]

My end users are overloaded and not usually paying attention. So I use Combo Boxes and limittolist. Then I allow additions to that lookup table only when absolutely necessary. If they free type in a field that could be linked to a lookup table, I am just asking for bad data. A lot of people and corporations depend on my data being dependable. Whoever is presenting the argument that typing in the store name rather than choosing it from a list is not thinking of the true possibilities of human error. Mooo...