Subform Not Allowing Data Entry

[Guest]

XP Pro Office 2003 Pro

I have a table tblClient_InfoV1

A query qryClientNameV1 that pulls ClientID (primary key), LastName,
FirstName from tblClient_InfoV1 and creates ClientName

A form frmClient_InfoV1 based on tblClient_InfoV1

I can enter data in all the forms fields and it all posts to the table

I created a form frmClientMasterV1 from the query with ClientID and
ClientName at top of page. Then I added a tab to the form and added a
subform on the tab created from frmClient_InfoV1.

When I try to enter data in the LastName field subform I get Msg:
"You can't assign a value to the object
*The object may be a control on a read only form
*The object may be a control on a form open in design view
*The value may be too large for the field
The last two may be s are not the case and I don't think the first is valid
either, but not sure how to confirm that.

What might be my problem?

Thanks

 

[Guest]

Shep -
I am not an expert like some of the guys in this group so you may get more
technical advice than this, but I can tell what worked for me!
I had 6 subforms sitting on tabs, just like your situation. I struggled with
this for 2-3 weeks and was at my wits end and could not get help via this
group.
In the end this was what I did differently from my original build:
I had created each form independently based on its own table, and when I
added a tab page and created a subform on it, I had used the "use an existing
form" option. I had exactly the same problems as you. I was refused entry to
any field for input, getting that error msge you described, and even I did
over-ride that by clicking OK, the data didn't store in the table.
Solution:
Instead of that route when adding the subform, use the option: "from tables
or queries". It means you are starting again with your form from scratch -
selcting all the fields you want and laying them out on the new form, and not
using the standalone form you already built, so it's a bit frustrating as you
have already done it once but hey - it worked for me and resolved endless
frustration.
Hope it works for you too!
CW
(my first response to a post - everything up until now has been a question!)

 

[Guest]

Shep -
I am not an expert like some of the guys in this group so you may get more
technical advice than this, but I can tell what worked for me!
I had 6 subforms sitting on tabs, just like your situation. I struggled with
this for 2-3 weeks and was at my wits end and could not get help via this
group.
In the end this was what I did differently from my original build:
I had created each form independently based on its own table, and when I
added a tab page and created a subform on it, I had used the "use an existing
form" option. I had exactly the same problems as you. I was refused entry to
any field for input, getting that error msge you described, and even I did
over-ride that by clicking OK, the data didn't store in the table.
Solution:
Instead of that route when adding the subform, use the option: "from tables
or queries". It means you are starting again with your form from scratch -
selcting all the fields you want and laying them out on the new form, and not
using the standalone form you already built, so it's a bit frustrating as you
have already done it once but hey - it worked for me and resolved endless
frustration.
Hope it works for you too!
CW
(my first response to a post - everything up until now has been a question!)

Many thanks CW, that is good to know.
Meanwhile, I added a casenumber to table and on form created an event to
auto assign a case number by clicking a command button. That creates record
and lets me enter data. I don't know why, but it works.

Best Regards