I have been using Application.run for years, and all of a sudden on this
computer, it has stopped working when I open a file. Note this does not
occur on all machines for some odd reason.

Here is a code snipet.

Code_file = "stl_code.xls"

Workbooks.open FileName:=ATL_Path, ReadOnly:=True
Application.Run Macro:=Code_File & "!Stl_Init"

If I put a stop on Application.run -- and try to step through this,
application.run just never executes. It just sits there every press of
"step into". However if I just press the play button - the code eventually
gets through this, but from what I can see never runs this stl_init procedure,
as there are variable set.

I am running Excel Version 2002 (10.6823.6825) SP3.

I have run into issues like this in the past -- where long files names --
those in code_file are longer than 15 characters -- just reduced the filename
size. But this one I cannot figure out, and I cannot trap on it either.

As inidcated earlier -- it seems to work fine on another machine -- same
Excel version as indicated above.

If this is just a sample workbook name, maybe you could try this:

Application.Run Macro:="'" & Code_File & "'!Stl_Init"

(Notice the extra apostrophe in the last portion, too.)

testingguy2007 wrote:
>
> I have been using Application.run for years, and all of a sudden on this
> computer, it has stopped working when I open a file. Note this does not
> occur on all machines for some odd reason.
>
> Here is a code snipet.
>
> Code_file = "stl_code.xls"
>
> Workbooks.open FileName:=ATL_Path, ReadOnly:=True
> Application.Run Macro:=Code_File & "!Stl_Init"
>
> If I put a stop on Application.run -- and try to step through this,
> application.run just never executes. It just sits there every press of
> "step into". However if I just press the play button - the code eventually
> gets through this, but from what I can see never runs this stl_init procedure,
> as there are variable set.
>
> I am running Excel Version 2002 (10.6823.6825) SP3.
>
> I have run into issues like this in the past -- where long files names --
> those in code_file are longer than 15 characters -- just reduced the filename
> size. But this one I cannot figure out, and I cannot trap on it either.
>
> As inidcated earlier -- it seems to work fine on another machine -- same
> Excel version as indicated above.

--

Dave Peterson

Hi Dave,

I read a hint like this, this morning. However that did not work either.
It seems that Excel gets stuck, as when I put a break on it, I cannot even
step into it - 100's of step into tries, as it just eventually just gives up.

I thought my security - which is set to LOW now -- was the issue, but still
it just gets stuck executing the code.

Do you have another suggestion?

Thanks


Dave Peterson wrote:
>If this is just a sample workbook name, maybe you could try this:
>
>Application.Run Macro:="'" & Code_File & "'!Stl_Init"
>
>(Notice the extra apostrophe in the last portion, too.)
>
>> I have been using Application.run for years, and all of a sudden on this
>> computer, it has stopped working when I open a file. Note this does not
>[quoted text clipped - 21 lines]
>> As inidcated earlier -- it seems to work fine on another machine -- same
>> Excel version as indicated above.
>

No, I don't.

If you create a couple of test workbooks with simple macros, do they behave
better?

I'm not sure how that will help, but maybe it'll give you a clue what is
different?????

testingguy2007 wrote:
>
> Hi Dave,
>
> I read a hint like this, this morning. However that did not work either.
> It seems that Excel gets stuck, as when I put a break on it, I cannot even
> step into it - 100's of step into tries, as it just eventually just gives up.
>
> I thought my security - which is set to LOW now -- was the issue, but still
> it just gets stuck executing the code.
>
> Do you have another suggestion?
>
> Thanks
>
> Dave Peterson wrote:
> >If this is just a sample workbook name, maybe you could try this:
> >
> >Application.Run Macro:="'" & Code_File & "'!Stl_Init"
> >
> >(Notice the extra apostrophe in the last portion, too.)
> >
> >> I have been using Application.run for years, and all of a sudden on this
> >> computer, it has stopped working when I open a file. Note this does not
> >[quoted text clipped - 21 lines]
> >> As inidcated earlier -- it seems to work fine on another machine -- same
> >> Excel version as indicated above.
> >

--

Dave Peterson