I'm planning to use the "compact on exit" functionality to keep my db's neat. I have understood that I also have to grant "Exclusive mode" to the database object to the users of my db (not to Users group, but my own users group). Does this have a security implication?
As I'm running a FE/BE solution, does the compact and repair only do my FE or both. If only the FE, is there a good way of triggering the BE to be C&R as well?
I have a database which seems to open many copies when it is accessed over the internet (via ASP) but If I open it on my compter over my LAN then it seems to open 'exclusive' and those on the Internet get the error message that 'file is already in use'. Is there a way of opening the database over the LAN and allowing the Internet to see it?
I have a simple Access database with a number of linked tables to Excel spreadsheets located in the same directory.When I open the Access database from two networked machines, I get an error on the second machine when I try to open a form that uses the linked tables. It says that the linked table has been opend in Exclusive mode.Any idea how I can prevent Access from opening the linked tables in exclusive mode?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
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 :)
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 :)
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.
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.
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?
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:
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?
I 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?
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?
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.
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.
Again, I've had a search, but can't find anything to solve my problem - so sorry if I've missed it.
Basically, when I compact and repair the database I'm developing at the moment, I get the error message - Table 'TempMSysAccessObjects' already exists.
There is no table of that name (or at least I can't see one and I haven't created one!) and the database just opens up again but has not compacted or repaired.
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??
