Cant edit table design despite snapshot usage

[krausr79]

I have a split database made in Access 2007. Each user gets their own copy of the frontend from a script. I wanted to be able to edit the design view of the backend tables even if people were using the database so I made all the forms use snapshot source and only allowed data updates through VBA macro update queries. Having any form open locks the backend source table from being edited. In fact, I've found that just having a normal snapshot query open causes the message "Either an object bound to table 'whatever' is open or another user has the table open. Do you want to open the table as read-only?"

Is there some way to have a table be the source for a form or query, but still have it designable under most circumstances?

Edit:
Attempted to late-bind a recordset on form load; result was the same:

Set rs = CurrentDb.OpenRecordset("Select redacted as ft from tblRedacted ", dbOpenSnapshot, dbReadOnly)
Set Me.Recordset = rs
Set rs = Nothing

 

[DavidAtWork]

I think you may need to rethink your approach. You're defeating the object of a live database, you want users to be able to update data while also expecting to have the table(s) in design mode, no can do!
You need to plan some database downtime if you want to make changes during normal working hours or make the changes during non-office hours when you can open the back-end exclusively.

 

[krausr79]

The aim is not to design tables while users are working in them; the aims are:

1. Stability: By keeping users from being in tables (especially more than one at a time) I hope to avoid data 'car crashes' and table corruption.

2. To be able to change table design at all: Having users 'Out' of the database needs to be done manually. I have to run a Back-end macro to see who's truly in the database, since the lock file is a useless pile of anyone who's touched the data since anyone started. I then have to contact IT to see which user is (probably) associated with the given user tags (if they're not already on my list of know tags), and then contact them and tell them to exit the database and hope that they are not AFK for the day with their computers locked. With upwards of 20 possible users, this has not happened yet.

3. A matter of principle: The idea that people can lock administrators out of a database just by having Read-Only data open is poor design that I'm looking to work around, and I know I'm not the only person who wants this.

 

[spikepl]

keeping users from being in tables

Define "users being in table"

Having users 'Out' of the database needs to be done manually

Why? Search for "kick out users"

people can lock administrators out of a database just by having Read-Only data

Define "Lock out". Also, how can "people" themselves decide what type of data they want to have?

Be careful about what specific terms you use - we do not read minds