Simple stupid question

  • Thread starter Thread starter Jose Esteves
  • Start date Start date
J

Jose Esteves

Okay, I am new to Access and I need to ask a simple
question I hope. I would like to create 1 table that would
have 5 fields. then I would like to create 1 table for
each field from the first table. then I would like to
input information on that first table and have that
corresponding field dump the inforamtion that I typed into
its corresponding table. I hope this makes sense.
 
Tell us what you're trying to achieve...What information are you storing in
the table? What are you modelling? What problem are you trying to solve?

--
Rebecca Riordan, MVP

Seeing Data: Designing User Interfaces
Designing Relational Database Systems, 2nd Edition
www.awprofessional.com

Microsoft SQL Server 2000 Programming Step by Step
Microsoft ADO.NET Step by Step
www.microsoft.com/mspress
 
Okay what I would like to have is a database of all fixes
we have done to our computer systems. the first table will
have these fields

TypeOfFix
TypeOfO/S
Soulution
DateCompleted

Then I would like to have separate tables for each of
these fields. I.E...
tblTypeOfFix,,tblTypeOfO/S,,tblSolution ect..ect..

I willbe inputting the information out of a form that was
created from the first table. and what I want is that when
the information gets inputted I would like the information
to go to there corresponding tables.

So Example, if I type windows 2000 in TypeOfO/S in the
main form. I would like to go to the TypeOfO/S Table and
see Windows 2000 in the filed as well as any other
information that gets put in that field. Hope this
explains more of what I would like to get at. thank you
for your response
 
Good Question....lol. I dont know, I really dont need them
but I would like to have them so that when I need to
create a database that I would need to keep seperate
tables I would no how to so it already. this is just for
personel knowledge
 
Well, you'd do it by calling an append query from a form. There's no way,
to my knowledge, to get Access/Jet to do it automatically. You can do it
with an Trigger in SQL Server.

But I can't think of a single exception to it being a really bad idea. The
whole point of a relational database is to minimize duplicate data. If
you're storing the same information in multiple problems, you're really
cutting a rod for your own back. What happens if it changes? What happens
if it gets deleted? What happens if....see what I mean? <g>

--
Rebecca Riordan, MVP

Seeing Data: Designing User Interfaces
Designing Relational Database Systems, 2nd Edition
www.awprofessional.com

Microsoft SQL Server 2000 Programming Step by Step
Microsoft ADO.NET Step by Step
www.microsoft.com/mspress
 
I see what you mean, I just wanted to see if it could be
done, from what I hear is that it can be done but it is
not worth the effort to do it this way. thank you very
much for your help.
 
I would think that a query could produce the information
you need. Base a query on the table, and select just the
Primary Key field and whatever fields are needed. You
could also use reports. Base a report on the table, but
selct just those fields you want to see. If you use the
query method, you can save a query as a table if you want
to some day. I agree strongly that you should make every
effort to avoid duplicate data, but that needn't limit
your flexibility. In fact, it should enhance it.
 
Back
Top