1 table - 2 forms

1 table - 2 forms

am 12.01.2008 20:06:38 von mcgrathml

Hi,

A customer has a table with greater than 30 columns (scientific
readings). The form used to input the data is very difficult to use
and I'd like to ask the group:-

(1) Can a main form call a sub-form that allows input of data
(into the same table as the main form) and then returns to the main
form?

(2) Could the form be split in any way so half the input fields
are available, then the operator can move to the other half?


The customer cannot split the columns in the table into two tables.

Any suggestions greatfully received.

Michael

Re: 1 table - 2 forms

am 12.01.2008 21:34:50 von Salad

mcgrathml@gmail.com wrote:

> Hi,
>
> A customer has a table with greater than 30 columns (scientific
> readings). The form used to input the data is very difficult to use
> and I'd like to ask the group:-
>
> (1) Can a main form call a sub-form that allows input of data
> (into the same table as the main form) and then returns to the main
> form?
>
> (2) Could the form be split in any way so half the input fields
> are available, then the operator can move to the other half?
>
Get to the database window. Open a table. Hold your shift key down and
click on 2 or 3 columns. Select Format/Freeze from the menu.

>
> The customer cannot split the columns in the table into two tables.
>
> Any suggestions greatfully received.
>
> Michael

Re: 1 table - 2 forms

am 12.01.2008 21:38:06 von Tom van Stiphout

On Sat, 12 Jan 2008 11:06:38 -0800 (PST), mcgrathml@gmail.com wrote:

You can create a wizard-style interface by using a hidden tab control.
On tab one you have the first step with the most important fields,
then user clicks the next button and you switch to tab two with the
next couple of fields, etc.
If user wants to see all data, write a report.

-Tom.


>Hi,
>
> A customer has a table with greater than 30 columns (scientific
>readings). The form used to input the data is very difficult to use
>and I'd like to ask the group:-
>
> (1) Can a main form call a sub-form that allows input of data
>(into the same table as the main form) and then returns to the main
>form?
>
> (2) Could the form be split in any way so half the input fields
>are available, then the operator can move to the other half?
>
>
>The customer cannot split the columns in the table into two tables.
>
>Any suggestions greatfully received.
>
> Michael

Re: 1 table - 2 forms

am 12.01.2008 22:10:17 von u28780

A tabbed page control is designed for just this purpose! The first thing to
remember is that the Tabbed Pages are all part of a single form; think of it
as a really long form turned on its side. Because it is all one form, all
referencing to any control on it is done in the same manner as if they were
all on one single screen.

Create a form in Design View. Goto the toolbox and click on the Tabbed
Control icon; it actually looks like several manila file folders. Place it on
your form and adjust the size to your liking. If you need more than the two
tabbed pages it initially gives you, click on the tabbed control to select it.
Goto Insert and click on Tabbed Control Page and another tabbed page will be
added. Do this as many times as necessary.

This is the really important part: when you go to add a control to a tabbed
page, you must first click to select one of the pages, then add the control.
Otherwise, the control will be added to the form itself, and will show thru
on all tabbed pages!

--
There's ALWAYS more than one way to skin a cat!

Answers/posts based on Access 2000/2003

Message posted via AccessMonster.com
http://www.accessmonster.com/Uwe/Forums.aspx/databases-ms-ac cess/200801/1

Re: 1 table - 2 forms

am 13.01.2008 16:41:34 von Don Calloway

On Sat, 12 Jan 2008 21:10:17 +0000, Linq Adams via AccessMonster.com
wrote:

> A tabbed page control is designed for just this purpose! The first thing
> to remember is that the Tabbed Pages are all part of a single form;
> think of it as a really long form turned on its side. Because it is all
> one form, all referencing to any control on it is done in the same
> manner as if they were all on one single screen.
>
> Create a form in Design View. Goto the toolbox and click on the Tabbed
> Control icon; it actually looks like several manila file folders. Place
> it on your form and adjust the size to your liking. If you need more
> than the two tabbed pages it initially gives you, click on the tabbed
> control to select it. Goto Insert and click on Tabbed Control Page and
> another tabbed page will be added. Do this as many times as necessary.
>
> This is the really important part: when you go to add a control to a
> tabbed page, you must first click to select one of the pages, then add
> the control. Otherwise, the control will be added to the form itself,
> and will show thru on all tabbed pages!

If you don't want to use tabbed pages, I implemented something in a
database I constructed which accomplishes the same thing without tabbed
controls. The answer was to have separate forms, each of which add a
certain portion of the table's information. Access to each form is
controlled through the switchboard. You can look at the input as steps
1, 2, ... n with the nth step being the final one to complete the record
in the table. My approach worked well because a single record isn't
entered by just one individual, but several individuals input their
portion of the total data record until the last person completes it.
Your situation may not lend itself to that approach, and so the tabbed
layout is probably what you need.

Re: 1 table - 2 forms

am 13.01.2008 17:35:35 von lyle

On Jan 12, 2:06 pm, mcgrat...@gmail.com wrote:
> Hi,
>
> A customer has a table with greater than 30 columns (scientific
> readings). The form used to input the data is very difficult to use
> and I'd like to ask the group:-
>
> (1) Can a main form call a sub-form that allows input of data
> (into the same table as the main form) and then returns to the main
> form?
>
> (2) Could the form be split in any way so half the input fields
> are available, then the operator can move to the other half?
>
> The customer cannot split the columns in the table into two tables.
>
> Any suggestions greatfully received.
>
> Michael

All Data are strings.
All DataBases are vertical.

Horizontal Databases are not databases. They are toys.

Customers don't have tables. They have needs. We meet them. When we
use good database design we have a good chance of meeting them well. A
Scientific Reading is a Scientific Reading. Unless there is much more
to your story, the thirty columns should be one column and we should
edit the data with a form-subform combination based on a Main Table,
Child Table configuration.
Such a design is scaleable, easliy analyzed and likely to operate
flawlessly. Thirty columns is nonsense.

Re: 1 table - 2 forms

am 15.01.2008 11:55:31 von Dominic Vella

Yes to Both.

Using a Main form to call a subform - When you use the Create Form Wizard
you will see that you have 2 choices to manage Subforms, either as subform
inside the main form, or by clicking on a toggle button which opens a new
form. The wizard does a fine job setting this up, but because you're
opening the same table, you may need to experiment a while to get how the
background code works.

Can a form be split - You can use the tab control and group your inputs into
specific tabs, or you can also use pages which is also in your toolbox.
You may want to check out the employees form in the sample NWind.mdb that
comes with MS-Access.


Dominic

wrote in message
news:a6e7d801-399f-4ca3-88e1-3a2bf99ad4ed@i72g2000hsd.google groups.com...
> Hi,
>
> A customer has a table with greater than 30 columns (scientific
> readings). The form used to input the data is very difficult to use
> and I'd like to ask the group:-
>
> (1) Can a main form call a sub-form that allows input of data
> (into the same table as the main form) and then returns to the main
> form?
>
> (2) Could the form be split in any way so half the input fields
> are available, then the operator can move to the other half?
>
>
> The customer cannot split the columns in the table into two tables.
>
> Any suggestions greatfully received.
>
> Michael