Several columns in a form---How to?

[spdas]

Aloha, I would like to show one field (textbox), that represents an
inventory item and have 200-300 of these fields on a page.

1: I want to stay in the form format and not report as I want to use
mouseovers

2: Each Textbox would be one large inventory item and I will be adding
or subtracting daily and would like to arrange them on a form or map.

3: I have done this before but with stationary inventory and it was a
lot of work to setup 300 units on a page.
Now I need to do this using flexible inventory.

Ideas anyone?
Would Hierarchical FlexGrid work? I have tried subforms, but it gets
too bulky.
frank

[pietlinden]

Maybe I'm completely missing something here, but why would you need 300
controls on a form? I don't think Access will even allow something
like that.

Never mind the layout for a minute. What is the purpose of this form?
It looked for a minute like you needed a datasheet or columnar form,
but the more I read, the less sure I am.

[spdas]

pi********@hotmail.com wrote:

Maybe I'm completely missing something here, but why would you need 300
controls on a form? I don't think Access will even allow something
like that.

Never mind the layout for a minute. What is the purpose of this form?
It looked for a minute like you needed a datasheet or columnar form,
but the more I read, the less sure I am.

Aloha, to explain more fully.
1: I will want 200+ boxes on a form to represent my rental units.
2: On mouse over on any box it will bring up the customer info on a
subform on the right of the form
3: I built one before with a given number of text boxes for the units
and it works great and is clickable to bring up a ledger for the
customer or double click to pull up customer info, etc.

But this new application will have the text boxes varying daily and not
static so I need to get the info from queries, rather than the static
"Unit Map" as I described above.

I also do not want to go to a report as I want to be clickable and
mouse-overable. I am playing with subforms now and trying to determine
if this will work for me.

frank

[Rick Brandt]

spdas wrote:

Aloha, to explain more fully.
1: I will want 200+ boxes on a form to represent my rental units.
2: On mouse over on any box it will bring up the customer info on a
subform on the right of the form
3: I built one before with a given number of text boxes for the units
and it works great and is clickable to bring up a ledger for the
customer or double click to pull up customer info, etc.

But this new application will have the text boxes varying daily and
not static so I need to get the info from queries, rather than the
static "Unit Map" as I described above.

I also do not want to go to a report as I want to be clickable and
mouse-overable. I am playing with subforms now and trying to
determine if this will work for me.

You should have a table for rental units where each ROW contains the data
for a unit and then in a continuous form you would display 200 repeating
rows with the design of the form only needing enough controls for a single
record. What you are describing is not a proper use of a database form.

--
Rick Brandt, Microsoft Access MVP
Email (as appropriate) to...
RBrandt at Hunter dot com

[spdas]

>
You should have a table for rental units where each ROW contains the data
for a unit and then in a continuous form you would display 200 repeating
rows with the design of the form only needing enough controls for a single
record. What you are describing is not a proper use of a database form.

--
Rick Brandt, Microsoft Access MVP
Email (as appropriate) to...
RBrandt at Hunter dot com

Aloha, I am trying to avoid the 200 repeating rows using up the entire
row as I would like to have all 200 records displayed on one page. If
there was a column feature for forms then this would be no problem.
Limiting the form width by using subforms is too cumbersome,

Frank

[Rick Brandt]

spdas wrote:

You should have a table for rental units where each ROW contains
the data for a unit and then in a continuous form you would display
200 repeating rows with the design of the form only needing enough
controls for a single record. What you are describing is not a
proper use of a database form.

--
Rick Brandt, Microsoft Access MVP
Email (as appropriate) to...
RBrandt at Hunter dot com

Aloha, I am trying to avoid the 200 repeating rows using up the entire
row as I would like to have all 200 records displayed on one page. If
there was a column feature for forms then this would be no problem.
Limiting the form width by using subforms is too cumbersome,

Frank

Perhaps you could use multiple side by side ListBoxes. 4 with 50 units each, or
8 with 25 units each, etc..

--
Rick Brandt, Microsoft Access MVP
Email (as appropriate) to...
RBrandt at Hunter dot com

[Bas Cost Budde]

Several thoughts come to mind

* create the form on the fly. Given the right specs, that shouldn't be
too hard. I'd be glad to assist, if you wish we can discuss this over email

* use a Collection of objects to define the behavior of the controls,
you don't want to repeat your action code 200 times. Write a class
module that does with the control what you want. I Can show you sample
code if you need it.

* don't think MouseOver, think ControlTipText :) it is a property of any
control, defining what you see when you mouseover it. (Now is 'to
mouseover' really a verb?)
--
Bas Cost Budde
Holland