It doesn't sound like you are using
OCWebPreview ActiveX Control Module



So the easiest would be to remove it from the reference list on your
computer, then save the file, then redistribute. (go into tools=References
in the VBE and uncheck this reference)



The problem is probably caused by this missing reference, even though it has
nothing to do with the error flagged. Once you get rid of the reference,
your problem should go away.



--

Regards,

Tom Ogilvy



"Big Chris" wrote in message
...
Code works in XL2000 but not in XP!?
Please can anybody help?......and thanks in advance for looking.

I'm using the code below on a number input macro to check to see if the
number entered is the same as the validation code in hidden sheet1!A1.

It works perfectly in Excel 2000 but a user reports that in Excel XP he
gets the message: "Compile error in module 2". When I looked at it it
appears that the problem is at the point of 'MyNum' in the 6th row.

-------------------------------------------------------------

Sub InputNumber()
Application.ScreenUpdating = False
Application.EnableCancelKey = xlDisabled
Sheets("Sheet1").Visible = True
Sheets("Sheet1").Select
myNum = InputBox("Please enter your 8 digit validation code. If you
don't know it please contact XXXX", "Box Title")
If myNum = "" Then
Sheets("Sheet1").Visible = False
Sheets("Setup Sheet").Select
Application.ScreenUpdating = True
Exit Sub
End If
Range("A1").Value = myNum
Sheets("Sheet1").Visible = xlSheetVeryHidden

Sheets("Setup Sheet").Select
Application.ScreenUpdating = True
End Sub
-------------------------------------------------------------

Jim Rech advised me to look in 'Tools' and 'References.' in the VBE to
see if anything was listed as 'missing', and in there it says "MISSING:
OCWebPreview ActiveX Control Module".

This needs to be usable by anyone with XL2000 or later. Can you anyone
suggest a work-around that would enable this to happen? Different code
maybe that gives the same results?

How can I overcome this even on a single PC?

Can I get an auto-open macro to make whatever changes are required to
make it work or should I look for an alternative code that won't cause
this to happen?

Thanks for your help.

Regards,


---
Message posted from http://www.ExcelForum.com/