Object dependencies on macro?

[MVSGuy]

I need to move a fairly complicated (100+ report/query calls) to a
different database. How do I get an "object dependencies" from a
macro?

Regards,
MVSGuy

[David W. Fenton]

"MVSGuy" <kk*****@fuse.netwrote in
news:11**********************@i42g2000cwa.googlegr oups.com:

I need to move a fairly complicated (100+ report/query calls) to a
different database. How do I get an "object dependencies" from a
macro?

Eh?

Does the report depend on a macro?

For code dependencies, it's easy -- import the reports, then try to
compile the project. If there are outside code dependencies, you'll
get a compile error.

--
David W. Fenton http://www.dfenton.com/
usenet at dfenton dot com http://www.dfenton.com/DFA/

[MVSGuy]

For code dependencies, it's easy -- import the reports, then try to

compile the project. If there are outside code dependencies, you'll
get a compile error.

My apologies, perhaps I should have stated my case more clearly. I
need to copy a large macro with all the supporting objects from one
database to another. I'm doing this because there is a serious problem
with the original database. (Crashing when attemting to copy a report,
etc.)

A mass export/import will not work since for whatever reason, the
problem propogates to the new database.

Is there a function that allow me to specify a macro and give me a
report of all the supporting, reports, tables & queries?

I realize I can copy the macro over, run it and cut/paste whatever
object it spits out. This is pretty slipshod and could take quite some
time.

Is there an elegant way of doing this?

Regards,
MVSGuy

[David W. Fenton]

"MVSGuy" <kk*****@fuse.netwrote in
news:11*********************@p79g2000cwp.googlegro ups.com:

>For code dependencies, it's easy -- import the reports, then try
to compile the project. If there are outside code dependencies,
you'll get a compile error.

My apologies, perhaps I should have stated my case more clearly.
I need to copy a large macro with all the supporting objects from
one database to another. I'm doing this because there is a
serious problem with the original database. (Crashing when
attemting to copy a report, etc.)

Macros are an abomination. No serious Access developer would ever
use them, as there is no error handling.

I would try converting the macro to code, then reviewing the code to
see if that makes it clearer.

A mass export/import will not work since for whatever reason, the
problem propogates to the new database.

Is there a function that allow me to specify a macro and give me a
report of all the supporting, reports, tables & queries?

Not that I know of, but I don't use macros because they are
basically there for beginners, not for serious developers.

I realize I can copy the macro over, run it and cut/paste whatever
object it spits out. This is pretty slipshod and could take quite
some time.

Is there an elegant way of doing this?

Unfortunately, when you're working with an amateur, inelegant design
(i.e., one that depends on macros), you can't really expect
elegance.

--
David W. Fenton http://www.dfenton.com/
usenet at dfenton dot com http://www.dfenton.com/DFA/

[Lyle Fairfield]

MVSGuy wrote:

I need to move a fairly complicated (100+ report/query calls) to a
different database. How do I get an "object dependencies" from a
macro?

Assuming that you are using an mdb and a >=2000 version of Access the
code found at
http://www.ffdba.com/downloads/Save_...ts_As_Text.htm
MAY help.
It should copy make a copy of everything in the db to a new db in a
sub-folder to the folder where them db resides.
It also creates a text-manifestation of all the Access objects in the
db.

If there is are errors in one or more of the objects it should correct
the error if its something like a bad compilation, or baulk when it
tries to recreate the object. When it baulks it should give you a
message that will allow you to identify the object.

If you decide to use this, use the download link to get the dat file.
You should be able to import it into your VBA project easily, or simple
copy and paster the code. Save the new code module before you run it.
TTBOMK the code is harmless; regardless make a copy of your db and run
it from there to be extra safe.

I'm ambivalent about posting this as ... many posters describe their
problem to the extent that one is only guessing about the cure. Other
posters ... sigh.

[Lyle Fairfield]

Of course,

http://www.ffdba.com/downloads/What_..._An_Object.htm

trys to answer your question

but I am !!!!Guessing!!!! that the other helps with your problem.

[MVSGuy]

Lyle Fairfield wrote:

http://www.ffdba.com/downloads/What_..._An_Object.htm

This is best answer I've had so far!! I've added "On Error Resume
Next" since the rookie creating objects liked to put slashes in object
names. (And no, there was no formal naming structure. Sad.)

After I run the script, I do a simple search on the directory to find
all references to an object.

Thank you specifically to Lyle and to all the other experts who tried
to help,
MVSGuy