Import query

[Guest]

When I import a query from one MDB to another, it would save alot of time if
the tables that related to this query will be moved also automatically.


----------------
This post is a suggestion for Microsoft, and Microsoft responds to the
suggestions with the most votes. To vote for this suggestion, click the "I
Agree" button in the message pane. If you do not see the button, follow this
link to open the suggestion in the Microsoft Web-based Newsreader and then
click "I Agree" in the message pane.

http://www.microsoft.com/office/com...-af09-7310f6314ca3&dg=microsoft.public.access

 

[John Vinson]

When I import a query from one MDB to another, it would save alot of time if
the tables that related to this query will be moved also automatically.

Umm....

WHY!!!?

Queries and tables are two *very* distinct types of entity. Copying
tables (rather than linking them) between different databases would be
redundant, and should be done only for very specific reasons.

What are you trying to *accomplish*, and why do you have multiple
databases containing the same table data and the same queries?

John W. Vinson[MVP]

 

[pietlinden]

When I import a query from one MDB to another, it would save alot of time if
the tables that related to this query will be moved also automatically.

I agree with John. I would _hate_ this. If you really wanted to, you
could write some code that grabbed all the dependent items imported
them. To have Access do what I didn't tell it to would _really_ annoy
me.

 

[Guest]

I should have been more specific, the tables that are moved from one mdb to
another are actually linked tables, and not the actual tables.
I work with 20 MDB's that are linked between them with reference, and it
happen that for some reason I need to move a query from one mdb to another,
sometimes it's a complex query that contain few tabes (linked), after
importing the query I need to specify which tables to import so the query
will run. (to be more clear, when you import linked tables it actually copy
the link and not the table with the data)

 

[Guest]

In addition, if I got an MDB that been used for some prcess's, and most of
them been canceled, I wont to create another mdb without the "Rubish", I
found that it's better to import what I need rather then delete what I don't
need, so when I import a query, I would like the related tables/queries to
move with it
--

 

[John Vinson]

In addition, if I got an MDB that been used for some prcess's, and most of
them been canceled, I wont to create another mdb without the "Rubish", I
found that it's better to import what I need rather then delete what I don't
need, so when I import a query, I would like the related tables/queries to
move with it

Thanks Ofer. That clarifies matters - I was wondering what the
background might be!

I'd still strongly prefer to go through the (rare, for me) bit of
extra work to import just what *I* want to import, rather than having
Access make arbitrary decisions for me; for instance, one scenario
might be that I want to import a query from one database into another
to adapt it to a different set of source tables.

John W. Vinson[MVP]

 

[Guest]

John, first thanks for you reply
In that case it would be easier to copy the SQL from one query to another
and then change the tables names, when you import the query and then open it,
if the tables are not located in that mdb, you will be prompt with error
message and the link between the table (that doesn't exist) will be removed
and the SQL will be different, so you wont be able to use it with different
tables (as the lnked are removed, so you don't have the original SQL)

There is no point to import a query if the tables/queries that relate to it
doesn't exist in the other mdb, so might as well bring them also.