Have the backend in use only breifly

[krausr79]

I once made a split database with tables in the back end and read-only queries in the front end. I was hoping that the backend would only be in use when people ran the queries and otherwise would not be in use. That is, I would be able to compact and repair, redesign tables, write back-end VBA most of the time.

It didn't work. Even for read-only stuff, The back end was 'in use' for as long as anyone had one of the queries open. Is there a good way to acheive my original vision?

 

[jdraw]

You don't do maintenance on the backend when it is live (in operation). You either kick users out of the live system, or do your maintenance in off hours.

Ideally you have more rigor in your data management regime. You have some standards, and training and you isolate your development and production databases. You have a standardized backup procedure to prevent dat loss. You schedule maintenance and updates as releases. You test your changes thoroughly before applying to production.

You familiarize yourself with tips like these and these.

 

[Galaxiom]

Modifying a backend while it is in use is not a good idea.

You should work on a development backend then transfer the live data to it while the users are not connected.

There should not be any VBA in the backend.

 

[smig]

Backend should have tables only.

Normaly you make no developments and changes to the backend.

 

[krausr79]

I don't make changes while users are in it. I use a system that kicks users out based on the value in a table which works for 90% of all users. What happens is that if any of the remaining 10% are not at their desks at that moment, then the maintenance can't be done. I feel that if users were in and out instead of always in, that would go a long way to eliminating the problem.

Also, the VBA part was mostly an example. The only VBA I have in the backend is a routine to tell me who is actually still keeping me out of the backend. My original question still stands.

 

[gemma-the-husky]

as the others have said

the backend should include just your tables. you should not need to be working directly on these as a matter of course. maybe very occasionally to implement improvements.

in particular you do not need to be writing back end vba.