Can I link to reports in another database?

[Bob]

For maintenance reasons I would like to split my DB in an Frontend and
a Backend. The frontend is an MDE. The backend contains all the tables.
Nothing special. But I will also have my reports in the backend or even
in a second backend database. I that case I can easily spread new
reportslayouts to my customers, without rolling out an update of my
frontend database.

But: is that possible in MSACCESS 2003 and how? Ca it be done with a
reference to another DB?

[BillCo]

You cant link to reports. you can only pull in data, not forms, reports
or other application objects. application objects live in the
application :(

your best option is to keep your reports in the front end, but create a
small login app which checks for version updates and downloads the
newest version if needed. That way you can update reports in master
front end on the network and simply increment the version number. when
people log in via the log in app it will pull down the new version with
the report updates. lemon squeezy! There's a lot available on how to do
this, so I wont repeat it all here.

[Lyle Fairfield]

"Bob" <bs*****@merema .nl> wrote in news:1147259863 .339323.98880
@j33g2000cwa.go oglegroups.com:

For maintenance reasons I would like to split my DB in an Frontend and
a Backend. The frontend is an MDE. The backend contains all the tables.
Nothing special. But I will also have my reports in the backend or even
in a second backend database. I that case I can easily spread new
reportslayouts to my customers, without rolling out an update of my
frontend database.

But: is that possible in MSACCESS 2003 and how? Ca it be done with a
reference to another DB?

Probably you can if you set a reference to the database containing the
reports and expose them by modifying their manifestation as text.
This is not trivial (and may be impossible). To learn how, you could serach
this group for Terry Kreft and VB Attribute; this thread addresses the
exposure issue:
http://groups.google.ca/group/comp.databases.ms-
access/browse_frm/thread/52b6f6c65f84b0c b/855dfeb0f00bd7f a

It !!!MAY!!! be easier to reference the database and to create a public sub
in a standard module (in that database) that opens the report, and to call
that from from your main db.

--
Lyle Fairfield

[salad]

Bob wrote:

For maintenance reasons I would like to split my DB in an Frontend and
a Backend. The frontend is an MDE. The backend contains all the tables.
Nothing special. But I will also have my reports in the backend or even
in a second backend database. I that case I can easily spread new
reportslayouts to my customers, without rolling out an update of my
frontend database.

But: is that possible in MSACCESS 2003 and how? Ca it be done with a
reference to another DB?

See if this link helps
http://groups.google.com/groups?as_q...=2006&safe=off