Rocky Smolin at Beach Access Software
rockysmolin at bchacc.com
Mon May 12 16:05:11 CDT 2008
Yep. That would make it really general. Then you could isolate all the reports in a separate mdb or allow users to add their own custom reports and run them from your mde by letting them enter mdb file name, and report. Rocky Smolin Beach Access Software 858-259-4334 www.e-z-mrp.com www.bchacc.com -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of David McAfee Sent: Monday, May 12, 2008 1:36 PM To: Access Developers discussion and problem solving Subject: Re: [AccessD] FW: Run Report in Another Database Couldn't you pass your Sub two parameters, such as ReportName and OpenMethod so that you can call any report and then open it in Preview or Normal? David McAfee On Mon, May 12, 2008 at 11:36 AM, Rocky Smolin at Beach Access Software < rockysmolin at bchacc.com> wrote: > Well, like Lambert says - set a reference to the target db (where the > report > is) in the calling mdb. User Tools-->References and change file type to > mdb, navigate to the folder with the target mdb and set the reference. > > In the target mdb make a module with a sub named something like RunIt > with the one line DoCmd.OpenReport "rptMyReport", ACViewNormal (or > Preview if you > like) (where rptMyReport is already in the target mdb). > > Then in the source mdb just say Call RunIt wherever you want and walla! > The > report runs in the other mdb. > > Apparently setting the reference in the other mdb makes all the > objects in that mdb visible in the source mdb. Who knew? > > (Well, Lambert knew) > > > Rocky Smolin > Beach Access Software > 858-259-4334 > www.e-z-mrp.com > www.bchacc.com > > > > -----Original Message----- > From: accessd-bounces at databaseadvisors.com > [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Edward S > Zuris > Sent: Monday, May 12, 2008 12:09 PM > To: 'Access Developers discussion and problem solving' > Subject: Re: [AccessD] FW: Run Report in Another Database > > > For the curious, what is the answer ? > > -----Original Message----- > From: accessd-bounces at databaseadvisors.com > [mailto:accessd-bounces at databaseadvisors.com]On Behalf Of Rocky Smolin > at Beach Access Software > Sent: Monday, May 12, 2008 11:02 AM > To: 'Access Developers discussion and problem solving' > Subject: [AccessD] FW: Run Report in Another Database > > > Lambert: > > Never mind. I figured it out from your post. > > Thanks. > > > Rocky Smolin > Beach Access Software > 858-259-4334 > www.e-z-mrp.com > www.bchacc.com > > > -----Original Message----- > From: Rocky Smolin at Beach Access Software > [mailto:rockysmolin at bchacc.com ] > Sent: Monday, May 12, 2008 9:54 AM > To: 'Access Developers discussion and problem solving' > Subject: RE: [AccessD] Run Report in Another Database > > Lambert: > > Can you be more specific about "set a reference"? > > Thanks > > Rocky > > > > Rocky Smolin > Beach Access Software > 858-259-4334 > www.e-z-mrp.com > www.bchacc.com > > > > -----Original Message----- > From: accessd-bounces at databaseadvisors.com > [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Heenan, > Lambert > Sent: Monday, May 12, 2008 8:57 AM > To: 'Access Developers discussion and problem solving' > Subject: Re: [AccessD] Run Report in Another Database > > The simplest way is to define a public Sub or Function in the other > database that runs the report. Then in your first MDB set a reference > to the other database. Once the reference has been set you will be > able to call the Sub or Function and have the report run. > > Lambert > > -----Original Message----- > From: accessd-bounces at databaseadvisors.com > [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Rocky > Smolin at Beach Access Software > Sent: Monday, May 12, 2008 11:02 AM > To: 'Access Developers discussion and problem solving' > Subject: [AccessD] Run Report in Another Database > > Dear List: > > What's the command or syntax look like to run a report which is in > another MDB? > > MTIA > > Rocky > > > > > > > > Rocky Smolin > > Beach Access Software > > 858-259-4334 > > www.e-z-mrp.com <http://www.e-z-mrp.com/> > > www.bchacc.com <http://www.bchacc.com/> > > > > > > > -- > AccessD mailing list > AccessD at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/accessd > Website: http://www.databaseadvisors.com > -- > AccessD mailing list > AccessD at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/accessd > Website: http://www.databaseadvisors.com > > No virus found in this incoming message. > Checked by AVG. > Version: 7.5.524 / Virus Database: 269.23.16/1427 - Release Date: > 5/11/2008 > 1:08 PM > > > -- > AccessD mailing list > AccessD at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/accessd > Website: http://www.databaseadvisors.com > > -- > AccessD mailing list > AccessD at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/accessd > Website: http://www.databaseadvisors.com > > No virus found in this incoming message. > Checked by AVG. > Version: 7.5.524 / Virus Database: 269.23.16/1427 - Release Date: > 5/11/2008 > 1:08 PM > > > -- > AccessD mailing list > AccessD at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/accessd > Website: http://www.databaseadvisors.com > -- AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com No virus found in this incoming message. Checked by AVG. Version: 7.5.524 / Virus Database: 269.23.16/1427 - Release Date: 5/11/2008 1:08 PM