Connecting two forms with the same table

[uni.pd]

Hi everyone,
I'm a beginner in access and I've been having some problems with it.
Here is my problem for now. I have two forms which are supposed to
store data in the same table. Not just the same table but the same row
and different colums.
For example: the data from the first form are stored in the first 5
colums of the table and I want the data from the next form to be stored
in the same row but in the colums that come after the first five ones.
This is the best way I can explain this.
Any help would be very appreciated!!!
Thank you to everyone.

 

[John Vinson]

Hi everyone,
I'm a beginner in access and I've been having some problems with it.
Here is my problem for now. I have two forms which are supposed to
store data in the same table. Not just the same table but the same row
and different colums.

Ummm...

WHY?

This seems to be *very* awkward both for you as the developer and for
the user.

For example: the data from the first form are stored in the first 5
colums of the table and I want the data from the next form to be stored
in the same row but in the colums that come after the first five ones.
This is the best way I can explain this.
Any help would be very appreciated!!!
Thank you to everyone.

What is the structure of your table? How many fields - just ten, or
lots and lots? Is your table properly normalized???

If you *do* have good reasons to do this, how will you ensure that the
same record is open when you open the second form? Might it not be
simpler to use one Form, with two pages on a Tab control - five
textboxes (or other controls) on the first page, and the remaining
controls on the second?

John W. Vinson[MVP]

 

[uni.pd]

Well. I know it's not a very "normal" table but I rally have a reason
to do this. My table has a lot of fields. I can't put them just in one
form so I've done three forms. Thats why I'm asking...

 

[John Vinson]

Well. I know it's not a very "normal" table but I rally have a reason
to do this. My table has a lot of fields. I can't put them just in one
form so I've done three forms. Thats why I'm asking...

I needed 60 fields in a table... once, several years ago.

That was a VERY special case.

If you need more than that, it's almost a certainty that your table is
incorrectly structured, with one-to-many relationships embedded within
each record.

My tab control suggestion still applies - you can have upwards of 700
controls on a Form - but all the more I'd suggest investigating your
table structure.

If you REALLY REALLY insist - you can open one Form from another Form,
passing the current ItemID in the WhereCondition argument to
synchronize the second form to the first form's record. It's a *bad
idea* though - properly normalizing your tables is the best bet.

John W. Vinson[MVP]

 

[J. Goddard]

Take a look at using a "Tab" control on your form; each "page" of the
tab can contain different fields from the same record you are looking at.

John