1004 application defined error

[charliec]

hi, i have 2 macros that run fine by themselves, but when I try to combine them into one i get a "run-time error '1004' application-defined or object defined error" and don't know why. the error is in the SetupVariables macro at the line listed below, but it works fine in other macros since it is used to set up the variables. any ideas why i am getting this error?

Please Login or Register  to view this content.

the daily_file assignment is flagged in the SetupVariables macro (below), but not the first assignment line for the business plan. if i comment out that daily_run line it flags the next eligibility_file line.

Please Login or Register  to view this content.

[Greg M]

Hi there,

It's difficult to be certain without access to all of your code, but I suspect that the dreaded "not-fully-qualified reference" strikes again!

In the problem line:

Please Login or Register  to view this content.

the code will look for a worksheet called "inputs" in whichever workbook happens to be active when the line is executed, and will generate that error message if it is unable to find such a worksheet.


To avoid situations like this you should always use fully-qualified references, e.g:

Please Login or Register  to view this content.

or

Please Login or Register  to view this content.

Hope this helps - please let me know how you get on.

Regards,

Greg M

[charliec]

hi greg, i suspected it was something like that, but still don't understand why it works in other macros even though the same SetupVariables macto is called. however, i did use the fully qualified reference method to reference the file where the SetupVariables refers to without having to fully qualify all the lines and that seems to work. thx again.

[Greg M]

Hi again,

Many thanks for your feedback.

You're welcome - glad I was able to help.

As far as:

but still don't understand why it works in other macros

is concerned, it all depends on which workbook is active when the routine is activated. Given that your routines open other workbooks, there is no guarantee that the "correct" workbook is active when the routine executes.


Regards,

Greg M