General :: Difference In Size Between Actual Access Database And Its Backup
Aug 19, 2014
I am using Access 2007 database in work environment. When one of my colleagues tried to update some records in a table, it created a backup of the database.
The issue is that the size of the actual database is much smaller than the size of the backup. However all the data are present and I don't think any data has been deleted.
But I don't know why there is a difference in size?
Some of the tables in the database are linked from MS SQL Server.
My friend uses quite a lot of tick boxes for Yes/No questions. he asked me if it was possible to show the difference between entering an actual NO and never ever visiting the box in the first place. I replied "that's easy you need tri-state".
I can switch tri-state on all right but the table field is still Yes/No so it does not save the third state. Second attempt is to replace the tick box with an option group showing yes/No/Not clicked. Now I find that I am trying to use the "improved" version 7 interface and I can't get the option group wizard to work at all.
I have developed an access database, and prepared its run time exe file. My question is how to develop the database so that the user can regularly backup the database?
I am trying to use VBA to backup the BACK-END of a split database (so I can automatically archive selected data). If I use FileCopy I get a message that the BACK-END database has not been found.Obviously I could 'unlink' the BACK-END, copy it and 're-link' it..Is it possible to copy the BACK-END tables(not just the links) into the FRONT-END and get at them that way?
I'd like to have a button on my dashboard that gives the user the ability to back up the database and save it with a different date. For example, existing database called "Fishing.accdb" and I'd like to have code behind a button that allows the database to be saved as "Fishing0711.accdb"
I'm trying to avoid the user having to go into the File Save as menu system....I've tried the docmd.copyObject method but can't get it to work
I'm using Access 2007, with what I think is a normal database that I've built up over the past month (maybe 15 tables, <1000 records, 20 queries, 4 or 5 reports and macros). I'm not an experienced Access programmer, so I don't think I'm doing anything fancy with security settings or any other such stuff. (If I have, it's surely by accident, not by intent.)
When I try to back up the db using the simple office button -> manage -> backup method, access generates a date-stamped backup filename and opens a file save dialog for me, but it ALWAYS fails to backup the database. I always get the same error message when I click save, whether I save on my machine, or on a network drive.
"Could not use '<path to the current database dir><backname>.accdb; file already in use."
This same error occurs when I create a new blank database with a single Table1 in it, so I don't think it's my database.
Does anyone have any idea why this might be happening? I scoured the net for help, but nothing. I checked various Access forums, but nothing. So I arrive here after I've done my homework... thanks
Im trying to create a command that will create a backup of my access database once every week. here is the code I've got so far. it works, but not once a week but every time I start the access:
MsgBox ("Hello! Starting Backup procedure")
Dim DateOfBackup As Date Dim strSourcePath As String Dim strSourceFile As String Dim strBackupFile As String Dim SQL As String
Hello all!Maybe strange, but I have litterely created a new database from my "old" one. I did this because I thought the size of the database was growing way to fast.What I did was open two instances of Access, one with a new empty database open and one with the other "old" database open. I manually created all tables, queries, forms and code again by selecting everyting in design view, copying it, creating a new table/form/query/module in the empty database and pasting the data. After that I had to set some properties and it was ready to go. After compiling and compacting the new database was just 718kb in size. Empty that is. Then I added a couple of cases, compacted again, added some more, compacted again. (copies of the same data on different records). The same I did with the other "old" database.Both now have 12 clients with 2 cases (totalling 24 cases) every client and every case existing of the same data.The new database is now 1.120KB in size, the old one is 2.096KB. That's almost double. The only real difference between the two that I can think of is that one has a 20KB image tiled on the background of each form (the same image though) plus, of course, in the one database I've been designing, adding, deleting more.But how is it possible that these data sizes are so different? 100KB difference, ok. But almost double the size? How is that possbile and why? Are there things I can do to keep it at bay apart from using the Compacting and Reparing option? Plus: Is this normal?Edit: I emptied them. One is now 812KB in size empty, the other one is 1496 empty. Still... double the size. ?
I have a database (Access 2003 and I am using it with Access 2007 with user level security) on shared folder on internal Dell server and I have created a shortcut to each user's machine to access it. This days I am facing a problem of db size as every 10 days it's increasing upto 2gb but the strange thing is when I am doing cut / pasting same database to my desktop from the server shared folder it will become 80 mb only and I am again placing that db (80mb db) into the server and it will work. What is a reason behind it? why my 80mb db is showing 2gb db on server?
I have adopted someone elses database. It is a front end with about 100 linked tables/forms/reports/modules. The problem is that the database is really large. I would think by looking at the objects that it should be around 5mb tops, however after compacting it is still 63mb.
Is there a way (vba or otherwise) to look at each object and get its size in KB?
Once I can figure out which object is taking up too much space I can work on making them smaller.
We have an Access 2010 database that is accessed by some users from another location. Each user has their own copy of the front end. For some reason two users in our Sydney office enter orders, but after they have entered and saved the order, sometimes for no apparent reason they get an "invalid argument" error message and all the data in the order has been converted to hieroglyphics. I cannot seem replicate this from my server location.
It seems to only occur from our Sydney based server. Could it be that each user's copy of the front end is located on the same virtual drive on our Melbourne based server? Should I move the Sydney user's copies of the front end to the Sydney based server?I think it might be the growing size of the database but I compacting doesn't reduce it by much.
Hey guys, Was wondering, what is the recommended maximum size for Access databases? I've heard that for very large databases that oracle is preferred. Would Access be appropriate for something on the scope of 5000 records of roughly 6 text and 2 number fields? Do people ever notice performance effects on databases of that size?
Also are there any ways to help reduce the size of the database? Do you recommend change the default field sizes where appropriate and would this have a noticeable effect on a database of this size? Any other suggestions to help keep the database manageable, and functioning?
I'm basically trying to figure out if there's much to worry about here, before I start importing my data. Thanks.
I just got done migrating the tables in my database to a SQL server, I went in and deleted the extra table that was created with the migration manager so all the data in my database is on a SQL Server, For some reason the size of the database is still the same. Why is that?
I even when in and deleted the tables query and forms but the size is still the same, if there some setting that im missing?
I had a massive Access file of almost a GB in size. and I deleted all records off the tables hoping it would shrink and my purpose was to have the tables alone in their structures. However despite deleting all records, the database file size seems to stay the same. anybody knows why this is so? I don't think we can "commit" changes to databases done in access as it is done in other databases. anybody knows why this is so?
Will keeping your field size shorter result in a smaller MDB file?
Or does Access only use as much space as there is real data in its fields.
Way back in the dBASE III days, dBASE would pad all your "real" information with as many spaces as necessary to fill up your field. I suspect that the MDB structure is probably smarter than that.
Another question on the same topic - I believe there is a maximum number of characters in a record (4000?). Can your field sizes add up to more than 4000, as long as the actual data, all combined, never totals 4000...? Thanks............ ..dc
Is it possible (using the menu or VBA code) to find out the size of the objects in an Access database file?For example if the .accdb file is 300Mb, is there any way of comparing the size of the numerous tables/forms/reports/queries etc, that make up the database?(I know that if I created a new access file and imported the objects from the working database that could give an indication but that would be quite a repetitive process).
when I open a pdf through access weather it is by hyperlink or attachment it always opens the full size of my monitor, if I open a pdf outside access then they open ok , how do I set the size that access opens the pdf the size I want.
I really need help with this. I have a database that is quite large and is accessed through VPN. When I shrink and compact the database it goes to a respectable size. But over time everytime a report is previewed the size of the database grows. Or every access it grows to double its size in no time at all.
Any ideas... on what would make it grow and how to stop it.
I saw a demo that the user could copy and paste a JPG format file physically to ACCESS, and then something happened, and ACCESS could read the JPG length and width size (e.g. 1.3 meter length and 1.15 meter width) into 2 individual ACCESS cells which is acted the same as user input to that 2 clells.
I'm very new to access, but see it has potential for a big payoff for a project I am doing. Currently, I'm stuck summing across the columns for Step 1 EC (est completion) - Step 8 EC. This may be a poor design on my part from inputting the data in the table. But all of these jobs being a stochastic process with always different steps in machining, I don't know how else to do it.
With all that being said, I would like each Piece Part to have a sum of days at the bottom of estimated completion and actual completion. Again, it must show the total for EACH part.
For example, as shown in the access file in report under "Piece Parts Report" the first part (No. 2 Aluminum Base Plate), it goes through 3 steps... with the steps being 1, 5, and 5 days respectively. I'd like for it to show at the bottom a total of 11 days for that part to be manufactured.
I recently created a database with an FE and BE, and I want to be able to back up the BE from the FE. In the FE, I added a menu item "Back up database...", and it works good for the FE, but I want it to back up the BE, where the data is located. The reason that I like the menu item is that it opens a "Save Backup As" dialog box, and it also adds the date to the name of the database. Also it will be easier for the people that are using the db.
