Hi All,
Is there any way to determine the right time for compacting a database?
I mean say for example - is there any way (thru a property/system table) which I can refer to see how many records are marked for deletion?
This way - I can compact the database ONLY if there are large number of records marked for deletion?
I have searched all the places I could but could not get the answer I want. :confused:
Thank you,
Dev.
:)
I have an application with a backend db on PC 1, and the same application on PC 2 linked to the backend db on PC 1 via the network.
The link works fine but the time formats are different.
On PC 1 the time format is shortime and displays as it should i.e. in 24 hour clock format
However on PC 2, opening the same database via the network, the time format is still shorttime but when you read the time within the code it comes out in AM/PM format. Also, when the defaul tiem should be #20:00:00# but this changes to #8:00:00 PM#
Weirdly though, when you just open the table, the times are in the correct shorttime format.
Guessing, it must be a setting within the main core of Access 2003 that is different between the 2 instances?
Any ideas?
This screen shot may help:
I have an application with a backend db on PC 1, and the same application on PC 2 linked to the backend db on PC 1 via the network.
The link works fine but the time formats are different.
On PC 1 the time format is shortime and displays as it should i.e. in 24 hour clock format
However on PC 2, opening the same database via the network, the time format is still short time but the format is in AM/PM or medium time.
Guessing, it must be a setting within the main core of Access 2003 that is different between the 2 instances?
Any ideas?
Hi everyone,
hopefully you'll be able to help me out with this one, been searching but can't find the exact answer.
I am running a database with multiple users, max of 10, currently the database autocompacts when it is closed, however this takes time every time anyone closes it.
what i am looking to do is have the database automatically compact but only once a day. Any ideas???
many thanks
Goodmorining,
I use Access XP and I have a problem with the Compact and Repair function.
When I start this function via the normal menu's access doesn't seem to respond anymore. I can leave my comp on for hours dut nothing happens.
He does make a copy (db1) with the same volume but then it stops.
Does anybody else has this problem and what can I do about it
Thanks
Kind regards
Rolf
Hi
does anyone know how i would make my database compact & repair itself either when i open or close it?
tried to do it via a macro but it says that it can't compact and repair when a macro is running :(
:confused:
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.
Help please???
Kevin
Hi all,
This morning i opened up my database, it worked fine, ie could add new records on to the forms etc but when i went to look at my tables, queries, forms etc nothing was there and an error message about indexes came up.
I had a look through this forum and found a lot of useful information on compacting and repair. I compacted my database and it went from 89KB to creating a new database with only 28KB. The new one which it created works perfect for me and i have deleted my old one, as still no tables, queries etc showed up.
I didn't even have a clue i should have been compacting my database regularly, stupid i know but we all learn. My question is, when looking at threads i have noticed that when people talk about compacting, repair is mentioned too, do i need to run the repair tool now on my database? Or is it ok. Im not entirely sure of its function, i will keep looking though, Thanks for any replys :)
Hi guys,
This is just for discussion really. What does Compact and Repair actually do? If I was to set my database to compact and repair on close, am I in danger of losing any data, formatting on forms or anything? What are the pros and cons?
I would really appreciate some replies. Thank you in advance :)
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
When I 'compact and repair' on my office computer, two tables' autonumber fields become corrupt (I get a duplicate autonumber)
I took the original .mdb home and 'compact and repaired' it at home and to my surprise the tables didn't become corrupt.
Any ideas why the compaction causes errors in the office but not in my home?
Thanks very much
Hi,
Could anyone explain to me what compact and repair actually does? Made a backup copy of my database and did the c and r and reduced the size greatly! Has it lost data? Just would be good to understand how this works.
Thanks
Sam
I have a macro that will copy the database to a folder upon quiting.
The databse also is enabled from the options to compact and repair upon exit.
Problem is the copied databse will be always not compacted becaue the macro will run 1st before quiting (and hence before compacting).
is there a way around it
I have search the post and I found several articles about compacting and repair the DB. I just installed 2007. So you think that had an issue with compacting. Before I installed 2007 I had no problems at all. I even tried to import tables, forms and etc. into a new DB. I get error messages there as well.
I can say when I was working in 2007. I had to open the 2007 DB in exclusive. As of now I am just fishing for answers.
Bottom line I must have done something while working in 2007.
Any Ideas would help.
PS. I can go into the db with no problem at all, which is really strange. But when I create a new DB I can't import any of the tables or forms.
Hi,
I apply Compact On Close (Tools->Option->General tab). So, every time, it will compact the database when closing the file.
However, will it do repair the database automatically? It seems just do compacting.
This is a very general question. so I am not sure if it has been asked before.
I know that compact and repair can sometimes fix problems with the database.
Should it be done only when problems seem to be creeping in? Or should this be done on a regular basis - say once a week or once a month?
Can compact and repair be set up to run either on a specified day of the week (for example every Monday), or day of the month (for example the first of each month)?
Alternatively can I have it run automatically when the database is closed?
If so, how would it be done?
I am using A2003 with Windows XP.
Okay... unlike my last post (although unintentional), this is legitimate.
Whenever I do a compact and repair on my database, access crashes and offers to attempt to repair my db. IF I allow it to do that, it will blow away all of my VBA code and so everything stops working.
If i uncheck the repair box, access will just close. I can reopen my db myself and it's find. I'm not sure about any repairs (never understood, what it's repairing), but it's definately compacted any everything is fine.
So why does it crash and why does it eat my db unless i uncheck the box upon crashing?
I have built a DB in Access 2002 which includes an automated Compact and Repair button. My problem is that the DB, (I have just found out) must run on 97. The code I am using is as follows:
CommandBars("Menu Bar"). _
Controls("Tools"). _
Controls("Database utilities"). _
Controls("Compact and repair database..."). _
accDoDefaultAction
This is producing an error in 97 because, I belive, the compact and repair are two seperate headings. Can someone advise me where I'm going wrong or even correct my code for me? Thanks!
I understand how to compact and repair and also the fact that you need to do it so that you can increase the efficiency of your database, but my question is why? I have a database that is used fairly heavily all day by 4 to 5 users. At the beginning of the day the file is about 91 mb, by the end of the day the file size is about 133 mb. Why does it grow so much in just an 8 hour period? What causes access to need to be compacted and repaired?
View 2 Replies View RelatedI have an Access database that's on our in-house server. This database has never been compacted/repaired. Recently our server crashed (but we were able to retrieve the database). Does the fact that the database has not been compacted have anything to do with the server crashing? Could that have affected it in any way?
Also, how often should the database be compacted/repaired?
Thanks for your help!
Hi,
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?
Thank you in advance
Gents I hope you can help me with this issue.
If my BE DB crashes I use compact/repair and it fixes the problem.
If I Just use compact/repair on my BE DB when nothing is wrong with it then it causes the data to disappear in certain fields.
Any Ideas what i am doing wrong. (Besides from telling why do you use this utility when nothing is wrong)
Hi,
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?
I have a large DB that I want to compact & repair daily. I have the option set to "compact on close"
is there a way to write a batch file that will open the program, then close it again so it will do a compact?
if not a batch file then any type of program that might be able to handle this?
Hi all. I am having some problems with some users, not allowing the database enough time to compact and repair before they switch off their PC or laptop. Although they have been told many times about the function needing time many are just impatient. This has resulted in various db1, db2 etc being created within the folder which are then being opened and used by other members of staff being less then smart.
My question is, is there a way to have some sort of splash screen or something similar run during the compact and repair process that tells the user what is happening. Any other alternatives or methods would be fine this was just my first thought.
Thanks
James