By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
455,608 Members | 1,526 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 455,608 IT Pros & Developers. It's quick & easy.

I need to trick a requirement of an exclusive access in Access 2000

P: n/a
Hello
I already initiated a thread with the same name on 22/03/2004. Thank
you everyone who answered me.
I wanted to link to that thread, but somehow there was no "Post follow
on article" link(?). Sorry for repetition, but the story has developed
a bit.
We have an Access 2000 database application - reports distributor.
Reports are created by developers, then reports and queries are copied
into a database (Access 2000 also) on network. It is called
repmanobjects. The application's front-end is on PCs. When a user
selects a report to run, the report and everything it needs is copied
from repmanobjects.
When I initiated the previous thread, there was one table in
repmanobjects, which recorded each report's execution. Since then, I
removed this table into another database. As a result, the only thing
repmanobjects is used for is to copy reports and queries from it,
which is done by the following command:
DoCmd.TransferDatabase acImport, "Microsoft Access", serverDB,
acReport, stDocName, stDocName
We, developers, need to export reports and queries into repmanobjects.
Now (after I have removed the registration table) we can export
queries, - no problem, but not reports. Any idea, why? What is the
difference between reports and queries as objects? What direction
should I search to sort out this little problem? Because to come to
work earlier then anyone else started working to copy reports prepared
yesterday into repmanobjects is a bit unpleasant.
Any help will be greatly appreciated.
Galina
Nov 13 '05 #1
Share this Question
Share on Google+
2 Replies


P: n/a
ga****@mail.ru (Galina) wrote:
Now (after I have removed the registration table) we can export
queries, - no problem, but not reports. Any idea, why?


Hi.

I don't think I have the answer to your question, but I'm rather curious
why you'd want to operate this way (ie exporting objects). Surely
distributing a front end container for reports would be the best method?

Regards,
Keith.
:o)
Nov 13 '05 #2

P: n/a
Keith
Because there are hundreds of reports and queries. Reports container
database is more then 20 Mb now. New reports or updates happen almost
every day, possibly not once a day. Each user needs only several
reports and doesn't use the rest. Distributing the application of such
volume every day, or several times a day will be unjust to the network
and users themselves.
Regards
Galina

Keith Wilby <ke*********@AwayWithYerCrap.com> wrote in message news:<Xn************************@10.15.188.42>...
ga****@mail.ru (Galina) wrote:
Now (after I have removed the registration table) we can export
queries, - no problem, but not reports. Any idea, why?


Hi.

I don't think I have the answer to your question, but I'm rather curious
why you'd want to operate this way (ie exporting objects). Surely
distributing a front end container for reports would be the best method?

Regards,
Keith.
:o)

Nov 13 '05 #3

This discussion thread is closed

Replies have been disabled for this discussion.