Link to home
Start Free TrialLog in
Avatar of Davisro
DavisroFlag for United States of America

asked on

Open Access form without locking the back end

Experts,

I have an Access split database with a form that has a record source that is a crosstab query. When I open the form and do nothing else, the query runs and populates the form, and also locks the back end. I want to leave the back end unlocked so I don't have to call everyone who may have the form open in the database and ask them to close their client before I can make changes the the back end.

How do I open the form without locking the database?

Thanks
Avatar of Gustav Brock
Gustav Brock
Flag of Denmark image

You can't. You have to have users to exit the frontend before modifying table schemas in the backend.

/gustav
I'm not sure what types of changes you are trying to make to the BE?  if the changes have to do with the cross-tab query, those changes should be in the FE, not the BE.  And if you are pushing the results of a crosstab query into another table, then that table should also be in the FE (or because it would be 'temporary', possibly in a separate temporary table in a separate database file that the FE is linked to).
1. When a bound form is open, there is a connection to the BE and so the BE is locked.
2. NEVER make BE changes during the work day unless it is an emergency.   Making changes to the BE requires that all users exit the database and during the work day, you can't be sure that no one is going to try to get back in before you are finished.  Schedule your BE updates for off hours.
3. I presume that you always make a back up of the BE before you start any schema changes.
Avatar of Davisro

ASKER

I inherited this application and the prior developer created a data input form that
1. Users select criteria (Contractor ID, Name, PO Number Etc) on a filter form
2. Command button runs a make table query to copy only the selected records from the master table to a local table and opens a details form that is bound to the local table to view records.
3. Users updated form fields and submit changes via command button which opens recordsets to copy the fields to an audit table (before and after submit), and to the master table

Looking at this setup, it seemed to me that the significant time and effort invested in programming it was to keep the back end closed, and only open it to post a transaction (in this case updating or creating a new record in the master table).  I have since added new forms to this database and set them up the same way, but...

I suppose, based on your comments, that its not a best practice to use unbound forms and only open the back end when posting data to tables?
ASKER CERTIFIED SOLUTION
Avatar of PatHartman
PatHartman
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial