compile error in hidden module

**Armidion** · 10-09-2007, 08:11 AM

Hello,

I was wondering if anyone knows how to fix this. I've sent out a worksheet with macros that call up userforms but when someone runs the form and tries to call up some userforms they get this error.

Thanks

**Armidion** · 10-09-2007, 10:47 AM

Just a bit of further information, This sheet has been run many times with different people and has functioned properly with no errors. This error popped up when I sent it to one of our Asian suppliers to use and it only seems to happen when they use the sheet

**Dean England** · 10-09-2007, 11:11 AM

There are different language versions of Excel. While the formulas and functions may work in your machine, they may not work in your Asian supplier's machine. That might be something to look at. In some instances the , (comma) is replaced by the ; semi-colon, etc.

HTH,

Dean

**royUK** · 10-09-2007, 01:33 PM

Attaching an example workbook containing that userform might help.

**Armidion** · 10-09-2007, 01:41 PM

Here is a workbook with the forms.

Regards,

**royUK** · 10-09-2007, 01:54 PM

You have used a calendar Control in the UserForm. The most probable cause is that the other computer does not have the Control installed. You can either install the ocx or create an alternative calendar instead. The datepicker & Calendar controls are often missing. There's a free DatePicker addin here

http://www.excel-it.com/free_addins.htm

**Armidion** · 10-09-2007, 01:58 PM

I've wondered if it was the calender ocx. I've asked them to install it and see if this resolves the issue.

I'm thinking it might be a part of the problem but the fact that all the buttons are affected and brings up the error is what leads me to think that there is something else that is causing the error as well.

**royUK** · 10-09-2007, 02:31 PM

What buttons are affected? It works Ok for me.

**Armidion** · 10-09-2007, 02:36 PM

This is the strange thing. It works fine for everyone in my office but when sent over to Asia none of the buttons work. everything they press brings up that error. Only one person has tried it so far so I've sent it to some other people just to make sure it isn't just an isolated problem

a previous poster has suggest that it may be a language version conflict so I'm trying to rule out everything else that I can think of.

If it does turn out that it is a language version conflict than I'll just have to suggest that they go and purchase a North American version of Office. I just don't want them to go and do that and still have this problem.

Thanks for everyone's help by the way