Re: One to One - Multilple tables for large field qty

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

Jeff,
Thanks for th reply. As I mentioned this was the second pass at having to
explain a reason why our business scenario need for this, I just need to
look for a technical answer. This database (something I did not mentioned is
this db is normalized with an abundance of one to many table surrounding it..
it is in 3N form...it just so happens that a few forms have too many fields
that needed to be broke up, but have a cenrally controlled autonumer ID
generated)

So, just a technical question outside of right and wrong: What is the VBA/
query process for getting the primary key of hdr table into the third table
of a three-table one to one join? In other words, when I join my hdr table
(one to one) with each form table, the creation of a record work fine (it
added the PK to both tables). If I add the third one-to-one, the primary key
does not copy to the third table (have to key in manually in order for the
join to work)

Thanks for any technical advice.
Brahio

"Jeff Boyce" wrote:

Brahio

If you were advised to normalize your data, there's a reason.

Access is a relational database. Its features/functions are designed to
work with well-normalized data.

If you insist on feeding it 'sheet data (wide, many fields), both you and
Access will have to struggle to find ways to do what is simple if only your
data was well-normalized.

If you insist on using a spreadsheet-like data structure, you might not get
many folks offering ideas -- after all, I can drive nails with my chainsaw,
but it's neither safe nor easy.

Is there a reason you aren't just doing this in a spreadsheet application,
since it sounds like you've decided that's how your data will be organized?

Good luck!

Regards

Jeff Boyce
Microsoft Office/Access MVP

"Brahio" <Brahio@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:33081068-68BF-47EB-94DF-272B49FC5BDC@xxxxxxxxxxxxxxxx
HI,
I recently posted a question, but would like to resend in a different
light.
The responses were only about my data not being normalized, but I just
need
some guidance regardless.

I have to use one-to-one joins as our users have four different form types
needing to go into Access. Each form has some similar info in the header
(where I created a single table) such as created by, Date, Form ID#. I
created at a minimum one table for each of the four forms because the data
will be approaching the 255 limit. Two of the forms, I had to add another
table as to again not approach 255. There are no entities to break up
(like
customers to orders, to details, converting to 3N, etc which I have more
experience in)

So here is my question. On the header table there is a form ID (primary
key
with autonumber) which is joined with a one-to-one to another table2 (has
about 230 fields - questionnaire types, etc). I created a third table
joining the same FormID.

I created a form from a query and entered a new record. When I look at
the
header table, it created formID#99, fine. When I look at table 2, I can
see
that the record is created with the FormID #99 as well. Fine. But on the
third one-to-one join, it never creates a record, even when I have some
information populated. I was hoping it would create a recordset with only
the FormID #99 filled in.

Thanks for any feedback
Brahio




.

Relevant Pages

  • Re: Itanium Port Question
    ... It is a fine and good practice to have the primary key be the first ... if you have no reason for it to be elsewhere. ... By physicaly storing the primary key up front, rms does not have to ... I found RMS compression to ALWAYS be a net CPU AGAIN. ...
    (comp.os.vms)
  • Re: Primary Key and Indexes, are they necessary?
    ... The vendor responsed that the reasons they do not add the primary key ... Indexes do slow down data entry. ... Indexes should always be evaluated and have a reason for existing. ... In Oracle 10g, the Cost Based Optimizer has been improved to the point ...
    (comp.databases.oracle.misc)
  • Re: Primary Key and Indexes, are they necessary?
    ... The vendor responsed that the reasons they do not add the primary key ... Indexes do slow down data entry. ... Indexes should always be evaluated and have a reason for existing. ... In Oracle 10g, the Cost Based Optimizer has been improved to the point ...
    (comp.databases.oracle.misc)
  • Re: Imagination
    ... I know of no reason I need to adjust my post to the level ... To limit spam harvesting it is not in the posting header. ... post exact recipes. ... But there is a real issue--- Diabetes has damaged my hands ...
    (alt.support.diabetes)
  • Re: offsetOf
    ... in that file (only using pointers, the header with the struct definition ... When you use opaque types, translation units which work with that type ... single common header file. ... a normal consequence of that bad decision, and is in fact the reason why ...
    (comp.lang.c)