Can one open a report in another mdb? (by RLi)

[Guest]

I have a split database, front end/back end.
The front end contains the form/reports/modules/queries etc.
The back end the tables and data.
The front end is distributed in mde format (so vba and design mode are non
accessible).
I would like users to be able to see and freely modify the report design,
but not the forms design.
So i thougt: maybe store the reports in a separate (open) mdb.

But can anyone tell me if one can call a report in a mdb from a form stored
in another mde? And parsing filters from the form to the report?

Thanks for any reply,
Rob

 

[Bob Howard]

How about importing it and then executing it?

Bob

 

[Guest]

You mean importing it on the fly in the mde? How do you do that?

What i want is distributing a mde with forms/queries/modules etcetera and a
separate mdb with only the report definitions. In that way i could easily
send updates to customers (simply a new mde) without them loosing their
personnalisations of the reports.
So i would like to be able to call reports in the (open) mdb from the
(protected)mde.
Importing them first might be nice, but since the mde does not allow for any
VisualBasic changes i expect an automatic import might fail.
Am i wright, or did i misunderstand you suggestion?

 

[Bob Howard]

Check out the TransferDatabase method or action. Of course, there may be a
better way to accomplish what you're after, but this may work for you.

Using TransferDatabase, you name the report in the source location (the mdb)
and the target location (your mde). You could have several reports stored
in the mdb that the user can mess with. When importing them into your mde
for execution, you may wish to retain the report's name, or you could give
them all the same name (within the mde) so that only the latest would be
retained. Upon completion of the import, you would issue an OpenReport to
perform the desired result.

Bob

 

[chase.bushey]

transfer database

While researching this same issue I stumbled on this thread. I need to do basically the same thing only I have several reports that I want to import each time a user logs in, but I need this done without hindering productivity or showing the user.

The reports need to be in different databases until log in because if I send updates to the client they need their specific reports to not be overwritten.

Any ideas?