In trying to work out another problem I have discovered that one of my forms is suddenly read-only.
I have checked the design view and allow changes, edits, deletions are all marked yes.
In trying to work out another problem I have discovered that one of my forms is suddenly read-only.
I have checked the design view and allow changes, edits, deletions are all marked yes.
Last edited by Karen H; 02-10-2011 at 02:00 PM. Reason: attached to wrong post
Why do you feel the form is read-only? Can you modify the RecordSource directly?
I am not sure what "record source" means but I can modify the records under table view, cannot make any changes on the form. Any attempt to modify or enter data on a form results in a bell, no messages just a bell.
On the property sheet for the form under the Data tab is a RecordSource property. If you press the "..." button on that property, can you then modify the RecordSource?
Nope, that will not work either
If it is a query then this link might help: http://allenbrowne.com/ser-61.html
I had originally created the table with 58 fields. I decided that I should separate some of the fields that would be rarely used so that I could access the basic data more quickly.
Now, everytime I add the third table to the query it becomes read only.
Have you looked at the link I posted in post #6?
Yes, I did check out the link you sent, the only thing that it could be is the join could be wrong. This response was after I checked that out.
I had originally created the table with 58 fields. I decided that I should separate some of the fields that would be rarely used so that I could access the basic data more quickly.
Now, everytime I add the third table to the query it becomes read only.
Access make the query read-only when the record is ambiguous. Take a closer look at how you joined the tables. Is there a PrimaryKey (PK) in one table and the same value in a field in another table as a ForeignKey (FK)?
Yes, there is.
When I split the data up, I copied the whole table again and deleted all the fields I did not need in each new table. I changed the PK to be an FK.
Each of the FKs has the same id numbers that were in the original table.
Also, on a related note, one of the tables won't hold the relationship. it will take it, I save the relationship window and exit and come back in and the relationship is gone.
I fixed the relationship issue, when I said show all, there were 8 different sets of relationships for that table, after deleting all but one everything having to do with the relationships is ok, but everything is still read only.
Let's try and eliminate corruption as an issue. *Import* your db into a new fresh db and see if the relationship issue follows: http://www.btabdevelopment.com/ts/impnew
I followed the link you sent and imported the way they said to, I have just been copying and giving a new name. But, alas, still no change.
Hi Karen,
Is it possible to do a Compact and Repair and then zip up your db and attach it to a post here? Remove any sensitive data of course.