Re: Still Struggling...

But the reason we did that is to get rid of tblSubs...remember? You told me
to use tblEmployees for the fields that are common to both subs and site
employees. Then you said to create a sub form for tblSiteEmps.

To this point we have been talking almost exclusively about tables. I don't
recall saying much about forms, but I could be wrong. Anyway, having the
tables set up like you do is correct, but that doesn't necessarily mean
that you have to use two separate *forms*. If you are interested in having
the names and addresses on one form, I can try to explain that later, but
if you are happy with how you have it now, then I'll just leave it alone.
Maybe
you don't need to think about anything more right now.

Yeah...about that. Can I ask you a question? I think I made a mistake by
inputting fields for ClassDescription and TitleDescription. Naturally, there
wasn't a drop-down list.

I'm not sure what you mean here. ClassDescription is certainly appropriate
in tblClassifications, and TitleDescription in tblTitles, so I'm not sure why
you
think this was a mistake. If you tell me what form you are working on and
which
tables are involved I can give you more specific advice, but in the meantime
here is some general information.

First, when referring to objects on forms like text boxes, combo boxes, etc.
they are called controls. Tables and queries have fields, forms and reports
have controls. Controls have a "Control Source" property. If the control
source
is a field (in a table or query), then the control is bound. If the control
source is
something other than a field (like a calculation), or if there is no control
source
(a control does not have to have a "control source") then it is unbound. So
to make
a bound control, you use a field as the control source. Whether a control
should
be bound or unbound depends on what you are doing. Right now,
it sounds like you are working with the subforms for your employees where
you need to assign the proper Classification and Title, so the control should
be bound, because that data needs to be stored in the table. Unbound controls
are typically used to perform searches, do calculations, etc.

Now, in the case of a combo box (or a list box), there will also be a "Row
Source"
property, which basically determines what data, or values, are *displayed* in
the
combo box. I use the term display loosely, because you can, an in most cases
would, hide certain values in a combo box so the users don't see them. This
can
be data from a table or query, or just a list of values that you define
yourself.

"...the fun is really gonna start'? What do you know that I
don't?

I would say you're finding out right about now.

Control Source. Row Source. Bound. Unbound. Master/Child links.
Bound Column. Column Count.

Fun stuff, don't you think? <big grin>

Aria wrote:
Hey, there's no crying in baseball or relational database design ;- )

<lol>I'll try to toughen up but it seems to me there's nothing *but* crying
and the pulling out of your hair!

Actually, since this is a 1:1 relationship, you can use a subform if you want,
but it's
not really necessary. You could do it all on one form if you wanted (there's
that damn
monkey wrench again <g>).

But the reason we did that is to get rid of tblSubs...remember? You told me
to use tblEmployees for the fields that are common to both subs and site
employees. Then you said to create a sub form for tblSiteEmps.

Now that you're ready to try creating some forms, the fun is really gonna
start :- )

Yeah...about that. Can I ask you a question? I think I made a mistake by
inputting fields for ClassDescription and TitleDescription. Naturally, there
wasn't a drop-down list. <imagine that> I remembered that we discussed a
combobox. I was having problems creating it because I can't find the answer
I'm looking for. Everyone seems to start at the same point, "Row Source". My
info states," You use unbound controls to display information." "...use bound
controls to display, enter, and update field values in your database."
Everything I have read so far says use unbound. When I did, it didn't save
the data. When I close and re-enter there's nothing there. I'm thinking
maybe it should be bound. Been searching for days... Why is it so hard to
find the info you're looking for?
Ok, I asked for an answer to one question but you ought to know better than
that by now. :-) "...the fun is really gonna start'? What do you know that I
don't? BTW, how do you do make a bound control? I think I tried it both ways
but it wasn't quite working or I was too tired to notice what I was doing
wrong.

Finally, I decided to create some relationships. I could
never get the ones I needed before. Guess what? It worked....it worked...it
[quoted text clipped - 27 lines]
Now that you're ready to try creating some forms, the fun is really gonna
start :- )

--
________________________

Sean Bailey
s b a i l e y 2 8 4 AT e c e n t r a l DOT c o m

Message posted via AccessMonster.com
http://www.accessmonster.com/Uwe/Forums.aspx/access-gettingstarted/200807/1

.

Relevant Pages

  • Re: Data not showing in sub form on open zzz
    ... the sub form shows its data correctly. ... Control Source or the form's Record Source. ... sub-form is corrupted, which would require the sub-form to be recreated ...
    (comp.databases.ms-access)
  • Re: Refresh certain txtboxes on a page with Form referenes
    ... Nice approaches (and yes, it's a "tab control") ... does the subform on page 1 need to be a subform? ... A text box in a sub form on the first page has a reference like this, ...
    (microsoft.public.access.formscoding)
  • Re: Data not showing in sub form on open zzz
    ... the sub form shows its data correctly. ... Control Source or the form's Record Source. ... sub-form is corrupted, which would require the sub-form to be recreated ...
    (comp.databases.ms-access)
  • Re: Return to active record
    ... You wouldn't create a separate recordset as it ... You only need to store the subform's bookmark before the ... control on the Main Form, then return to the same record ... requery the Main Form instead of the Sub Form. ...
    (microsoft.public.access.modulesdaovba)
  • RE: Want to spice up my interface...
    ... > I currently have a "sub form" displayed on the main form where the user can ... > series of command buttons - old stuff.... ... > It would also be nmice if I could use some sort of a treeview control so ...
    (microsoft.public.access.formscoding)