Re: Copying reports from one database to another

From: Lewis Moseley (lmoseley_at_nospam.bellsouth.net)
Date: 06/28/04 

Date: Mon, 28 Jun 2004 18:43:17 -0400

PLAN B:

Conversely, you can EXPORT most any object to another database.
Starting in the database that has all of the reports, choose the
REPORTS section and highlight a report. Click on FILE, EXPORT.
Navigate to the desired database. Click YES to overwrite, if
necessary.

Repeat for other reports and/or other destination databases.

NOTE: IF you are still using Access 97, be aware that A97 does not
like exporting objects when the object already exists in the target
database. After allowing you to export and overwrite one or two
objects, then it often crashes. This is not destructive, but IS an
annoyance.

If you are using Access 97, there is a very nice little freeware tool
that allows you to select multiple objects and export them without
error. Get it from the DEVELOPER TOOLS section here:

http://ourworld.compuserve.com/homepages/attac-cg/acgsoft.htm

PLAN C: Copy and rename the entire database using windows explorer,
then delete the data and reports that you no not need for that client.

On Mon, 28 Jun 2004 14:40:38 -0700,
<anonymous@discussions.microsoft.com> wrote:

>We have 20 clients that are currently in a single
>database. We prepare 4-5 reports for each client. We would
>like to split the database per client, but we dont want to
>change/create a report 20 times. What is an easy way to
>duplicate these reports from one database to another?

Relevant Pages

  • Re: SYSTEMS ENGINEER/ VAX-VMS/ CAREER POSITION
    ... System Administration and database admin from NIIT, ... salary details and generate reports and enclosures,and calculates ... Responsibilities: ... Write New programs from user requirements, Programming Changes ...
    (comp.os.vms)
  • Re: Convert Access application to .NET?
    ... I am learning as I go and the client does not want to ... I had assumed that the instability came from the UI, not the database. ... do you know how Crystal Reports compares to the reports in Access. ... We decided to convert the whole app to .Net. ...
    (microsoft.public.dotnet.framework.windowsforms)
  • Re: Advice needed for a growing Access 2000 project
    ... However, it turned out that quite a few of those were "leftovers" from previous releases, no longer accessible from anywhere but the database window, and, thus, no longer used. ... But that certainly isn't the _norm_ -- without any 'heroic' measures, there are routine reports of split Access DBs ... Finally, in my opinion, for "Windows apps", that is, individual-user applications, modest-sized multiuser applications, and client-server applications of any size, Dot Net does NOT "help along" any of these issues. ... The post I reference was in reference its self to the MS Access Help file under "Microsoft Access database general specifications" ...
    (comp.databases.ms-access)
  • Re: running report cause fatal error- on Win98, not XP
    ... It is actually not that difficult to crash JET with complex queries, ... another query. ... only the more complex reports cause the crash- the others do ... Then compact the database: ...
    (microsoft.public.access.reports)
  • Re: running report cause fatal error- on Win98, not XP
    ... another query. ... only the more complex reports cause the crash- the others do ... Then compact the database: ... Still in the code window, choose Compile from the Debug menu. ...
    (microsoft.public.access.reports)