"Strict" VB compiler Eivind 12/10/2008 10:14:00 AM I have written some VB code as an addin for Excel 2003, which works fine on my computer. When transferring the code to a colleague, I get all sorts of error messages, even if he also uses Excel 2003. It seems that the VB compiler on my colleagues computer insists that all variables has to be declared. Furthermore, on his computer references as cells(i,j).value gives a type mismatch diagnostic when the cell is empty. And Application.WorksheetFunction.Sum(range) gives an error if some of the cells in range are empty. What can be the explanation for these differences? Any suggestions? Thanks!

Re: "Strict" VB compiler "Ken Slovak - [MVP - Outlook]" <kenslovak[ at ]mvps.org> 12/10/2008 2:49:05 PM This is an Outlook group, you will get better Excel answers if you post to an Excel group. -- Ken Slovak [MVP - Outlook] http://www.slovaktech.com Author: Professional Programming Outlook 2007. Reminder Manager, Extended Reminders, Attachment Options. http://www.slovaktech.com/products.htm "Eivind" <Eivind[ at ]discussions.microsoft.com> wrote in message news:E78AF61A-D6E7-4B7A-A4BF-4DF01AA58016[ at ]microsoft.com... [Quoted Text] >I have written some VB code as an addin for Excel 2003, which works fine on > my computer. When transferring the code to a colleague, I get all sorts of > error messages, even if he also uses Excel 2003. It seems that the VB > compiler on my colleagues computer insists that all variables has to be > declared. Furthermore, on his computer references as cells(i,j).value > gives a > type mismatch diagnostic when the cell is empty. And > Application.WorksheetFunction.Sum(range) gives an error if some of the > cells > in range are empty. What can be the explanation for these differences? Any > suggestions? Thanks!

RE: "Strict" VB compiler SolS. 12/19/2008 11:32:02 PM Your colleague's Option in VBA (VB) are set to Explicit - yours are not. You may have a missing variable or a variable that is not defined i.e. Dim mVar where on your colleague's machine Excel expects something like Dim mVar as (String, Integer, Double - one of the definition types). It is safer and better to have the Option Explicit set, so I might suggest you do so on your machine, recompile the code and then when you port it to another machine it will work. Sol. "Eivind" wrote: [Quoted Text] > I have written some VB code as an addin for Excel 2003, which works fine on > my computer. When transferring the code to a colleague, I get all sorts of > error messages, even if he also uses Excel 2003. It seems that the VB > compiler on my colleagues computer insists that all variables has to be > declared. Furthermore, on his computer references as cells(i,j).value gives a > type mismatch diagnostic when the cell is empty. And > Application.WorksheetFunction.Sum(range) gives an error if some of the cells > in range are empty. What can be the explanation for these differences? Any > suggestions? Thanks!