Re: Learning VBA

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

Some information that may be of interest.

I contacted my brother-in-law about the possible module corruption and
I have now successfully re-built all three of them. The underlying
problem persists however.

It's worth noting though, that the original Excel file was created in
the Spanish version of Excel in Office v.X. My brother-in-law thinks
this could be part of the problem. He says that on his Spanish Office
2003 for Windows, the visual basic items are NOT localised. He notes
that in the Spanish Excel for Mac they ARE localised. Our Office 2004
for Mac is my copy from England and is therefore in English.

So internal identifiers or labels are given localised names on our
Spanish Mac Excel v.X (this is where the original file was created).
For example, 'image_1' would automatically be 'imagen_1' in our
Spanish Mac Excel. The same thing happens for the modules, 'module_1'
would automatically be 'módulo_1' on our Spanish Mac Excel (note the
accent in there).

When my brother-in-law opens the file on the Windows Office 2003 Excel,
the accent on the module name is replaced by a dash but the file works
correctly in spite of the name change.

I find it hard to believe that Microsoft would allow this kind of
difference to break compatibilty so feel the problem lies elsewhere.

After rebuilding the modules on the English Mac Excel 2004 the names
are now Module 1, Module 2 and Module 3.

Regards.

.