Name saving as ID

[TheDrescher]

I'm currently utilizing a combo box in my main form to select employee names
from a linked table. When the record is saved into the database table, it
shows the ID number from the table instead of the name from the field. How
would I correct this? Thanks!

 

[Marco]

Friends and friends around the world.
We are presenting the new messenger.
He will be in the commissioning by the friends that we indicate to use the
system.
Access the system by clicking the link below and register free.

You get something for using orkut?
You get something for using skype?
You gain something by using twiter?
You get algumaocisa for using facebook?

Enjoy this is your time!!

Sign up and join for free.


http://www.sqipcom.com/?ref=webempreendedor

http://stakeholder.sqipcom.com/user/webempreendedor

 

[Jeff Boyce]

From your description, the form and combobox are behaving exactly as they
should!

If you are looking at the table directly, you SHOULD see the ID of the
employee, not the name ... however, you should NOT be looking at the table
directly! Access tables store data, Access forms display it.

Use the forms, Luke!

Regards

Jeff Boyce
Microsoft Access MVP

--
Disclaimer: This author may have received products and services mentioned
in this post. Mention and/or description of a product or service herein
does not constitute endorsement thereof.

Any code or pseudocode included in this post is offered "as is", with no
guarantee as to suitability.

You can thank the FTC of the USA for making this disclaimer
possible/necessary.

 

[Linq Adams via AccessMonster.com]

SPAM

Friends and friends around the world.
We are presenting the new messenger.
He will be in the commissioning by the friends that we indicate to use the
system.
Access the system by clicking the link below and register free.

You get something for using orkut?
You get something for using skype?
You gain something by using twiter?
You get algumaocisa for using facebook?

Enjoy this is your time!!

Sign up and join for free.

http://www.sqipcom.com/?ref=webempreendedor

http://stakeholder.sqipcom.com/user/webempreendedor

 

[TheDrescher]

I see. My apologies, my Access skills have been woefully underused of late.
So once I run reports from this table I can make it display the name using
the ID as criteria. No issues there.

As a secondary question, the main page of the database is a form where most
of the information will be input/saved. I have two fields that automatically
populate based on the employee selected in the combo box using the Dlookup
function. When I save a record to the table, these fields are coming up
blank, is there any way I can have the text that automatically populates
saved in the table fields?

TheDrescher

 

[John W. Vinson]

As a secondary question, the main page of the database is a form where most
of the information will be input/saved. I have two fields that automatically
populate based on the employee selected in the combo box using the Dlookup
function. When I save a record to the table, these fields are coming up
blank, is there any way I can have the text that automatically populates
saved in the table fields?

Storing derived data such as this in your table accomplishes
three things: it wastes disk space; it wastes time (almost
any calculation will be MUCH faster than a disk fetch); and
most importantly, it risks data corruption. If one of the
underlying fields is subsequently edited, you will have data
in your table WHICH IS WRONG, and no automatic way to detect
that fact.

Just redo the lookup whenever you need it, either as a
field in a Query or just as you're now doing it - in the control source of a
Form or a Report textbox.

 

[Jeff Boyce]

What John said, but with more emphasis. JUST SAY NO!

Don't (re-)store the same info in another table. That's a very
spreadsheetly way of trying to use Access.

I'm guessing that you are trying to do this so you'll have all the data you
need for a report in one place (i.e., a table). Instead, use the relational
database relationally. Create a query that joins your related tables,
gather the employees' details, then base your report on that query.

Good luck!

Regards

Jeff Boyce
Microsoft Access MVP

--
Disclaimer: This author may have received products and services mentioned
in this post. Mention and/or description of a product or service herein
does not constitute endorsement thereof.

Any code or pseudocode included in this post is offered "as is", with no
guarantee as to suitability.

You can thank the FTC of the USA for making this disclaimer
possible/necessary.