In my access applications i have used the database split built in functionallity to split my frontend and backend tables.I have created a mail mechanism and when the database grows to that level i recieve a mail, ask users to get out of the database and compact the database. But this is tiding. I have a scheduled job that compacts databases early in the morning before users logged on. But during day work databases grow enormous again. Well is there a way by VBA code to create an auto compact function that on idle will log off all users in the database and compact it?
In month-end posting - I basically delete all the records from my transaction file. And in doing so - it seems to be resetting the auto number index - which is causing me major problems.
The resetting of the index after deleting all the records is normal.
I am working in VB 2010 - using a 2003 MS Access database.
Access 2013 ... Is it possible to compact a database to a new name?
(In previous incarnations of Access I regularly 'compacted and repaired' databases to USB sticks rather than simply copy the file in the (mistaken??) belief that this was a more reliable approach)...
There are between 10 - 15 users at one time. It is a shared network, the front_end is on individual hardrives and the tables are located on the server. We just converted to Access 2003, our data file size is 47kb.
Users who are not active in the database get disk or network error message and have to close out. Is idle time a possible factor? Some users maybe entering information sporadically through out the day, but need to have the database open, they may need to refer to a member record upon receiving a phone call.
I'm about to start on a new project - automatically compacting and repairing our databases every evening. I am confident that I can do this (just!), my only issue is deleting the lockfile in case any users have forgotten to log off the databases before they have left.
Obviously I will be unable to carry out the C & R if users are still logged in. Does anyone have any ideas as to the best way to tackle this?
I know this has been discussed before but I have not been able to find a solution for my problem.
I have a database with linked tables from the back end database. The normal size is about 4.5 mb but after doing some work on a fairly simple form and a function with Select Case statements and simple SQL (the SQL was here before that change) the size has risen to 33Mb. This actually doubled to 66Mb earlier today after a very minor change but did compact back to 33Mb.
I have the Jet Compact Utility to no aval. I have tried creating a new database and imported all the objects from the original but again to no avail.
I have an access 2000 database, which we copied from it's original location to another computer. I now am trying to modify/update the file, and have discovered an unusual problem. The filesize is roughly 75 megs! It is not a huge database, the biggest table has 2200 entries x maybe 8 fields.
There apparently had been corruption in the 2200 line table, as when I first looked into it, it had something like 275,000 rows. So I deleted back to the 2200 "good" rows of data. Figured I had the filesize problem fixed. But it won't shrink. Tried compact/repair and it didnt help. Crunched data for a long time, seemed to be working, but the filesize turns out nearly the same.
I then created a new database, and imported all of the info from the "big" one. Filesize = 1.5 meg. Great! not really. I cant get any of the code to copy over and I am not a VBA guy. All of the form buttons return error messages, and when I look into the event procedures there is no code. I tried copying all that code over, and it appears to have copied, but it doesnt work.
Maybe someone out there can offer suggestions? Thanks, Harry Manvel
I was wondering if anyone might be able to help me. What i'd like to do is to be able to get the access to trigger compact and repair database tool automatically just before it shuts. Is it feasible? or has to be done manually?
I have created a database with approx ten tables with many queries (make table and append and delete queries). I need to compact this database as I would normally do (usually deal with databases of 500MB and more with no issue) however after over an hour I still get the message 'not responding'. I have tried creating a new one from scrath and get the same issue. Can anyone help please?
The compact and repair utility is very good. Since all my record operations are done through menu, I would like to put a command button for this utility also. But I dont know how to do this. Would somebody help? Thanks in advance.
I am trying to compact & repair a secured database. I log in exclusively as the administrator with the following shortcut property target: "C:Program FilesMicrosoft OfficeOFFICE11MSACCESS.EXE" f:pathnameappname.mdb /User "adminname" /Pwd "adminpwd" /wrkgrp f:pathnameappname.mdw /excl
When I run Compact & Repair, I get the following message: "Microsoft Office Access can't delete f:pathnameappname.mdb after compacting it. The compacted database has been named f:pathnamedb1.mdb."
It goes on to say that it can't delete the original database because it is read-only (even though it is not).
Can I compact a secured database manually, or does it require some sort of utility?
I ahve come across a small problem and i am wandering if someone can helo me out on this. I have a programme which is for the fast food and uses a order no for each receipt, now the problem is each time the form is closed and opened the number goes to the next avaialable number so last nunber was 32 the next will be 33 etc this number adding is done by code but i am having a problem somewhere along the lines and it goes back to 1 every so often, so the you have to log off and log in to to to the next available record,
So i was thinking rather having to do the number increment by code why not have a auto number field in there instead, the only problem is at the end of the day the number should go back to 1 for the next day so is there a way to compact and repair the database or better still to zero the tables i wish??
Is there anyone out there that knows if it is possible in any way to make a database compact automatic at a certain time. If someone (user) has forgotten to close the database, automatic gets thrown out and then it compacts itself ?
My access database grow exponentially to 170 MB, We share the access database on the network and those tables on the access database are linked to SQL Server. I tried to compact and converted to 2003 format, It still doesn't shrink too much for the size. Please someone tell me what should I do for it, because someone try to access thur the VPN connect, and it make no sense for her to take 5 mins for loading a report remotely.
I have found myself with a big problem, One of my databases has managed to become rather large in size, 1,084,576kb
Unfortunatley i am unable to compact the database, as i get the following error on compact "record(s) can't be read; no read permission on L:database name"
The size of the database now seems to be the reason why reports and queries are failing,
I have tried "database utilities" Repair Database - and this has no affect. I have also tried temporally removing some of the tables and queries into another database, but the Db size remains the same.
Does anyone have any ideas as i'm stumped? p.s. the database in running on ACCESS 97
i have a database that is 12 megabytes. when i compact and repair it, the database is 6 megabytes.
am i losing information? is there anything bad about compact and repaiir? my database seems normal after the compact and repairt, but i would like to confirm weather or not compacting makes the database lose info
Can anyone give me guidance or code on how to automatically compact and repair.
There is something going on in my database when I open and it goes from 3.7kb to 26 kb each time it is opened - I cant find out why - ope to the why suggestion but another option is to automatically compact and repair
Is it possible to have access close the db when my users are idle after a set ammount of time, say 60 seconde of inactivity? My users seem to forget that they have the application open and other users can't get on.
I currently manually run a compact and repair on the backend of a database at work, but was wondering if it might be sensible to set it to compact on close so that (in theory) it is done at least daily and therefore shouldn't take much time?
The back end resides on a network server, which is backed up continuously, so in theory it should be easy enough to roll back to a backup copy should anything untoward happen.
Is there any option to kick out users after a certain time of idle.
Say, a user login my ms access and don't logout from database and he don't do anything in ms access. I want automatically logout from ms access after a certain time he is idle.
How would I use the Access 2010 setting, 'Compact on close'?We have a back end on a server and many users with front ends on their computers. So would I set 'Compact on close' on the back end? And then it would compact when the last user logged out?
"how to COMPACT the DB by introducing delay of 10 seconds and then close the DB".In the Database, I'm able to accomplish the "Compact" the database using the function below.
Function Compact() SendKeys "%(FMC)", False End Function
As my DB is quite huge, the Compact action takes around 10 seconds to complete.Now, i would like to Close the Database after Compacting the DB. I tried including "DoCmd.Quit" in the function. The commands in the function, closes the DB but the Compact function doesn't seem to have executed as it needs 10 seconds to complete.
Function Compact() SendKeys "%(FMC)", False DoCmd.Quit End Function
how to introduce this delay of 10 seconds and then close the DB.
