Reports can also be kept in an Access .mda file.
We use a similar function for custom reports for our clients. We 'call' a report. If the report exists in the .mda file, then we open it, otherwise, the system calls the 'default' report contained within the same front end. The .mda file needs to be a reference in the main mdb file. The mda file will also have table links to both the main front end and back end, whatever format that may be(SQL server, Access, MySQL, etc). This enables us to upgrade core functionality without the client losing reports or cause other upgrade headaches.
The other option is to have a reports only mdb file. At my old company, I had one mdb file for data entry/modification and one purely for reports. This enabled me to make changes to one file or another without killing all work being done at one time. By the time I left the company, I had 4 separate front ends by with specific functionality by job function (our SQL server db was over 8 GB in size).
Always be flexible and remember, there is always more than one way to do it. Pick the one that suits your needs best.
TJ
jezmo_codpiece <[EMAIL PROTECTED]> wrote:
We use a similar function for custom reports for our clients. We 'call' a report. If the report exists in the .mda file, then we open it, otherwise, the system calls the 'default' report contained within the same front end. The .mda file needs to be a reference in the main mdb file. The mda file will also have table links to both the main front end and back end, whatever format that may be(SQL server, Access, MySQL, etc). This enables us to upgrade core functionality without the client losing reports or cause other upgrade headaches.
The other option is to have a reports only mdb file. At my old company, I had one mdb file for data entry/modification and one purely for reports. This enabled me to make changes to one file or another without killing all work being done at one time. By the time I left the company, I had 4 separate front ends by with specific functionality by job function (our SQL server db was over 8 GB in size).
Always be flexible and remember, there is always more than one way to do it. Pick the one that suits your needs best.
TJ
jezmo_codpiece <[EMAIL PROTECTED]> wrote:
I'm sure this topic was covered recently but I have been unable to
find the post. I want to have my reports in a separate mdb file for
future updating purposes, but cannot remember how it's done. Can
anyone enlighten me please? Many thanks
Yahoo! Photos
Ring in the New Year with Photo Calendars. Add photos, events, holidays, whatever.
Please zip all files prior to uploading to Files section.
YAHOO! GROUPS LINKS
- Visit your group "AccessDevelopers" on the web.
- To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
- Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.
