"Linq Adams via AccessMonster.com" u28780@uwe wrote in message
news:9f2ccd955cfda@uwe...
| I'm not exactly sure what you mean by
|
| "It will not permit data entry either from the parent form or from the
| subform itself."
|
| Can you add/edit data on the main form? If the main form is Read-Only
you
| won't be able to Add/Edit records in the subform.
|
| --
| There's ALWAYS more than one way to skin a cat!
|
| Answers/posts based on Access 2000/2003
|
| Message posted via AccessMonster.com
| http://www.accessmonster.com/Uwe/For...forms/200911/1
|
What I meant was: When trying to type in any field of the subform, either
by having opened the parent form or just the subform itself, I received a
beep and the cursor didn't move or change.

I then opened the query builder from within the subform as I have said.
I could see the records. I proceeded to the new record row and began
typing dummy data. No objections or beeps and the cursor jumped to
the next field as expected. I didn't try to save the dummy data but I was
allowed to enter it.

I have since had to add fields to underlying tables and I created a new
lookup table as well. I also had to add controls to the subform. That's
when I opened the query from the database window. I removed one join
from the query and added the new one for the lookup.

Now it works. It appears that somehow the join I deleted was making the
data unupdatabe.

Thanks for your help, Linq. I'll keep my eye out for your cat.
--
Len
__________________________________________________ ____
remove nothing for valid email address.