Someone told me about a problem with an Access back end (only) ballooning in size with normal use, such as from perhaps 800 KB to about 300 MB. I'm familiar with this kind of problem occurring with a front end, such as possibly through certain VBA code activity (which is why I'm posting this here), but I'm not aware of why this would occur in a back end. The person who asked me about this says the back end has no code, only tables and two queries. I'm pretty sure it would be Acc XP on Win 2K, although it is possible that it began in a previous version of Access, such as 97 or earlier. Does anyone have any experience with this problem occurring for a back end only, or ideas about what would cause it? I recommended checking ‘Compact on close’ in general options, but am wondering about how effective this would be. Thanks.
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Chriss Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Back End Only Balloons In Size Through Use 1
- Thread starter Dor100
- Start date
-
1
- #2
- Thread starter
- #3
I normally set 'Compact on close' myself for everything. For back ends:
*is it only really effective when the last user closes the application, or will it work on a back end for anyone who closes the app even if others are still on it?
*will it work on the back end because the file is in use and the .ldb appears, or does the file have to actually be fully "open" in order for the "on close" part to kick in?
*is it only really effective when the last user closes the application, or will it work on a back end for anyone who closes the app even if others are still on it?
*will it work on the back end because the file is in use and the .ldb appears, or does the file have to actually be fully "open" in order for the "on close" part to kick in?
Dor100
Sorry, it wasn't clear that this is a multi-user application.
I would assume that the Compact On Close would only happen when the BackEnd is actually closed by the last user.
However, if you need it to compact more regularly, and it it is indeed helpful to do that, you could set something up to compact periodically to do that.
You may want to do some searching though as to what happens when a database is compacting and one of your users try to access the data in it. (plug "compact database in multi-user environment Microsoft Access" in a search and see what comes up.
Good luck. If I see anything, I will let you know.
Tom
Sorry, it wasn't clear that this is a multi-user application.
I would assume that the Compact On Close would only happen when the BackEnd is actually closed by the last user.
However, if you need it to compact more regularly, and it it is indeed helpful to do that, you could set something up to compact periodically to do that.
You may want to do some searching though as to what happens when a database is compacting and one of your users try to access the data in it. (plug "compact database in multi-user environment Microsoft Access" in a search and see what comes up.
Good luck. If I see anything, I will let you know.
Tom
Dor100
Here is a link from the Microsoft site. This refers to Access 2003, but it may help.
Tom
Here is a link from the Microsoft site. This refers to Access 2003, but it may help.
Tom
- Status
Similar threads
- Locked
- Question
- Locked
- Question
- Locked
- Question
- Locked
- Question