I'm wondering how stable a split database is? Currently I have 10 users on a sbs using access 97. They all need their own input forms, which all have various sub forms in them.
They keep getting messages to say that the forms they are using are being used already, and are locked, and all I can think of is that somehow the macros behind them are getting confused.
I don't know whether splitting the database so they each have their own frontend database would solve this, but I don't want to cause other problems in the process.
Would it be possible to have only the forms on the individual frontends, but have the queries, reports and tables on the backend? All I can find on the web is how to split it to have the tables on the backend and everything else on the front end.
I'd not recommend that approach. Remember that the code is run from the context of the front end application, so if you were to put the reports, queries and tables into either the backend database or another one, you would need to modify your code to specify where to open the relevant object from.
Certainly I've never had need to put forms, reports, queries etc in the back end.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.