Suddenly CAN'T DELETE / EDIT Records ???

[kev100 via AccessMonster.com]

This is driving me CRAZY !

I'm doing some weekend work here.....

Have done some editing on an existing Access App.

Earlier...I had NO PROBLEMS editing / deleteting records......

I've been adding various features....but have NOT changed any edit settings
Anywhere (that I know of)....everywhere that I know to check in properties,
etc all have a 'YES" in the fields relating to allowing editing.

But now...it seems as if there is some sort of "MASTER" read-only switch that
has been turned on somewhere.

I can't edit / delete a field/record from anywhere (not from any of the
queries, forms, tables...nothing)....it justs gives that irritating little
chime and says "read-only" at the bottom when I try.

I can open up a copy of the app Before I started adding various items....and
edit/deleting still works fine there.

The only thing I can think that it MIGHT be related to is a Custom Menu that
I created.....but I've since Completely DELETED that and am using the
original defualt one....but still...nothing!

Does anyone where/what I could have possibly changed that would be causing
this?

Thanks very much.

 

[Allen Browne]

1. Close Access.

2. In the Windows Explorer (My Computer), open the folder containing your
MDB.
See if there is an LDB file there with the same name.
If so, delete the LDB. (It will be a very small file.)
The LDB contains locking information for the MDB. Normally Access deletes it
on exit, but after a crash you can be left with spurious locking info in
that file.

3. Still in Windows Explorer, right-click the MDB, and make sure the Read
Only box is not checked. Also make sure you have write-access to this
folder. (You may not have if you are not logged in as a local computer
administrator, or if the file is on a network.)

4. Open the database, and repair it:
Tools | Database Utilities | Compact/Repair

5. If that doesn't work, did you do anything with Access security?
Or with replication?

6. Still stuck? Create a new MDB, and import everything from the failed one.
Steps in the first symptom of:
Recovering from corruption
at:
http://allenbrowne.com/ser-47.html

 

[kev100 via AccessMonster.com]

6. Still stuck? Create a new MDB, and import everything from the failed one.

Steps in the first symptom of:
Recovering from corruption
at:
http://allenbrowne.com/ser-47.html

WHEW !!!

Thanks SO MUCH !

That one worked.....what a relief...I was already dreding I was going to have
to redo all of today's work.

Thanks Very much !

 

[dabaum]

I am having a similar problem. I am working on the design master for a
replicated database. I was assigned to update some forms and table designs.
It has a frontend and Backend data file. I finished making the design
changes and tried to synchronize the program and the backend file was changed
but none of the form designs/queries/reports/modules were carried over to the
front end. Then the original front end stopped working as well as the design
master.

I created a new mdb from the replica parent made it the design master and
imported the tables from the bad one. Now despite the code being the same,
my I can't edit the recordset. I can post the code if needed... I'm at a
standstill though until I can figure this out.