A2003 Backend opens in read-only intermittently

[Rudy]

I'm running A2003 with BE and FE DAO. Twice over the last three months the
BE has opened as read-only. We can view all data, but when we try an update
of a record we get a message saying the databse is read-only. Other
programmed error messages are appearing because of the read-only status.

Any ideas on what causes this. Anyone else have this happen?

[John Mishefske]

Rudy wrote:

I'm running A2003 with BE and FE DAO. Twice over the last three months the
BE has opened as read-only. We can view all data, but when we try an update
of a record we get a message saying the databse is read-only. Other
programmed error messages are appearing because of the read-only status.

Any ideas on what causes this. Anyone else have this happen?

Sounds like it could be a permissions problem. Is it always the same user?

--
'---------------
'John Mishefske
'---------------

[Charlie]

No. It's not a single user, but all users. The BE is read-only to everyone.
Could this be a JET hiccup?
"John Mishefske" <jm**********@SPAMyahoo.com> wrote in message
news:bP*******************@tornado.rdc-kc.rr.com...

Rudy wrote:

I'm running A2003 with BE and FE DAO. Twice over the last three months
the BE has opened as read-only. We can view all data, but when we try an
update of a record we get a message saying the databse is read-only.
Other programmed error messages are appearing because of the read-only
status.

Any ideas on what causes this. Anyone else have this happen?

Sounds like it could be a permissions problem. Is it always the same user?

--
'---------------
'John Mishefske
'---------------

[John Mishefske]

Charlie wrote:

No. It's not a single user, but all users. The BE is read-only to everyone.
Could this be a JET hiccup?

Make sure that the read-only attribute isn't set on the BE .mdb. Sometimes copying this
file from a CD will maintain the read-only attribute.

The other thing that comes to mind is the permissions on the BE .mdb file are not
permitting users to change the file.

--
'---------------
'John Mishefske
'---------------

[Charlie]

Thanks for the inputs.

I checked the file properties of the BE file and read-only was not set.

Also the permissions were set for read/write.

There was no changes to the programming of the FE or the BE file when this
occured. It was the same FE and BE used the previous day which worked
correctly.

Could the backup program for the database cause this to happen?
"John Mishefske" <jm**********@SPAMyahoo.com> wrote in message
news:vq*******************@tornado.rdc-kc.rr.com...

Charlie wrote:

No. It's not a single user, but all users. The BE is read-only to
everyone. Could this be a JET hiccup?

Make sure that the read-only attribute isn't set on the BE .mdb. Sometimes
copying this file from a CD will maintain the read-only attribute.

The other thing that comes to mind is the permissions on the BE .mdb file
are not permitting users to change the file.

--
'---------------
'John Mishefske
'---------------

[John Mishefske]

Charlie wrote:

Thanks for the inputs.

I checked the file properties of the BE file and read-only was not set.

Also the permissions were set for read/write.

There was no changes to the programming of the FE or the BE file when this
occured. It was the same FE and BE used the previous day which worked
correctly.

Could the backup program for the database cause this to happen?

Perhaps; I've never seen that happen. Is there a lock file (.ldb) remaining after folks exit?

Is this Access 2000 running under XP operating system by any chance? There is a known
problem with Compact on Close if running those versions.

Might search Google Groups. I'm sure this has happened to someone before.

--
'---------------
'John Mishefske
'---------------

[Charlie]

No. This is A2003 on XP.

There was no ldb file last time this happened. However, when I tried to do a
compact and repair the standard message came up saying there were users.

Thanks for in input and ideas.

"John Mishefske" <jm**********@SPAMyahoo.com> wrote in message
news:KR*******************@tornado.rdc-kc.rr.com...

Charlie wrote:

Thanks for the inputs.

I checked the file properties of the BE file and read-only was not set.

Also the permissions were set for read/write.

There was no changes to the programming of the FE or the BE file when
this occured. It was the same FE and BE used the previous day which
worked correctly.

Could the backup program for the database cause this to happen?

Perhaps; I've never seen that happen. Is there a lock file (.ldb)
remaining after folks exit?

Is this Access 2000 running under XP operating system by any chance? There
is a known problem with Compact on Close if running those versions.

Might search Google Groups. I'm sure this has happened to someone before.

--
'---------------
'John Mishefske
'---------------