Creating Option Buttons or check boxes with Access 2000 using VB

My current project requires me to create part of a form that is
created on the fly. The project consists a list of entries to an
event. The name and address and such is easy. The design is detup so
that the creater of the even can make their own event in the database.
When they do so a 2 tables are created. One for the entries such as
names and the other is for the parameters of each event.

The creator then goes in and makes each event giving it a name and
setting the parameters. This is all easy for me and works fine. When a
user goes into to start adding entries they put in the personal info
and using a series of check marks check what the events that person is
in.

How do I create a series of option boxes, or check boxes when I don't
the know names of the events or even the number of the events?
(Actually I may want to be using check boxes instead). Also an event
maybe added after entries are being started been taken.

I do know how to create select statements, change properties of form
elements and such. I also know the table name where the name of the
events occur. The user selects it so thats not a problem.

What has me stumped is creating form elements using VB in access 2000.

At this point I need a direction to look or even a simple example.

Thank you.

PS The actual design of the form and layout works wonderfully. We used
it this summer at a real event. The problem is that the tables and
queries were only for that event so we are building something that
anyone can use. In reality we only used the backend features of access
since myself and a friend were running it.

re: Creating Option Buttons or check boxes with Access 2000 using VB

I've never had occasion to be _required_ to create Forms/Controls on the
fly. It's usually a poor solution to some perceived problem that should be
addressed a different way. But then, I've only been in this business since
1957 and only used Access since January of 1993, so I might have missed a
few requirements here and there.

And, as for "when I don't the know names of the events or even the number of
the events?", I'm not sure what you are talking about. Are you talking about
creating event code to go with the controls you want to create?

In any case, if you'd detail what you have and what you really need to
accomplish, perhaps someone could suggest an approach that will do what is
needed.

Larry Linson
Microsoft Access MVP


"Ben" <benmcl@hotmail.com> wrote in message
news:bd807c82.0309220809.6685ee84@posting.google.c om...[color=blue]
> My current project requires me to create part of a form that is
> created on the fly. The project consists a list of entries to an
> event. The name and address and such is easy. The design is detup so
> that the creater of the even can make their own event in the database.
> When they do so a 2 tables are created. One for the entries such as
> names and the other is for the parameters of each event.
>
> The creator then goes in and makes each event giving it a name and
> setting the parameters. This is all easy for me and works fine. When a
> user goes into to start adding entries they put in the personal info
> and using a series of check marks check what the events that person is
> in.
>
> How do I create a series of option boxes, or check boxes when I don't
> the know names of the events or even the number of the events?
> (Actually I may want to be using check boxes instead). Also an event
> maybe added after entries are being started been taken.
>
> I do know how to create select statements, change properties of form
> elements and such. I also know the table name where the name of the
> events occur. The user selects it so thats not a problem.
>
> What has me stumped is creating form elements using VB in access 2000.
>
> At this point I need a direction to look or even a simple example.
>
> Thank you.
>
> PS The actual design of the form and layout works wonderfully. We used
> it this summer at a real event. The problem is that the tables and
> queries were only for that event so we are building something that
> anyone can use. In reality we only used the backend features of access
> since myself and a friend were running it.[/color]

re: Creating Option Buttons or check boxes with Access 2000 using VB

I probably should make this clearer than I did in my last post.

THe user opens the admin form. The first thing done is to create a
show and give it a name. "South Mountain"

This creates 2 tables. 1st table is the names and addresses of the
particpants. 2nd is the list of the events and the parameters of it,
how many divisions, time split and placings to be awarded.

Next the user creates the first event. This creates a yes/no field in
the personal table to be used to check wiether or not the person is in
that event. The number of events could be anywhere from 3 to 35 and
given any name.

When all the events are created the user goes into the entry form and
starts to fill in the info such as name and phone number then checks
off what events that person is going in. Of course I have no idea when
I create the form how many or what the name of the events are so I
would like to create the check boxes on the fly when the person enters
the form.

Also some times events can be removed or added to a show so the next
time the user enters data the changes must appear. We really like the
check boxes because it is very fast, and simple. As I said before when
we designed it before we went through many different ways of
displaying and using this part of the interface and concluded it to be
the best way.

Please note there is a very real possibility of dividing up the
peronal table into a more organized fashion. ie 1 table for the
personal info and and other table to keep track of the events they are
in.

I would also like to point out that only one person at a time would be
using it and that the number of records are very low.

The one solution I posted before is very ugly. For some reason though
I thought Access 2000 had a something to create a form object. Hope
this clears things up.

Thanks again.