2 quesitons about forms

[Danny]

1. If I use the switchboard tool to open a form that is a datasheet, and
select the form 'open form for editing' it will open the form but not give
that tabular view. But when I open the form from the project window, or in
code, it will open in the datasheet or tabular view. How can I open a form
in this mode via the switchboard manager.

2. I have a table that has many categories. It is probably best to make
each one of these categories a separate table, but there would be like 60
tables.
So, how can I allow the user to edit these categories. For example, there
is a size, color, shape field. The person cannot just delete a size from
the size column, because it would effect all the other columns etc. is
there a way I can have the user delete this one cell and have everything
from that one column move up one to get rid of the gap. This way no other
columns are affected.

Thanks
Danny

[Bernard Peek]

Re: 2 quesitons about forms

In message <xsLJc.1095$Iz2 .595535@news4.s rv.hcvlny.cv.ne t>, Danny
<dannywork5@hot mail.com> writes
[color=blue]
>2. I have a table that has many categories. It is probably best to make
>each one of these categories a separate table, but there would be like 60
>tables.
>So, how can I allow the user to edit these categories. For example, there
>is a size, color, shape field. The person cannot just delete a size from
>the size column, because it would effect all the other columns etc. is
>there a way I can have the user delete this one cell and have everything
>from that one column move up one to get rid of the gap. This way no other
>columns are affected.[/color]

You haven't given me much to work on here. Categories of what, exactly?
Tables contain fields and rows. What fields? What does a row represent?

Ideally table structures are derived from the logical data structure,
one entity for each type of 'thing' the database needs to record.

My guess is that you have some sort of product that can have various
attributes; size, colour etc. In that case you may want one main table
of products and another table for each of its attributes. That means one
table for colour, probably holding a colour code and a text description.
One table for size, containing a size code and a text description field.
Is this right?


--
Bernard Peek
London, UK. DBA, Manager, Trainer & Author. Will work for money.