Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Westi on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Just want to make a simple Look Up control on a form

Status
Not open for further replies.

Dontremb

Technical User
Jan 22, 2009
77
US
I don't know why I can't do this.

I have a form with 3 tables as a source (linked, and one subform).

I am just trying to make a simple look up field on the form, so I can search for a record by name.

I tried doing the combo box wizard, but the option to make a lookup isn't there.

I checked my other form, (which is pretty much exactly the same, except the form and subform are in opposite positions) and that look up works fine, and I tried to make another look up in that form just to check and make sure I wasn't crazy, but the wizard works fine in that form.

It just doesn't have the third option in the combo box wizard for my new form.

Any ideas?
 
There must be a problem with your relationships.

Your source for your form comes from a query that contains 3 linked tables correct?

What is the source of the subform?


 
How are ya Dontremb . . .
Dontremb said:
[blue] ... (which is pretty much exactly the same, except the form and subform are in opposite positions) ...[/blue]
The [blue]recordsoure[/blue] of your Form/subform combinations should follow your [blue]table relationships[/blue], where the mainforms recordsource comprises the [blue]parent table[/blue] and the subforms recordsource the [blue]child table[/blue]. Its a [red]very bad idea[/red] trying to work in reverse relational order.

[blue]Your Thoughts? . . .[/blue]

See Ya! . . . . . .

Be sure to see thread181-473997 [blue]Worthy Reading![/blue] [thumbsup2]
Also faq181-2886 [blue]Worthy Reading![/blue] [thumbsup2]
 
Hrm... Unfortunately, I'm a bit new to doing correct relationships. My years of Access experiences was pretty much limited to one-to-one relationships.

My source is 3 tables, in a many-to-many relationship. That's why I thought it would be ok to do these two forms.

Tables:
Personnel
Vacancies
Compilation (Which is the table that links both of the other tables in a many-to-many relationship.)

The first form (with subform) shows the Job Vacancy in the main form, then the subform shows information about all the people in the Personnel table who applied to that job. It also shows (in that same subform) some information from the tblCompilation where necessary.

The second form, which I'm working with right now, (which works great, btw, except for the lookup.) Is just the opposite, the main form shows a Person from tblPersonnel, and the subform shows all the Jobs from tblVacancies that the person has applied to, (plus some info from tblCompilation where applicable.)

I've heard a few people mention parent-child, but I must admit, that I don't really understand that term very well.

Also, (though this is more of an annoyance) I have to manually refresh at just about every step in this database. It's very annoying. I've tried putting code into it to make it Requery, but it doesn't EVER seem to work. It Requeries, it just doesn't actually refresh any of the data. But that's not really what this question is about.

 
Dontremb . . .

If you wanna know what your doing be sure to critique the following:

Fundamentals of Relational Database Design

Normalizing Tables

Table Relationships

If you don't want to bother, you'll see this thread fall into the dust. This is must know stuff. I'm sure when your done reading you'll make some changes in your design and start a more informed thread . . .

[blue]Your Thoughts? . . .[/blue]

See Ya! . . . . . .

Be sure to see thread181-473997 [blue]Worthy Reading![/blue] [thumbsup2]
Also faq181-2886 [blue]Worthy Reading![/blue] [thumbsup2]
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top