LookUpWd-cont'd

  • Thread starter Thread starter Linda
  • Start date Start date
L

Linda

Hi Albert,

I am totally daunted! :(
Here's what I've done so far...lost all my entered names
in my form (snnniffff). Yet, when I checked a few of my
queries and my LFiles Table they seem to be all there as
entered, which I suppose is good-I think. Here's step by
step what I've done:

1- Gone to Tables under Objects and created a new Tbl
called Names. So now I have 2 tables: Legal Files and
Names.

2- Went into the underlying LFiles Table and in the Data
Type, it already had "Text" there, so went down into the
LookUp Tab (under Display Controls was Combo/Row Source
Type was Value List/Row Source were the names I had typed
when the LKUP Wd popped up) I've changed the DisplayC to
Text. Saved that and exited that.

3- Went to Forms where I already had a form Add New
Files. I now made another form to add New Names in the
future.

4-Opened Add New Files in DView, opened the toolbox, made
sure the wand was pressed; pressed Combo - chose ...values
in Tbl/Qu chose Names, which says Names-Unbound then
deleted the old Names...poooff when I went into Form View,
names gone. (real sad face)

Didn't go any further as that seemed to be "quite" enough
(!)

Albert, the "Make care note" about left joins, not sure
what that is, though that doesn't mean that I haven't seen
it, just that I don't/didn't know the name. How do I get
that to appear to see what you're talking about?

Really appologize that this is so long. (I've been waiting
for 2 months for an answer from my boss to take an Access
course and still waiting and have followed-up regularly,
and still waiting... a little dispirited) So I have to
rely on this site for answers, not that I wouldn't use it
but I would understand more of it all.

So again, if you have any suggestions on how I've done so
far, apart from losing the names, I'll keep on going.

Kindes regards
linda
 
Linda said:
Hi Albert,

I am totally daunted! :(

No, but this stuff does take time!
1- Gone to Tables under Objects and created a new Tbl
called Names. So now I have 2 tables: Legal Files and
Names.

Ok. I assume that this table "names" is going to be our new combo box
list..right? You then opened up this little table with ONE field, and
started typing in what WILL BE the combo box list. Each "value" for the
combo box will be one record in this little tiny new table.

So, you create the little table with one field, and then enter all the
values you want for the combo box.
2- Went into the underlying LFiles Table and in the Data
Type, it already had "Text" there, so went down into the
LookUp Tab (under Display Controls was Combo/Row Source
Type was Value List/Row Source were the names I had typed
when the LKUP Wd popped up) I've changed the DisplayC to
Text. Saved that and exited that.

Yup..that seems good.
3- Went to Forms where I already had a form Add New
Files. I now made another form to add New Names in the
future.

Why did we need a new form? The only possible change to the old form was the
combo box. I would have just deleted the combo box form the original form,
and then added it back using the wizard.
4-Opened Add New Files in DView, opened the toolbox, made
sure the wand was pressed; pressed Combo - chose ...values
in Tbl/Qu chose Names

Up to this point, this makes sense. And, hopefully you have already typed in
the values for that "names" table before you do this. .....so at least you
could see the results while using the wizard.
, which says Names-Unbound then

No, I don't recall anything about using un-bound things here. You are NOT
going to using a un-bound control. (un-bound means that the control is not
attached to a field in the forms underlying table. In your case...your
controls are bound to fields from the table as they always were.
deleted the old Names

Hum, what did you delete? You mean you deleted the old names combo
box...right?

If yes..then you are doing great...but that "new" combo you added needs to
be set, or attached to the correct field in LView table.

....poooff when I went into Form View,
names gone. (real sad face)

As mentioned, your "names" field is going to be bound. By the way, that
seems like not a very good name here. I would use something better then
"names"...as that seems to hint at people's names...and it would be hard to
believe that you are storing names inside of a "value list" in side of a
field?

You had an original database with a SINGLE table with some data, and a combo
box. That combo box was a simply "list" of values that you had typed in when
you created it (you called this names for some reason). Our goal here is to
simply take that simple little list for the combo box and move it to a
table. It will not really change how things work...but it means we will be
able to add to the list without having to open the form (or table) in design
mode and add more entries to that combo list. Now, we will be able to simply
add to that combo list by opening up our names table, and adding new entries
into that new simple table you called names.
Didn't go any further as that seemed to be "quite" enough
(!)

Remember, the ONLY thing we are dong on the form is removing the original
combo box,a and then adding that same "names" control back, but we use the
wizard. So, when we use the wizard, we grab the "list" of values from the
new "names" table, and the results are to be "saved for later use", and of
course that is going to be our names field in LView form.
Albert, the "Make care note" about left joins, not sure
what that is, though that doesn't mean that I haven't seen
it, just that I don't/didn't know the name. How do I get
that to appear to see what you're talking about?

You only need to worry about the above if you are using a complex combo box,
where the "id" is stored, but you display the text. This is a little
advanced for you right now. I thought you might be using query builder and
more then one table for your combo box. (you where NOT..so..don't worry).
However, we are NOW going to use and have two tables in the database.
However, in your case, your simple list of values for the combo is in a
simple table called "names", and we don't have to do anything special in
reports to "lookup" values from the other table (that is when the database
starts to get relational).

So, since that simple table for the combo box only has one field...don't
worry about the above "left join" until you start building queries for
reports, and ALSO ARE using multiple tables for that query.
So again, if you have any suggestions on how I've done so
far, apart from losing the names, I'll keep on going.

Bring up the form in design mode, and view the "list" of fields...and drag
and drop the "names" field onto the form...you should see the original data
no problem...

I suppose it is time give you the standard advice we all give:

You want to make a copy of your whole file before you try ANYTHING that you
are un-sure of). That way, you can always go back to the previous copy.

Also, you could have continued this thread on your original post...as it is
easer for me, or anyone else who might want to offer you help..
 
Hello,

Albert, I will be reading your last message this morning
and will get back with answers.

Kindest regards,
Linda
 
Back
Top