Split database Queries/Forms not updateable.

[Guest]

I have a split database. Many users have a copy of the FE (front end) on
their desktops and work in it daily. The BE (back end) data tables reside on
a shared drive on our network.
Everything has been great for 1 1/2 years until today!!!

All of a sudden if you open a query or form it is "read-only" and won't
allow you to update the fields. We can still update the table though.

I have ran the compact/repair tool and it did not fix the problem.

Any idea why queries/forms would be read-only all of a sudden and how to fix
it?

 

[Joseph Meehan]

I have a split database. Many users have a copy of the FE (front end)
on their desktops and work in it daily. The BE (back end) data
tables reside on a shared drive on our network.
Everything has been great for 1 1/2 years until today!!!

All of a sudden if you open a query or form it is "read-only" and
won't allow you to update the fields. We can still update the table
though.

I have ran the compact/repair tool and it did not fix the problem.

Any idea why queries/forms would be read-only all of a sudden and how
to fix it?

Most likely the security settings on the LAN were changed and now they
users lack full access to the directory where the back end is maintained.
They need read, edit, create and delete. It is also possible the file was
made read only. Check both the MDB and the LDB file if present.

 

[Guest]

To get to know more about the issue, more data is required.
is this happening on all the computers?

what changes had been brought in your policies, network or windoes
administration?

 

[Guest]

There have been 0 changes on our network. We were working fine and then
nothing all of a sudden nothing. I have 4 databases split all with the BE on
the same exact shared drive and this is the only one having a problem all of
a sudden.

I even tried merging it backinto one database instead of it being split.
And the same thing is happening. You can edit from the table, but not from
the queries or forms. If I try making a brand new query the same is true.

 

[James Mc Diarmid]

Not a lot of info about this problem.

I had a similar problem a whaleback with a combo box using an inner join
query.

A record was damaged and once this was corrected, the combo box once again
worked.

I wrote a process that checked every field in every record.

My 2 cents worth, hope it helps.