Amending Split Database

Question

I have split my Database and provided forms to users and have a .be file on server.  I need to add a field to back end table, but access keeps opening table as read only. "This database has been opened read-only.  You can only change data in linked Tables.  To make design changes save a copy of the database."  I thought that splitting the database, (Access 2016) was to allow changes to be easily made to the table whilst others had forms opened.  Am I missing something?  Once I add the Feld I will then amend my forms and provide the updated for to users.  Also intermittently the forms open with no fields visible.

On another matter, I would love to find an online workshop / training forum to interact in real time.

Answer 1

In order to make a design change to a BE table, you open the BE, then design the table. You don't go through the FE. Before you do so, make a backup of the BE, just in case something goes sideways. You always want to be able to roll back.

In order to be able to make design changes to a table, you need to have exclusive access. So if users have forms or reports open on the same table, you have to first kick them out, then quickly make the change.

Usually design changes mean that the FE will also be updated, so this can be part of a larger deployment of the new version.

Answer 2

Reading between the lines, you kicked all users out, made a backup of the BE, and changed the BE. All just like I suggested.

Good. That is all you need to do.

If you then open the FE, 99% chance the table changes will be reflected automatically. If not, use the Linked Table Manager to refresh the links.

Answer 3

Hi Baldrics, I'm an independent adviser and will try to help.

Yes splitting the database DOES allow users to make changes to the data. But it does serve as a problem in modifying the tables in the back end.

There are two possibilities here. The first (and the one I usually use), Is to block users from using the application while you make the changes. Usually, I make the changes in my development back end, test them with the new front end. Then I block users from using the back end while I duplicate the changes.

The other alternative is SQL DML statements to modify the tables. The ALTER TABLE statement may allow you modify a table even while its in use.

If you need further clarification on this feel free to ask.

Answer 4

In order to make a design change to a BE table, you open the BE, then design the table. You don't go through the FE. Before you do so, make a backup of the BE, just in case something goes sideways. You always want to be able to roll back.

In order to be able to make design changes to a table, you need to have exclusive access. So if users have forms or reports open on the same table, you have to first kick them out, then quickly make the change.

Usually design changes mean that the FE will also be updated, so this can be part of a larger deployment of the new version.

Thanks Tom, I saved the database as stats v3.1 updated, made my changes and now want to make this work with my linked table / Forms.  I am trying to save as, and overwrite the original BE, as that is what all form are linked to. 

But this is what I get.;  No one has the table or forms Open.  This seems at odds with al rules of naming or replacing a file.

I don't understand!