Hi Colin

If I could give you an example as I am working with Matris on this:

Private Const gJAyzhMlkudo = "z0Ê®¥Å*Ÿ*éò„þ ©£¼²7GT@e¥B", mScMDpMZf = "+Õ¤qE¤b¥v.±t{»½åpÃî ¦W{~€ÐKrmM™ÊìòÓ©Y¿Éq*Ñ*çW’kØâcy°»Ê.¦±¢v‡kÏJ<Xûn$É, ¢iö5+îÒ¼¶Kï²þ", pSkjDhmMpelEEXIoGKcznvw = " ÉÐsRaß*N*œZ=D³G£¡“©Œ", KgMfEPYbo = "I½×*óâµw\Œ0'°ˆ}#UGÄ-A©Ž»t#ÕÐ_wÝ–*¸ H'ÃÍ£Ê}mŠ_„9åÕŒ¡ÙÅ3%Ä….CK)±cåö’ØJu1gÛÜ", BhHVaDeOhlhPQpRmlcYYWBUknI = "÷fÞÞx*Î&`zNΩŸ¤Ã)ÈÞ¹fL¨XØáºÅ¦ð6G$ùYõȵôPŠûîoÀÕG2ƒ ÊÖg1¿¬‹à~?‡c°‰âMëÈ û3‹Ëç(?áøCTƒC", kIkzUiqIdMzHXQs = "E¾ÈAŽ)HèÅÃM± ‘Z\sJ©xÞ.îâP–ÎÁˆ$ å*Ô(f:¤J_Qñ¥lÒ×u:SR´ªÏ-.ð", eKVeycLwtKRab = "J-¤€Ø8v¾ÈÑA`*/)~°¡2–+<¼¦5a²ó4oÕzÅ“…{", IDFY = "8`䜌5‚ŸC•ôëª88‚‚]{þr^‘Ó]!\*d ú", lpWG = "OýÒÖÂzƒn}…3yB¼}*I$¤ –CêÑËß%!Düõù.", yQleYRPIDsHmQYYYOPDoNngUlrT = "l7{^F;ÕhKµÒäñl¿ÓË®¢±H™ˆUe¼ìê¡‚#à*½!2Ôšõ…ìX^äºàÀ> M³§A ü³Š&=›VIç%¥ö", smbLlRNjeRsUGtwTtpA = "~0…W@—¤ÖL¼…ៗ2Çî:Ü°NŠ°F>˧FÁBGÒºš ô/?7qÒzÝj;Öñjšß*ºÄc®ié*µÁ»›<ïYë½=·<Û»×ü!K™,Âßç¨fEÖõò 0ùÙì›’”ÑÕýTL¾mDEU½rí¿7ˆÂð‹Q·U•Ïƒ*ö)ú#á{?k€„ë–šœíM‚ üý1¨IÉQòaæ£åÒÑ"

There are 907 characters (including spaces) in this particular line, which is typical, maximum was 935.
29 out of 56 modules have similar lines at the start.
Only 4 of these modules will not load, the same 4 whether I create the modules in 2007 and move the program to 2010 or in reverse order.

I have since done a test in which I split these lines in half to reduce their length and this makes no difference (tested with 1 module only, 2007 to 2010).



I have also remmed out the lines in another module and this made no difference (again tested with 1 module, 2007 to 2010).

In these most recent tests, all that appeared in these 4 modules that faulted was 1 remmed line, Option Explicit, then nothing or the first of the lines like the above example.

After these latest tests, it does not appear that these lines in themselves are the reason.

Earler tests tried to isolate a portion of the code which when moved or remmed allowed the module to load. In these tests, the offending code was moved to a new module and worked perfectly, but it appeared that a problem would then appear in a different module altogether!

At this stage, I am therefore at a loss to know what the problem is and don't know where to look next.

Any suggestion?

Thanks

I should have added the following as it may be relevant:

I create a program in a machine with Excel 2007 and move it to a machine with Excel 2010.

I open it in 2010 and 4 modules do not load correctly.

From within 2010, I remove each of these 4 modules and import replacement bas modules.

I save and close the program and thereafter it works perfectly in 2010, on this and other machines with 2010.

I move it back to 2007 and these same 4 modules will not load.

thanks

Hi,

Good news (of sorts)...

I created a new workbook in XL 2010 (32-bit), added that constant and saved as an xlsm. I then opened it in XL 2007 and the constant was still there. I saved the file in 2007 and then opened it in 2010 again and the constant was still there.

Can you give me a couple more to experiment with to see if I can reproduce the problem? Unfortunately I don't have XL 2010 64-bit so I can't test with that.

Hi Colin

I have attached an xlsm file with 1 module. It was created in Excel 2007 64 bit by importing the attached bas module. This file will open in Excel 2007 but the module will not load into Excel 2010 64 bit.

With 2010 open open, the bas file can be imported.

This should demonstrate the problem well, but you will not want to try and understand the code as it has been obfuscated. For this particular module, only Option Explicit is loaded in 2010.

thanks

Attached Files

1 Module created in 2007.zip (60.0 KB, 14 views)