ACCESS 2013 Database Increases in Size?

[ApexJim]

May I please ask for any help or suggestions from anyone to the problem I now have since converting from Access2003 to Access2013

BRIEF HISTORY
We have run an Access 2003 Shared Database (20 Users) on our local network server for over 8 years using Windows XP without any problems at all.

The Database is 258 MByte in size, with a variety of Tables/ Queries / Forms / Reports that any user on the network can call up as needed.
I have designed the database to meet the users needs and it has worked perfect over many years of constant daily use.

In Early December we upgraded the complete system and we are now using 2 Servers with Windows Server 2012 R2, The shared Database is located in its own partition on the Server Hard Drive with 4.89Gb Capacity -3.04Gb Free.
There are twenty users on the network, each with Windows 7 and MS Office Professional Plus 2013.

It is the same Database converted to 2013 format.

CURENT PROBLEM -- The Database is fine first thing in the morning and its size is approx. 258MByte, after about an hour to two hours of use its size increases to 280 / 290MByte quite quickly, also users then experience very slow operations and "Updating Tables" is shown in the Users PC screen bar.

We have to get all users off the network to compact and repair the database and it then returns to its normal size and normal operation.
This compact operation is now having to be done several times a day and I need to sort this out.

Can anyone help me to advise on the best possible solution to try?
Please remember that the same database has worked on the same network for over 8 years without fault on Office 2003 and XP based machines with the same 20 users.

Someone must have experienced this problem when upgrading to 2013?

All help will be appreciated to look for a solution

Thank You

 

[llkhoutx]

Access has historical bloat issues which compact & repair usually fix. However, your "bloated" database is relatively small, well below the 2G maximum size.

Check and optimize your record locking options, i.e. via Access Options->ClientSettings->>Advanced.

Of course, is could be a server issue.

I assume that your database is split with the (data) back end on a shared server and the (program) front end on each users' PC.

 

[ApexJim]

Hi,
Thank you for your reply to my query.

What would be your suggestions for the Record Locking please in the advanced client options?
This is currently set to Open Database using Record Level Locking"

The reason I ask is the database is not split and all users share the single Database from the server, they call it up by a shortcut on their individual PC Desktop.

Locking I believe currently prevents corruption occurring during any collision aspects when two users are trying to work on the same table?

Using the single database allows me to add /modify in a very easy manner in the evening time and just replacing the main database on the network in the early morning prior to any daytime usage .

I appreciate that splitting it to a FE / BE would add security and many other benefits, however as I have not had any problems in over eight years of use on the old network it has never been a priority or a requirement to split., but I do appreciate the reasons for FE / BE

The only problem is the current "Bloating" and once I know what is actually causing it I will do anything required including splitting to a FE / BE as a solution for it to be stable in the new Office 2013 environment.

Do you know what "Updating Tables" refers to in Access when random users see this on their PC cursor bar, as when this happens the database is unusable and this is when we have to ask all users to come out of the Database to allow us to Compact and Repair.

No users are ever actually "Updating Tables" , although they may be adding small amounts of new records during the day to certain tables.

Thank you for your help on this query and any views, if you have the time to reply would be most welcomed.

Kind Regards
Jim

 

[spikepl]

Google is your friend. Remember that next time prior to asking - a huge majority of issues have been encountered by others.

Read this thread in its entirety: http://www.experts-exchange.com/Database/MS_Access/Q_24540947.html#view-all

 

[jdraw]

Read this info from FMS
1) http://www.fmsinc.com/MicrosoftAccess/DatabaseSplitter/Index.html
2)http://www.fmsinc.com/MicrosoftAccess/Performance/LinkedDatabase.html

 

[ApexJim]

Thank You jdraw for your information links - they are very good
Jim

 

[ApexJim]

Thanks spikepl for your advice
I cannot read the answer on the link you gave me unfortunately, unless I join that network, would you suggest I do to achieve the benefit?
Thank You
Jim