Hi,

We have a database running with a split FE/BE with the front end running
on users machines distributed via Tony Toews' AutoFE Updater (great
utility). Front end is a compiled/decompiled/recompiled MDE...

This has been running without problems/corruption for about 8 months.

Yesterday morning, we released a new version to our users. The backend
changed slightly and various new forms in the front end.

During most of yesterday, people used the new version without problems.

At some point during yesterday, one of the 'admin' users made some
changes to the security.mdw file, but forgot to lockout the db first.
(The mdw file is in the front end directory)

The effect at the time appeared to be to stop people opening certain
forms, access appeared to hang when they tried to open them.

This seemed to be sorted by getting everyone out and making sure lock
files were removed.

Overnight, the mdw file was updated via a terminal services session
which, unfortunately, timed out leaving the db in a strange state again.

This morning, I terminated that session.. checked the open files on the
share with the back end to make sure no one was connected.

The situation I am now in is very strange...

The first person into the database can use it normally.
Subsequent people can open the switchboard (which is in the FE) and some
forms (BE), but not most of the forms. When they open them, access
appears to hang, but, in fact, they appear to be waiting for a lock. If
the first person who opened one of the failing BE forms exits it, then
one of the others gets into it.

So, its like an exclusive lock has been applied to some forms (a lock
with a wait). But exclusive locking is not showing as set anywhere.

I tried various things and then decided to back out to the working
version applied yesterday morning, but they now gives the same symptoms.
Very strange....

I then set up a new test environment using AutoFE with a completely
different FE directory and a different location for the BE, but the
problem is still there.

If I wasn't sure that multiple people were successfully using the db
yesterday morning, I would be convinced there was a locking problem in
the db. However, multiple people were definitely using it yesterday and
the same version (Zipped just prior to implementing) now seems to have
this locking problem.

I will carry on debugging tomorrow, but I would love to hear any
suggestions from anyone as to what might be causing this. I thought
maybe a windows locking problem, but some forms can be opened by
multiple people on the back end.

The share is on a Win2K server, the clients are Office 2000 running on a
mix of WinXP and Win2000 machines.

Sorry about the length of this post. Any advice gratefully accepted...

Cheers