bewildering behavior changes between 2 different Mac G4 laptops

[Kent Eilers]

disclamer - i am a windows developer and not fluent with Macs.

I have an excel app that works on one G4 notebook but not the other. Both
have the same version of excel and the same OS (OS X).

When I open the app on the 2nd laptop it errors out in the workbook open
event working with a named range. Also some of the buttons are missing when
the app is opened on the 2nd laptop.

I originally did my development on Windows 2k, ported the app to the 1st G4,
discovered it basically didn't work, rewrote the visual elements (and some
code too) on the 1st G4 then copied the app onto a CD and transfered it to
the 2nd G4 - where it doesn't get past the open_workbook event.

Is there some preference configuration that is responsable for this? Why
would it work completely on the 1st G4 and not the 2nd?

Any ideas?

argh !

 

[Bob Greenblatt]

disclamer - i am a windows developer and not fluent with Macs.

I have an excel app that works on one G4 notebook but not the other. Both
have the same version of excel and the same OS (OS X).

When I open the app on the 2nd laptop it errors out in the workbook open
event working with a named range. Also some of the buttons are missing when
the app is opened on the 2nd laptop.

I originally did my development on Windows 2k, ported the app to the 1st G4,
discovered it basically didn't work, rewrote the visual elements (and some
code too) on the 1st G4 then copied the app onto a CD and transfered it to
the 2nd G4 - where it doesn't get past the open_workbook event.

Is there some preference configuration that is responsable for this? Why
would it work completely on the 1st G4 and not the 2nd?

Any ideas?

argh !

Are there linked sheets? Are there any hard coded paths that may be
different between the Macs? Will it work if you copy the app from the CD to
the mac's hard drive? Can you trap or identify what code in the open event
is causing the problem?

 

[Kent Eilers]

Thanks Bob for you reply )

sheets are not linked, no hard coded pathing, we copied the file to their
server with the same results - it opened fine from the G4 I did the
development on, and got the same error issue from the other G4.

I ported the app back to windows...and got the same error (I think)....after
fiddling around I reduced it to the following:

<< below 2 lines generates error>>
worksheets(1).activate
Worksheets("this month").Activate

<<these does NOT generated error>>
worksheets(2).activate
worksheets("this year").activate

so...do i have a corrupted worksheet? ..that the original G4 could talk with
and love anyway? I am doing this in the immediate window.

is there a way to 'recover' from a corrupted workbook aka MSAccess's
unsupported "/decompile " flag?

 

[Bob Greenblatt]

Thanks Bob for you reply )

sheets are not linked, no hard coded pathing, we copied the file to their
server with the same results - it opened fine from the G4 I did the
development on, and got the same error issue from the other G4.

I ported the app back to windows...and got the same error (I think)....after
fiddling around I reduced it to the following:

<< below 2 lines generates error>>
worksheets(1).activate
Worksheets("this month").Activate

<<these does NOT generated error>>
worksheets(2).activate
worksheets("this year").activate

so...do i have a corrupted worksheet? ..that the original G4 could talk with
and love anyway? I am doing this in the immediate window.

is there a way to 'recover' from a corrupted workbook aka MSAccess's
unsupported "/decompile " flag?

Sorry, I'm out of ideas. But, If you can send it to me I'll be happy to take
a look.

 

[Kent Eilers]

Thanks for the offer )

I'm going to copy the buttons on that worksheet to a new one, delete the old
one, rename the new one to the same name and see what happens.

I'll let you know if that does not work.

 

[Bob Greenblatt]

Thanks for the offer )

I'm going to copy the buttons on that worksheet to a new one, delete the old
one, rename the new one to the same name and see what happens.

I'll let you know if that does not work.

Sorry, I'm out of ideas. But, If you can send it to me I'll be happy to take
a look.

It also occurred to me that maybe more than one workbook is open, and you
macro code does not properly qualify which to refer to. Have you tried
modifying your code to:

Thisworkbook.worksheets(1).activate

Or workbook("whateveritsnameis").worksheets(1).activate

On second thought it is RARELY, if ever, necessary to activate a worksheet.
Is the worksheet perhaps hidden and therefore can not be activated? Try
changing your code to reference the sheet directly without activating it.