For those who have spent time considering,

For those who have spent time considering, planning, designing and construction an Access database then you will know the problems look at this developers face when deploying the finished database application.

Inside the development and style mode, your Entry database runs flawlessly! You are happy with enough time, sweat and effort getting each mind work nicely, present well and match the business workflows the particular database application was suitable for.

However suddenly you deploy and also implement the Access data source in the '

' natural environment only to your scary discover that end-users commence to complain why they have slow, why that keeps crashing or precisely why the function did not respond in any way.

-

Naturally, there many reasons why some of the above comes about but performance is a very important factor when coping with multiple users working together with your application.

If you have concurrent consumers accessing your data source, you have to ideally divide an Access database plus the following 5 factors may help to explain precisely why:

Additional benefits to splitting an Access data source but I think the above mentioned will be a good start.

How you split an Access database is simple enough - you'll find this in the Database Utilities and also Database Tools portion (depending which version you might be using).

Actually locate the actual Database Splitter Wizard software this will do the many hard work in your case!