Okay, JeffBuzz. I see what you are doing, but unfortunately, there is no
going around a requery.
The problem is that only the data entered into the form will exist in the
form's recordset. When you add data outside the form, it doesn't know about
it. The only way for the form to know about the data added to the table is
with a requery.

Signature
Dave Hargis, Microsoft Access MVP
> HI Dave,
> Actually, I am not adding new records. I am just updating....oh
[quoted text clipped - 8 lines]
> I am suspecting this is my problem. Is my only solution to requery? I
> wish I could just somehow refresh the one table.
JeffBuzz - 03 Apr 2008 16:43 GMT
Thanks for your help Dave. Looking throught the documentation, it
would appear that the "Unique Table" property is what would help solve
my problem. Unfortunately, I can seem to get that to work.
Klatuu - 03 Apr 2008 16:53 GMT
The Unique Table property only applies to adp files (an Access Project), not
to MDB files.
I sympathize with your frustration, but you are wasting your time trying to
get around this. If your form has an uneditable recordset and you add or
modify data in any of the underlying tables, the only way to get the modified
data into the form's recordset is with a Requery.

Signature
Dave Hargis, Microsoft Access MVP
> Thanks for your help Dave. Looking throught the documentation, it
> would appear that the "Unique Table" property is what would help solve
> my problem. Unfortunately, I can seem to get that to work.
JeffBuzz - 03 Apr 2008 16:57 GMT
So it seems. Thanks again for your help (and your patience) :-)
Klatuu - 03 Apr 2008 17:02 GMT
Wish I could give you the answer you want.
The only other thing you may consider is reforming your query so it executes
more quickly, but that may not be an option.

Signature
Dave Hargis, Microsoft Access MVP
> So it seems. Thanks again for your help (and your patience) :-)