Problems with multi user access

[GT1]

I have a back-end .mda file sitting on a network server, with a copy the front end application on each individual computer. Two people can open the database file at the same time, but they can't view the main form (based on a query) at the same time.

The second user just displays the hourglass, and waits until the first user has closed the form before it opens as normal. I don't receive any error message, it just waits.

All the other forms open Ok, with the exception of one which return the error : "There was an error executing this command"


This problem doesn't occur if I open two copies of the database on a single PC. I have tried all combinations of "record lock" settings, but nothing seems to work. Any ideas?

Cheers
GT

 

[JustLJ]

Check to see how they are opening it (from the File|Open selection) -- is their MSAccess open setting for "open" or "open exclusive"? To share nicely, they need to be set to "open".

Good Luck!

 

[GT1]

Thanks for the suggestion....Both databases are being "opened", and the settings under oprtions|Advanced is set to "Shared" on all (front end and back end files on all PCs).

I have narrowed it down to a problem with the form.

I can open two copies of the database (front and back) and all the reports/tables/queries and other forms without any problems. The only time it doesn't work is when I try to open the main form (frmTask)...if the back end file is already open (either directly or via another copy of the front end), it waits until it closes. I can open two copies of the underlying query (qryTask) without a snag!

This problem only occurs with this one form, and does not occur when I open two copies on the same PC. If I open the problem form first, I can still access the back-end file without trouble (just not the other way round!). I can't even open the form in Design view if the back end is open.

[The other error message I was getting has now gone away ]

I'd appreciate any suggestions on this!

Cheers,
GT

 

[GT1]

Ok, getting closer to the source.....

I gave up and created a brand new form, exactly the same as the original, copying & pasting the controls and code behind the form. Tested this and all seemed fine and dandy...until I compacted the database and suddenly the fault re-appeared.

Basically the un-compated version works, the compacted one doesn't! Not sure if this has any bearing on it??

Cheers,
GT

 

[grnzbra]

If it's not an overly complicated form, you might want to try creating it as an unbound form. When the form opens, a connection is created to the back end, a recordset is created and the connection is dropped. Field values are then moved to the form from the recordset. Meanwhile, someone else can open the form, create thier connection, fill their recordset and drop their connection. (That is a mojor oversimplification of the process, but it does give one an idea of the concept)