petebob796
Registered User.
- Local time
- Today, 09:03
- Joined
- Jul 31, 2007
- Messages
- 27
I have been posting a lot recently and have greatly appreciated the help. I have just been looking at the size of a ms access project, this is a front end for another database so contains no data (runs as an mde for most). I have made a few modifications using access 2007 including at one point having it in the new file format, this was to fix a bug I was getting that caused a particular crash. I found converting it to 2007 and back cleared the problem.
Anyway the main things I added were an active directory query to enable certain buttons for a limited number of users. Including the VBA reference to do this. I also added a new report that when run in access 2007 (even in 2003 format) allows the new reportview so I can have an onclick event within the report for the user to gather more information which it wouldn't be appropriate to have on the main report.
This has balooned the size from 5mb to 50mb even after a compact and repair. Any suggestions as to possible causes could it really be adding vba references causing that much of an increase. I should say i'm not particularly worried it's ok for it to be that size I just wonder why such a massive difference.
Anyway the main things I added were an active directory query to enable certain buttons for a limited number of users. Including the VBA reference to do this. I also added a new report that when run in access 2007 (even in 2003 format) allows the new reportview so I can have an onclick event within the report for the user to gather more information which it wouldn't be appropriate to have on the main report.
This has balooned the size from 5mb to 50mb even after a compact and repair. Any suggestions as to possible causes could it really be adding vba references causing that much of an increase. I should say i'm not particularly worried it's ok for it to be that size I just wonder why such a massive difference.