Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations TouchToneTommy on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Database splitter

Status
Not open for further replies.

domino3

MIS
May 20, 2003
307
GB
I would like to know if it is possible to split an access 97 database into front and back end, as it is with access 2000.

Thank you.
 
Thank you.

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.

Any advice would be gratefully received.

Thanks.
 
Very stable, just make sure that you have all the forms set to optimistic concurrency (no locks).

John
 
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.

John
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top