We're designing an e-commerce app. using SQL 7. We want to allow for
unlimited billing/shipping locations. There will also need to be
"levels" of users, i.e. Master Admin - administers all information,
including company info., etc. for all locations. Location admin - only
administers info. for a specific location or locations (determined by
the Master Admin). Basic - can administer only their information.
What we have penciled out so far are 4 tables: 1 "master table" to hold
information on the company, including pricing level, tax status, etc. 1
table for billing info., 1 table for shipping info., and 1 table that
contains the location IDs that the Location Admin can administer (set by
the Master Admin), along with the name of the sublocation (i.e. Company
name General Electric, sublocation could be Norwalk, or New York).
So, my question is: First, and I know it's not a lot of info. to go on,
does it sound logically laid out? Second, has anyone designed something
like this that's in production use? I know at Amazon or Barnes and
Noble, one can have multiple billing/shipping locations, but those are
tied to the user who has logged in. We want to allow a flexible method
of allowing one user to manage a large amount of locations (one of our
customers has over 200 locations to manage), yet make it as simple as
possible for the user.
*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!