Re: Access 2002 Advice

Tech-Archive recommends: Speed Up your PC by fixing your registry

From: Jeff Boyce (JeffBoyce_IF_at_msn.com-DISCARD_HYPHEN_TO_END)
Date: 01/14/05 

Date: Fri, 14 Jan 2005 05:00:16 -0800

Aside from your desire to use 13 separate sections on the form, what
rationale have you used to determine that this must be 13 separate tables,
plus a main table? I ask because the standard approach to designing a
relational database (Access, SQL Server, Oracle, ...) is to start with the
entities (tables) and relationships first, then design forms that make it
easy for users.

Without more information about how your data is structured, it could be
tough to offer (cogent) suggestions... 

-- 
Good luck
Jeff Boyce
<Access MVP>
"saschamps9903" <saschamps9903@discussions.microsoft.com> wrote in message
news:46E41EFD-A15F-41C2-A165-4D45F6D9B9CC@microsoft.com...
> Hello,
>
> I am in the middle of designing a database for my department and I need
some
> guidance as to how to proceed.  I am desiging a form that will be broken
down
> into 13 seperate sections for users to complete, all sections relate to
one
> "account number".  What I did was create 13 different tables using the
same
> primary key in each table (ex: account number as PK in each table).  Then
I
> tied together each table as a query and started to create the from using
the
> one query as the basis for the form.  When I type in the "account number"
on
> the form , all of the tables are updated with the information that
> corresponds to each section.  my question is, will this type of design
turn
> my database into one complete mess?  or am I on the right track with how I
> have designed it to this point?  I would like to draw reports off of the
> entered information and I feel that this design method may screw
everything
> up.  I am using windows 2K with office xp

Relevant Pages

  • RE: "Module" option does not show up when setting permissions.
    ... It's by design. ... Access 2000 introduced the separate VBA ... Project for handling the code (notice the separate code window (VB Editor) ... an MDE database file out of it if you want to hide the source code from ...
    (microsoft.public.access.security)
  • Re: MVC design questions
    ... Instead of a single CRUD GUI program I've got two, the idea being that one can be given to anybody because it can't damage the database (no insert/update/ delete capability at all while the other, which can do these things, is intended only for suitable authorised users: most data is bulk loaded and the update GUI is only there for removing to odd piece of junk and tidying up. ... In fact, i'd create three - a full-access account for the DBA, an account with the ability to edit the data, but not do DDL, for the update app, and a read-only one for the search app. ... I have almost no OO background and have no idea who the currently recognised OO design gurus are. ... That era was dominated by big ideas - big processes, big notations, big books, big words. ...
    (comp.lang.java.programmer)
  • Re: database design question
    ... has projectID and ContactID fields in it. ... proper table design for the database. ... If I build separate tables for each contact role ...
    (microsoft.public.access.gettingstarted)
  • Re: Access 2002 Advice
    ... analyst type in the account number, name of account holder, address, etc. ... the database will probably get bogged down and get ... > entities and relationships first, then design forms that make it ...
    (microsoft.public.access.tablesdbdesign)
  • RE: Advise needed on Single user to multi-user database change
    ... the Database and you need to connect to the SQL Server using that account ... Do you plan to use the "sa" account or create separate accounts for each ... different connection to the database. ...
    (microsoft.public.sqlserver.server)