Too many forms, I Think?

  • Thread starter Thread starter Daryl B. via AccessMonster.com
  • Start date Start date
D

Daryl B. via AccessMonster.com

Hi everyone,
I have a question about a program I am creating for my work.
I am not very skilled at Access and I basicly need to know if I am going
about this right. I have created a Form with a Tab Control that has 6
Pages. I have 8 subforms Total on this Tab Control. Average 2 per page, one
is in Datasheet View and the other is in Form view. The subform that is in
Form view I use to input records that pop up on the Form that is in
Datasheet View. All forms are linked between 7 tables. Usualy using a one-
to-many relationship. I have used Forms becuse I do not know any other way
of entering my data between the different tables. I do not like the record
selectors that come with the Forms. So I create the command buttons to move
between records. Which means I have 5 sets of buttons between the Forms.
Basicaly I need to know if this is an overkill, or is there a better way.
Thanks
 
Daryl B. via AccessMonster.com said:
Hi everyone,
I have a question about a program I am creating for my work.
I am not very skilled at Access and I basicly need to know if I am
going about this right. I have created a Form with a Tab Control that
has 6 Pages. I have 8 subforms Total on this Tab Control. Average 2
per page, one is in Datasheet View and the other is in Form view. The
subform that is in Form view I use to input records that pop up on
the Form that is in Datasheet View. All forms are linked between 7
tables. Usualy using a one- to-many relationship. I have used Forms
becuse I do not know any other way of entering my data between the
different tables. I do not like the record selectors that come with
the Forms. So I create the command buttons to move between records.
Which means I have 5 sets of buttons between the Forms. Basicaly I
need to know if this is an overkill, or is there a better way. Thanks
Click to expand...

Without my knowing what you're doing, why you're doing it that way, and
what it really looks like, anything I can say is of limited value. But
I don't see anything fundamentally wrong with what you describe, if it
translates to ease of use and maintainability. I have some reservations
about the two-form combinations but, knowing only what you've told us, I
can't say that it's a bad idea.

It does seem rather a complex form, but I have an application with a
form that complex. One thing you want to watch out for, with all those
subforms, is that the form may take a while to load if you run it over a
network. There's a trick you can use to get around that problem if you
have to -- you can keep all the subforms unbound except the ones that
are currently invisible, using the tab control's Change event to run
code that sets and clears the recordsources.
 
Thank you,
The loading on page turn sounds good, I will try this.
 
Back
Top