Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
Moussie
Starting Member
20 Posts |
 Posted - 2004-11-10 : 17:40:26
|
Hello!We have a central SQL-server containing our data. Against this we run an .adp-client. This .adp-filecontains about 20k lines of (mostly interface-related)VB-code. In addition, and this is the killer, it has about 150 Access-reports. Now, a lot these reports contains bitmaps, and the .adp-file now stands at a size of about 55 mb after compression. It's getting to a point where redistributing the .adp is slowly starting to become painfulbecause of it's size. Since these reports don't change all that much we would like to have a central .mdb or .adp repository that would contain these reports, thus making the redistributed .adp-client much smaller (since it would then contain solely the code and the forms, no reports).In other words, we would like to "link in" REPORTS, prettymuch the same as can you link in tables or code from anotherAccess-file.Is this at all possible ? If there is somebody out there who knows, I figured this was the site they would frequent  Regards,Moussie |
|
|
billinb
Starting Member
2 Posts |
Posted - 2004-11-16 : 03:09:50
|
| Hello Moussie,The bitmaps are killer when it comes to disk space. But you might be on the right track by putting the reports in separate .mdb's and calling them from the main file.You could have some sort of exit routine built into a pop-up form in the reporting .mdb's, so that you can exit out of the application instead of just closing the form after the report has run.You might also look into utilizing pass-through queries in the .mdb's that are used for reporting.You might also be able to utilizing Excel for some of your reporting and you could use pivot tables that are pointed at a pre-existing connection so that it opens securely.At any rate, if you do this, you'd need to be able to manage several files and keep them secure, and in the same folder hierarchy as the main adp.Bill |
 |
|
|
Moussie
Starting Member
20 Posts |
Posted - 2004-11-16 : 05:05:52
|
| >But you might be on the right track by putting the >reports in separate .mdb's and calling them from >the main file.But this cannot be easily done as far as I know.I want to do Docmd.Openreport() on a report residingin another .mdb/.adp/whatever! I do not want to hassle with pop-up forms and exit routines :)>You might also be able to utilizing Excel for some >of your reporting >[...]This we already do, but it is not always approriateand we have all these legacy-reports that I do notwant to rewrite into excel :) |
|
|
|
jsmith8858
Dr. Cross Join
7423 Posts |
Posted - 2004-11-16 : 09:19:37
|
| move the bitmaps out of the report themselves, save them as files on a fileserver. That will greatly reduce the size of your ADP.be sure to specify in your forms/reports that the bitmaps are LINKED and not EMBEDDED. not sure how Access handles it if you embedd the same bitmap in 100 places -- it might store 100 copies of that bitmap ! if you link them, it takes up no space. just make sure everyone has access to the file server and drives are mapped properly and all that.you'll see a huge decreas in size if you have lots of graphs. Lots of code and and many report designs do not make files very large -- it's data and bitmaps.Of course, make sure after removing the bitmaps you compress the file (though I am not sure if you can do this with an ADP). if you can't, or the file doesn't shrink, it might pay to import all of your objects into a new ADP file.- Jeff |
|
|
|
|
|
|
|
|
Access reports from outside an .adp?