Salakhetdinov Shamil
mcp2004 at mail.ru
Sun Jan 1 13:37:50 CST 2012
Hi Mark -- Back to year 2004 I have had an issue with MS Excel 2003 when exporting VBA, creating new XL Add-In workbook and importing VBA back didn't help to solve p-code corruption issue: that XL Add-in workbook have had quite a few of class modules - that was the cause of trouble I guess. Since then I have been trying to use VBA as little as possible... BTW that troublesome XL VBA add-in was flawlessly converted into VB.NET VSTO XL add-in. Thank you. -- Shamil 01 января 2012, 22:39 от "Mark Simms" <marksimms at verizon.net>: > Interestingly Charlotte I had to use the VBE.VBPROJECT object in Excel to > set references. > Excel 2010's VBE is exhibiting the same p-code corruption behavior as Access > 2010. > So I had to create my own "eatbloat"....export all of the modules and forms, > delete em, recompile, close, open again, import all of the VBA source, > re-establish 12 references, recompile. > > > To make it work in a 2002/2003 version, you had to reference the VBE > > library and use its methods because you can't use DAO or ADO and VBA to... > > -- > AccessD mailing list > AccessD at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/accessd > Website: http://www.databaseadvisors.com >