G
Greg Green
Any ideas anyone?
TIA Greg
TIA Greg
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.
You should upgrade or use an alternative browser.
M
Marshall Barton
Greg said:Any ideas anyone?
Use a subform!
H
HSalim
It sounds like that is too much information on one form.
The goal of a good form should be taht it conveys all the necessary
information at a glance, in a well laid out, logical order.
Try to organize your form into logical sub groups that act like expansion
buttons
for example, you could display a custoner name or ID and when you click on
the expansion button you get
additional information such as Address or balance.
HS
The goal of a good form should be taht it conveys all the necessary
information at a glance, in a well laid out, logical order.
Try to organize your form into logical sub groups that act like expansion
buttons
for example, you could display a custoner name or ID and when you click on
the expansion button you get
additional information such as Address or balance.
HS
G
Greg Green
I have to do calculated fields for objects on multiple forms so averse to
subforms b/c more complicated to code:
me.parent!txtControlA1.value * me.parent!txtControlB1.value
vs.
txt1.ControlSource = A1 * B1 (these text boxes are named like Excel cells).
I just built the second form containing an Excel-like ~750 boxes, and the
me.recalc function work plenty fast on about 200 calculated controls. The
form is not populated by queries but by code that peruses the database. The
users are accustomed to having everything in one place. First time I've done
something this way, for this situation I like it! Given problems I've seen
Access have in other large/bizarre applications it's nice to throw something
together based on an idea and have it work correctly on the first or second
try.
GG
subforms b/c more complicated to code:
me.parent!txtControlA1.value * me.parent!txtControlB1.value
vs.
txt1.ControlSource = A1 * B1 (these text boxes are named like Excel cells).
I just built the second form containing an Excel-like ~750 boxes, and the
me.recalc function work plenty fast on about 200 calculated controls. The
form is not populated by queries but by code that peruses the database. The
users are accustomed to having everything in one place. First time I've done
something this way, for this situation I like it! Given problems I've seen
Access have in other large/bizarre applications it's nice to throw something
together based on an idea and have it work correctly on the first or second
try.
GG
HSalim said:It sounds like that is too much information on one form.
The goal of a good form should be taht it conveys all the necessary
information at a glance, in a well laid out, logical order.
Try to organize your form into logical sub groups that act like expansion
buttons
for example, you could display a custoner name or ID and when you click on
the expansion button you get
additional information such as Address or balance.
HS
K
Ken Pinard
Sounds like they want excel to be used. Have you tried embedding an Excel
spread sheet in the form?
Just a thought
Ken
spread sheet in the form?
Just a thought
Ken
Greg Green said:I have to do calculated fields for objects on multiple forms so averse to
subforms b/c more complicated to code:
me.parent!txtControlA1.value * me.parent!txtControlB1.value
vs.
txt1.ControlSource = A1 * B1 (these text boxes are named like Excel cells).
I just built the second form containing an Excel-like ~750 boxes, and the
me.recalc function work plenty fast on about 200 calculated controls. The
form is not populated by queries but by code that peruses the database. The
users are accustomed to having everything in one place. First time I've done
something this way, for this situation I like it! Given problems I've seen
Access have in other large/bizarre applications it's nice to throw something
together based on an idea and have it work correctly on the first or second
try.
GG