> Yes, I tried joining them in a query and then using the query as the
> control
> souce. When I did this and went to view my form, it would be completely
> blank. Perhaps I am doing something wrong...
Unless the query is updateable, you will not be able to see or enter new
records. Make sure that it is, if you want to edit.
> As for a subform, I am not familiar with how those work. I understand how
> to create them on the form (subform control), but not sure how they
> interact
> w/the primary form.
From what I read below, a subform is your answer. You can see a sample of
how it works with the Northwind sample database that ships with Access. To
see it, look at Help >>> Sample Databases.

Signature
Arvin Meyer, MCP, MVP
http://www.datastrat.com
http://www.mvps.org/access
http://www.accessmvp.com
> The main purpose of this form is when the work crew gets a call for a
> sewer
[quoted text clipped - 9 lines]
>
> Thanks
cktia - 13 Nov 2007 17:38 GMT
Please bare with me - I am attempting to use a subform as you suggested. I
am wanting to have a popup Subform_B that you can use to search Database_B
and get all the manhole info that is already in that database. But - the
kicker is that when you close Subform_B - it automatically populates
Mainform_A in identical fields like the one searched. Yes, this makes
repetitive data - but, that is what is wanted. Any ideas? I appreciate any
help!!! :)
> > Yes, I tried joining them in a query and then using the query as the
> > control
[quoted text clipped - 25 lines]
> >
> > Thanks
Arvin Meyer [MVP] - 14 Nov 2007 15:11 GMT
I only bare in the shower, but I'll try to bear with you. <g>
A subform is an integral part of a main form, not a separate popup. Are you
trying to retrieve some data, then duplicate it? Do you want to be able to
make changes to the new record before you commit it to the database as a
duplicate (with new information)?
A word of warning. Retrieving some information from a record which will be
duplicated in a new record, along with some new information is OK. If it's
an exact duplicate though, all you really need is a new ID value and perhaps
a field or 2 to show a difference (like the date entered). In that case,
Table_B only needs to store the ID from table_A and the additional
information.

Signature
Arvin Meyer, MCP, MVP
http://www.datastrat.com
http://www.mvps.org/access
http://www.accessmvp.com
> Please bare with me - I am attempting to use a subform as you suggested.
> I
[quoted text clipped - 42 lines]
>> >
>> > Thanks
cktia - 14 Nov 2007 15:28 GMT
hehe...Sorry about that - I blame not spelling "bare/bear" correctly on
having just gotten out of the most boring meeting ever and then trying to
immediately be coherent. Good news though - I believe that I have gotten the
main form/subform working as I wanted it to. Thanks for your input regarding
subforms - that is what I used.
> I only bare in the shower, but I'll try to bear with you. <g>
>
[quoted text clipped - 55 lines]
> >> >
> >> > Thanks