3 subforms for one form

[Rodger]

All,

I have a table that I had to create 3 forms becuase the form was so long. I
have a main form with lots of tabs including the 3 forms I create from the
one table. I have linked the 3 forms with the ID field. It works great on
the first subform but on the other two subforms I cannot edit the data. Any
ideas?

TIA,
Rodger

 

[John Vinson]

All,

I have a table that I had to create 3 forms becuase the form was so long. I
have a main form with lots of tabs including the 3 forms I create from the
one table. I have linked the 3 forms with the ID field. It works great on
the first subform but on the other two subforms I cannot edit the data. Any
ideas?

TIA,
Rodger

Why is the "form so long"? Does your table have a huge (>30) number of
fields? What are the Recordsources of the mainform, the subforms? What
are the Master/Child link fields of the subforms?

John W. Vinson[MVP]

 

[Rodger]

The table has about 75 fields . . . . .the form is a copy of a paper form
that we have to fill out, it is a government form. Well after much work and
looking at the form I noticed something . . . . . . I had all the fields
named WRONG . . . . .once I fixed that there was no issue!!! I was doing a
lot of coping and pasting . . . . that will teach me!!!

Thanks for your help!!

Rodger

 

[John Vinson]

The table has about 75 fields . . . . .the form is a copy of a paper form
that we have to fill out, it is a government form. Well after much work and
looking at the form I noticed something . . . . . . I had all the fields
named WRONG . . . . .once I fixed that there was no issue!!! I was doing a
lot of coping and pasting . . . . that will teach me!!!

That's one (only one of many!) of the problems that often stem from
letting paper forms drive table design.

Paper forms have their own set of logic (government forms may not even
have that... :-{( ). The underlying information structure which makes
sense for a paper form is VERY DIFFERENT from the logic of normalized
tables; if you base your table structure on a paper form it's almost
certainly going to be non-normalized, and get you into a lot of
trouble!

Consider treating your required government printout - not as a Form,
not as a Table - but as a Report, the final output of a system. Like
most Reports, it would NOT be based directly on a table, nor would
there necessarily be a Form that looks like it; instead, your table
structures would be based on the logical relationships between the
real-life entities which go into the report, and the Report (the
"Form" in government-speak) would be based on a Query consolidating
data across multiple tables.

John W. Vinson[MVP]

 

[Rodger]

John,

Yes I agree and I already did that, the form that I am has 49 questions and
some sub questions depending on the answer. I have been very careful to
make sure that all the data is normalized. Most of the paper forms all have
a section that deals with an individual and that information comes from an
entirely different table. The goal of this part of the project is to have
field agents fill out the application on their laptop and then print the
paper forms. They will then export all the data so I can import it into
their main database. Currently they have all of these paper forms in Excel
and then they print it out and send it to the main office to do all the data
entry. So we are taking that process and automating it.

Some time in the future I want to take this out of Access and move to SQL
Server and VB. but I need to learn more about that and understand how to
update multiple companies.

Have you have done anything like this? We have two separate companies that
will be using the database at two separate locations/states. So if I make
changes to the table structure on one database is there an easy way to
update the other database?

TIA,
Rodger