Sub-Form no Longer works

[Gretchen]

I have a database that has been in use for about a month. There is a subform attached to a form and all has gone fine until now. Now when try to enter information in the subform, get the following message that I cannot figure out what's wrong.

You Can't Assign a Value to This Object
*The object may be a control on a read-only form
*The object may be on a form that is open in design view
*The value may be too large for this field

None of the above are true statements!

Also, the subform auto id no longer matches the form id (which is linked to the master database)

H e l p !!! Am totally lost on why this isn't working any longer.

Appreciate all ideas

 

[Jack Cowley]

First try a compact and repair. If that fails then try running JetComp.exe (available as a download from the MS KB). If that fails try importing everything into a new, blank db and see if that fixes the problem....

hth,
Jack

 

[Gretchen]

Thanks! I'll try those and let you know how it goes! Appreciate you taking the time to help!

 

[Gretchen]

!

Oh no! None of the above ideas worked. I did them all, in the order given. Still get same message! Help!!! Need more ideas!!

 

[rube]

Do you have any restrictions either in code, on a control or form.


i.e. AllowEdits or AllowAdditions=False

And do you remember any changes you made right before this started happening? It is easy to make one change for an action, that then prohibits a previously working action.

Final question, what do you mean the autonumber field and sub are no longer the same - name or data?

 

[Jack Cowley]

My only other suggestion is to rebuild the subform from scratch. You may want to import the required tables/queries into a new db and re-create the form/subform and if it works then import everything else into the new db. Your subform or form may be corrupt.

hth,
Jack

 

[Gretchen]

Argghh this is going from bad to worse

Settings are:

Allow Edits = Yes
Allow Deletions = Yes
Allow Additions = Yes
Data Entry = No
Recordset Type = Dynaset
Record Locks = No Locks

Still getting same message when try to enter subform data for new individual. Can make any changes desired or add information in any user that was previously in database. It's only newly added people in the Master DAtabase which this database links to. And now I'm finding it's a problem in another database! The other database has been in use for nearly a year now and has worked perfectly. I have made no changes in either one. I am exasperated!

To answer the question re autonumber field not matching. The master dbase has primary key of Auto and the law dbase has primary key of AutoID (as does the GCCLF dbase). I have made the relationship between those 2. Previously when a user was added to the master dbase and was pulled into the linked dbase, the auto and autoid matched. Now however they do not.

Any more ideas? (I did try recreating from scratch and still get same problem)

 

[Jack Cowley]

I am stumped as well, but the fact that the ID's do not match is interesting. Are you saying that the Primary key and Foreign key are no longer in sync? I am not sure how that can be because if the primary key is 7 then all records with 7 as their foreign key will (should!) show up. Are you saying that if you select the primary record with 7 as its key it does not show the correct records from the linked table?

I am off until about noon Pacific time but I will check-in when I return.

Jack

 

[Gretchen]

Yes (I think) that's what I'm saying. If Sonya Robinson is Auto 8233 in the Master Dbase, when I pull her up in the linked Law Dbase, the AutoID does not show anything or some odd number like 7129. Previously the Auto 8233 would show as 8233 in the AutoID as well. All the other records are that way.

p.s. Jack, sent you pm re all this