Macro Command Copy() doesn't work in OSX Tiger

[mdalgleish]

I have just started trying to move my files to OSX Tiger. Immediately
the macro command Copy() doesn't work. It is trying to work on 2
columns by 51 rows of a CSV file. I have tried saving the file to
excel. Interestingly Copy() does work earlier in the Macro. ANy
thoughts/help much appreciated.

 

[Bob Greenblatt]

I have just started trying to move my files to OSX Tiger. Immediately
the macro command Copy() doesn't work. It is trying to work on 2
columns by 51 rows of a CSV file. I have tried saving the file to
excel. Interestingly Copy() does work earlier in the Macro. ANy
thoughts/help much appreciated.

Exactly what is the error? What version of Excel? Have you updated to the
latest service pack? This used to be a bug when code was running from a user
form, but that has been fixed.

 

[mdalgleish]

The error is that when the macro gets to the cell it tells me there is
an error. Since writing the original question I have got passed the
copy command by bringing the requisite worksheet to the front BUT that
has just identified another problem - when running in the step mode the
windows don't change as a result of the MAcro (IOW the command activate
has no impact on which worksheet is in front)

I am using Excel 11.2 (according to the about Excel) and when I checked
for updates I was told there are none. Whether this means I have the
latest service pack I woulndn't know how to check for that.

At the present time of 5 lines of Macro code an hour I'm beginning to
think that Excel is not really ready for OSX Tiger yet and I should go
back to Excel in classic mode. Any thoughts on that?

 

[JE McGimpsey]

I have just started trying to move my files to OSX Tiger. Immediately
the macro command Copy() doesn't work. It is trying to work on 2
columns by 51 rows of a CSV file. I have tried saving the file to
excel. Interestingly Copy() does work earlier in the Macro. ANy
thoughts/help much appreciated.

Without seeing your code, it's impossible to tell what might be
happening. As Bob wrote, Copy used to not work from VBA, but that was
fixed.

I use Copy() reliably all the time in my apps.

 

[Bob Greenblatt]

The error is that when the macro gets to the cell it tells me there is
an error. Since writing the original question I have got passed the
copy command by bringing the requisite worksheet to the front BUT that
has just identified another problem - when running in the step mode the
windows don't change as a result of the MAcro (IOW the command activate
has no impact on which worksheet is in front)

I am using Excel 11.2 (according to the about Excel) and when I checked
for updates I was told there are none. Whether this means I have the
latest service pack I woulndn't know how to check for that.

At the present time of 5 lines of Macro code an hour I'm beginning to
think that Excel is not really ready for OSX Tiger yet and I should go
back to Excel in classic mode. Any thoughts on that?

From your description it sounds like you are using an XLM macro, not VBA.
Is this correct? Activate certainly works. Please supply some more detail
and a sample of the code that fails.

 

[mdalgleish]

You are correct (and mea colpa for not identifying that I was using an
XLM macro).

Since first writing the question I have got COPY() to work using the
new excel in OSX but am still struggling with Activate but given your
confidence let me take a couple more days. I should note that this
particular Macro is quite old and has worked from Excel 2.2 in system 7
on a Mac that I no longer remember the name of.

Thanks for your concern!

 

[mdalgleish]

OK I've done some more investigation and I am making progress. I'm not
sure I entirely understand what is going on but FireFox seems to be
interferring somehow with Excel.

Thank you for being so definitive!

 

[mdalgleish]

OK Excel in Mac whizzes I have done some more investigation and the
problem definitely happens using the step capability. In other words
the macro will run as long as the macro is 'running'. If the Macro is
slowed down to 'walking' pace by stepping thru it (this I like to do
when I am trying debug a Macro) the copy() function just doesn't work
reliably. I think this is the problem I was having at the earlier post.
Now I'd like to spend more time investigating this but I am now 10 days
behind getting real work done as I try to get these macros working
(issues still have to do with the access tree and naming conventions of
OSX v OS9 for downloads from the web). I hope you'll get someone to
look into this.

Thanks for you help.

 

[Bob Greenblatt]

OK Excel in Mac whizzes I have done some more investigation and the
problem definitely happens using the step capability. In other words
the macro will run as long as the macro is 'running'. If the Macro is
slowed down to 'walking' pace by stepping thru it (this I like to do
when I am trying debug a Macro) the copy() function just doesn't work
reliably. I think this is the problem I was having at the earlier post.
Now I'd like to spend more time investigating this but I am now 10 days
behind getting real work done as I try to get these macros working
(issues still have to do with the access tree and naming conventions of
OSX v OS9 for downloads from the web). I hope you'll get someone to
look into this.

Thanks for you help.

I don't believe that is the issue at all. If it works correctly when the
macro runs by itself, and fails when stepping, then the wrong sheet is
probably active. How are you initiating the step mode? Once in step mode are
you reactivating the correct sheet? I have been following this thread, and
think you are looking in the wrong area for the problem. I have found VERY
few issues where XLM macros do not work, or do not work properly in Excel
2004. As requested before, please supply a sample of the code and a clear
description of what you are finding wrong vs. what you are expecting. I'm
sure we can easily fix the problem.

 

[mdalgleish]

Ok I am happy to send you the XLM script and the worksheets that it
works on. I'm not sure how to do this so that they are not public.
Advise me an email address (privately if you want) and you'll get it
asap.

 

[mdalgleish]

Ok I am happy to send you the XLM script and the worksheets that it
works on. I'm not sure how to do this so that they are not public.
Advise me an email address (privately if you want) and you'll get it
asap.