Macro rot ? Suggestions apreciated

  • Thread starter Thread starter Loup Vergez
  • Start date Start date
L

Loup Vergez

Hello all, I hope anyone could point me to a useful suggestion.
I am having a very strange problem with an excel VB macro.
Here is what happens:
A excel 97 spreadsheet contains a dozen of macros, all imbedded and
they make no external reference to external DLL's, ActiveX objects or
such.
The Macros are locked for vewing and editing with a password.
Everything runs fine until the spreadsheet is saved (even with no
changes done) from any other PC than the one it was created on.
At this point, the macro displays a message indicating an error in
hidden module X on startup.
If the spreadsheet (who lives on a shared network drive) is saved
(with or without modifications, that has no influence) there by the PC
on which it was created, all is fine, the macro runs.
When someone else opens the spreadsheet, the macro is still usable,
but ceases to work when document is saved.
The pc wher macro was written is fitted With excel 97, nearly all
others have 2K. I tried to install 2K on said PC but that did not
solve problem.

It would be very helpful if anyone had an idea in which direction I
should look to find a solution or explanation to this problem.
 
Hi,

My simple suggestion is to get rid of the password. In
that way you can hit "Debug" in the messagesbox (the one
that is disabled now) and see what is wrong. This should
give you a hint instead of guessing.

Good luck!

/Nicke
 
Nicke said:
Hi,

My simple suggestion is to get rid of the password. In
that way you can hit "Debug" in the messagesbox (the one
that is disabled now) and see what is wrong. This should
give you a hint instead of guessing.

Good luck!

/Nicke
Click to expand...
Hi Nicke,
Thanks for the suggestion. I am not the author of the macro, but tried
this anyway.
Debugging gives very few info, only things such as 'error on line X'
Whenever i comment out that line, an error is reported on next line
and so and so.

What really bugs me is the way those errors happend.
Let me try to summarise:

Machine X : machine running Office 97 on which macro was developped.
Machine Y : any other machine, running Office 2K

1. Machine X opens Sheet, executes macro. all ok
2. Machine Y opens Sheet, executes macro. all still ok
3. Machine X saves Sheet ( with no change in the macro) Still ok on X
and Y
4. Machine Y saves Sheet (still while not changing the macro code) :
Macro now bugs on X, but functions on Y.

Keep in mind that the macro is password protected, so change to the
macro code in step 4 is not possible.
This is really intriguing, If anyone had experience of such things
before, I reqlly would like to hear from it.
Thanks in advance
 
Hello Everyone again.
I still searched a bit everywhere but found no explaination nor
solutions for this peculiar behaiviour.
If anyone has any idead of what could cause this, or could point me to
some resosurce, I would very much appreciate.
thanks in advance for your time and feedback.
Loup Vergez
 
Back
Top