I have solved my problem. Or at least it has seemed to clear up. The
problem was at least partially, if not entirely, due to my sending my
customers an updated addin file thinking they were using the latest
full release of my application, but they weren't. So they had a
mixing of old and new application files.

I need to put some effort into having my application files check each
other for version compatibility. I hope that can be done without
triggering compile errors. I guess I could use the trick of fetching
a value from a worksheet cell before opening an addin or workbook.

Cheers,

Brian Murphy



"Brian Murphy" wrote in message ...
One user is in France. He has sent me screen shots of the error
message. I sent him the unprotected code thinking he could click the
"debug" button, and see the offending line of code.

This didn't work since he then got the "macro not found" message from
Addin1 that was still protected.

I have since sent him both addins unprotected. But it will take some
time to hear back from him because of the time difference.

The other user is actually just a prospective customer at the moment.
So I would really like to fix this quickly without bugging him.

I will email you the two addins. Load addin2 which is named
xlrotorto.xla. The reference to xlrotor.xla will cause it to get loaded
also (this is Addin1).

Then you can just see if you get a compile error.

Brian


"Bob Phillips" wrote in message
...
Brian,

That is normal. An error in a protected book shows as error in hidden
module, which then becomes clearer if unprotected.

Even though I have Broadband, I am not inclined to download 18Mb
(especially
as Rotating Machinery holds no interest for me <vbg). Could you not
get the
user who gets an error on the unprotected sheet to send you a screen
print
so that you could work out where the error is?

--

HTH

Bob Phillips
... looking out across Poole Harbour to the Purbecks
(remove nothere from the email address if mailing direct)

"Brian Murphy" wrote in message
...
Hello Bob,

Thanks for the reply.

I don't really know what code is causing the error.

The best detail I can give you at the moment is that the customer
using
Excel 2003 build 5612 got the compile error when I sent him the new
protected version of the file. Then when I sent him an unprotected
version
he got the "macro not found" error. I got no errors when I tried it
on a
system with office 2003.

If you want to see if you get the error yourself, download the huge
file
www.xlrotor.com/xlrotowm30.exe which is 18 megabytes. Run this to
install
my application, when prompted the password is 'turbine'. Replace the
installed file named "xlrotorto.xla" with my new questionable one.
Send me
an email directly to let me know you want it, and I'll email it to
you, it's
about 1 megabyte.

Load the example file that comes with the program named "XLTorsion
Example,
Ehrich 2.xls". Click the 4th button on the xlrotor toolbar. If you
don't
get an error, click the 5th button, and answer YES to overwrite the
worksheet. If you still don't get an error, then it evidently runs
okay on
your system.

Brian






"Bob Phillips" wrote in message
...
Well that is as expected, so the code must have an error on some
other
system.

Post the code that errors.

Which systems throw errors?

--

HTH

Bob Phillips
... looking out across Poole Harbour to the Purbecks
(remove nothere from the email address if mailing direct)

"Brian Murphy" wrote in message
...
The compile error is something that led to the macro not found
problem.

Here's the story.

The addins, there are two involved, are my own. I've been
distributing
these for years (www.xlrotor.com).
Addin1 is the primary addin.
Addin2 is secondary.
Addin2 is opened by Addin1 as needed,
and Addin1 uses Application.Run to run routines in Addin2.
Addin2 has a "reference" set to Addin1 so it can freely call
routines in
Addin1.
Both addins are "locked for viewing" and passworded, this done with
excel
2002.
So far, so good.
I've been doing it this way for years.

I recently made some minor edits in Addin2, and have sent this to 4
customers. Two of the customers have reported "compile error in
hidden
module: module name". Although they named different modules. I had
fully
compiled and saved the addin before sending it to them. I tested
the
addin
with excel97, 2000, 2002 and 2003, with no problems.

I sent a version of Addin2 that is not locked or passworded to one
customer,
and now he gets the "macro not found" message when Addin1 tries to
run a
macro in Addin2. He's using Excel 2003. The .Run command doesn't
get
executed without my Addin1 first making sure Addin2 is open.

I have no clue as to what the problem might be. I cannot reproduce
them.

It would be nice to know how they can get a "compile error" when I
send it
to them fully compiled. Since that is what started all this.

Brian





"Bob Phillips" wrote in message
...
Brian,

The error has changed from an can't find macro error to error in
hidden
module.

Did you write the addin, or is it a commercial one? Can you open
the
addin
up and find the spot it errors?

--

HTH

Bob Phillips
... looking out across Poole Harbour to the Purbecks
(remove nothere from the email address if mailing direct)

"Brian Murphy" wrote in message
om...
Thanks for the reply, Bob.

These are macros that I've been using for years. Now all of the
sudden two customers are getting the "compile error in hidden
module"
messages in a new file I recently sent them. The file checks
out fine
for me with excel 97, 2000, 2002 and 2003. So I'm baffled.

Brian


I don't have any idea what the problem could be. I send the
offending
file

"Bob Phillips" wrote in
message
...
It could be a private sub.

It may not be in a standard code module.

It may be in an other workbook.

By your last statement,did you include the addin name in the
run
statement?

--

HTH

Bob Phillips