Other users can't access their front end when I am editing a different front end

[cricketbird]

I have a split database. The back end is in a public folder on our network.

There are two front ends - one that is read-only (dozens of users), and one that is used to enter data (2 users). The users all copy their appropriate front end to their desktops and use it from there.

I am doing some developing (new reports, etc.) on my own copy of the data-entry front end. However, as long as I have my front end in design view, the read-only folks can't open their front ends.

Is this expected behavior? Can I change it somehow?

Here's a description I got from a read-only user:

After I ‘enable’ content – that same pop-up window appears saying it’s in use, then a ‘disable macros’ window.
Only the ‘disable macros’ is a valid choice – the ‘continue’ button is grayed out & I couldn’t select it.

The "read-only"ness is generated by having all of the fields on their forms be "locked" and hiding the menus, not via any network or permissions settings. A dedicated person could easily bypass my little system, but it works for us.

Thanks,
CB

 

[GinaWhipp]

Where is your development copy? SOunds like it might be on the network and the Users are using it instead of copying it to their local machines.

 

[Mihail]

Create a copy of the original BE.
ReLink your personal FE to this copy.

 

[cricketbird]

The FE that I am using is my own personal copy of the data-entry FE on my own personal hard drive - not the network (although it accesses the shared BE via linked tables).

I have verified that they are running the correct read-only FE directly from their hard drives (not a shortcut or other method).

Any other ideas?

 

[GinaWhipp]

You know I just *read* your message and realized something... Are these .ACCDB databases? If yes, then I suggest putting them in Trusted Locations and not on the Desktop. See...

http://www.access-diva.com/d4.html

 

[Mihail]

Read again, slowly this:

Create a copy of the original BE.
ReLink your personal FE to this copy.

 

[cricketbird]

These are .mdb files. I think Mihail came the closest. I first tried what Mihail suggested (making a new copy of BE and relinking my FE), and that didn't work. However, then I made a copy of my FE, and deleted then relinked the tables, and that seems to have fixed the issue. I'm not sure exactly how what I did helped, but perhaps something was corrupted and making fresh copies of both the BE and FE seemed to help (for today at least).

Thanks everyone
CB