Speed performance tips for split database

scubadiver007

Registered User.
Local time
Today, 07:45
Joined
Nov 30, 2010
Messages
317
Hello,

I have a database with 14 tables which I set up for a small local recruitment company. As you can imagine they do a lot of adding, updating of records as well as doing searches.

I split the database into a back end with the tables and a front end for each consultant with the forms and queries plus links to the tables.

Q1) My subforms use the tables as the data sources. Is it better to use queries?

Q2) How do I compact a split database?

Any other tips?

Thanks
 
1. you should use queries. you can filter , and sort queries in ways you cannot directly with tables

2. you shouldn't need to compact the back end regularly/hardly at all. if it is growing too much, it maybe a design issue. do you store images in the dbs?
 
2. you shouldn't need to compact the back end regularly/hardly at all. if it is growing too much, it maybe a design issue. do you store images in the dbs?
I am not sure about hardly at all part. If there are more than 5 users making continuous read/write or even deletes, I think it would make more sense to perform a Compact & Repair atleast once a week? To free up garbage space and clean up any unwanted stuff lurking around?
 
In SQL Server, the tables are not connected but are created using SQL (which has been my experience anyway).

Does having established table relationships in the BE create problems for performance and speed?

I am wondering whether it might be better to have separate tables in the BE of an Access database and to update the records in the forms maybe using append queries.

Or is this more hassle?
 

Users who are viewing this thread

Back
Top Bottom