Comments on: Bogus Compile Errors http://www.dailydoseofexcel.com/archives/2008/02/04/bogus-compile-errors/ Daily posts of Excel tips…and other stuff Wed, 08 Feb 2012 23:58:05 +0000 hourly 1 http://wordpress.org/?v=3.2.1 By: Paul Sasur http://www.dailydoseofexcel.com/archives/2008/02/04/bogus-compile-errors/#comment-66760 Paul Sasur Wed, 05 Oct 2011 16:27:00 +0000 http://www.dailydoseofexcel.com/?p=1806#comment-66760 <p>I stumbled across this problem, specifically on (2) machines running Visio 2010. The control in question was a Listview, which is in the same Common Controls library as the treeview. Delection of the MSCommctrlLib.exd fixed teh initial problem, but I am still battling an issue where the properties and methods of the control are not recognized... but only on one specific userform. When other userforms containing listviews are run, there is no problem. Only one specific userform, but the twist is that I have listviews contained in a multipage control, which has been well documented as a source for strange behaviours. Wondering if anyone else has seen this.</p> I stumbled across this problem, specifically on (2) machines running Visio 2010. The control in question was a Listview, which is in the same Common Controls library as the treeview. Delection of the MSCommctrlLib.exd fixed teh initial problem, but I am still battling an issue where the properties and methods of the control are not recognized… but only on one specific userform. When other userforms containing listviews are run, there is no problem. Only one specific userform, but the twist is that I have listviews contained in a multipage control, which has been well documented as a source for strange behaviours. Wondering if anyone else has seen this.

]]> By: Rene http://www.dailydoseofexcel.com/archives/2008/02/04/bogus-compile-errors/#comment-39415 Rene Wed, 20 May 2009 09:36:00 +0000 http://www.dailydoseofexcel.com/?p=1806#comment-39415 <p>Nothing helps! I still get this error message with Office 2003. Luckily we get Office 2007 soon and I can use the name manager again! Great tool anyway!</p> Nothing helps! I still get this error message with Office 2003. Luckily we get Office 2007 soon and I can use the name manager again! Great tool anyway!

]]> By: Dick Kusleika http://www.dailydoseofexcel.com/archives/2008/02/04/bogus-compile-errors/#comment-30994 Dick Kusleika Thu, 28 Feb 2008 16:21:00 +0000 http://www.dailydoseofexcel.com/?p=1806#comment-30994 <p>John: You don't "have" to compile it, no. It does get compiled when you run it and compiling before running does a couple of things for you. It tells you if you have any errors before you run it. It also converts your code into something called p-code (I think). Basically there's two compilation steps in VBA: Text to p-code, p-code to machine code. When your code is fully compiled in the VBE, it removes one of those steps that VBA has to do before it can run. You should always compile your code before you "release" it into the wild.</p> John: You don’t “have” to compile it, no. It does get compiled when you run it and compiling before running does a couple of things for you. It tells you if you have any errors before you run it. It also converts your code into something called p-code (I think). Basically there’s two compilation steps in VBA: Text to p-code, p-code to machine code. When your code is fully compiled in the VBE, it removes one of those steps that VBA has to do before it can run. You should always compile your code before you “release” it into the wild.

]]> By: jkpieterse http://www.dailydoseofexcel.com/archives/2008/02/04/bogus-compile-errors/#comment-30852 jkpieterse Thu, 21 Feb 2008 12:46:00 +0000 http://www.dailydoseofexcel.com/?p=1806#comment-30852 <p>Sometimes it helps to remove the profile (I know, a royal PITA!) and recreate it.</p> Sometimes it helps to remove the profile (I know, a royal PITA!) and recreate it.

]]> By: jeng02 http://www.dailydoseofexcel.com/archives/2008/02/04/bogus-compile-errors/#comment-30839 jeng02 Wed, 20 Feb 2008 20:18:00 +0000 http://www.dailydoseofexcel.com/?p=1806#comment-30839 <p>I'm sorry to say that I cleaned out all the .exd files out of my user profile, but Name Manager still crashes Excel with that compile error every time I try to edit a name's reference text.</p> <p>I am using XP Pro, Excel 2003, 11.8169.8172 SP3.</p> <p>Name Manager is still a great tool. I'll just have to do my edits in the normal Names dialog.</p> I’m sorry to say that I cleaned out all the .exd files out of my user profile, but Name Manager still crashes Excel with that compile error every time I try to edit a name’s reference text.

I am using XP Pro, Excel 2003, 11.8169.8172 SP3.

Name Manager is still a great tool. I’ll just have to do my edits in the normal Names dialog.

]]> By: jeng02 http://www.dailydoseofexcel.com/archives/2008/02/04/bogus-compile-errors/#comment-30838 jeng02 Wed, 20 Feb 2008 19:57:00 +0000 http://www.dailydoseofexcel.com/?p=1806#comment-30838 <p>How about adding a check to the Name Manager install workbook that checks for 1) Excel 2003 (most problematic?), and 2) problematic .EXD files, and then warns the user?</p> <p>I just had the compile error crash Excel for me... Still, I don't want to seem ungrateful. Name Manager is really cool!!</p> How about adding a check to the Name Manager install workbook that checks for 1) Excel 2003 (most problematic?), and 2) problematic .EXD files, and then warns the user?

I just had the compile error crash Excel for me… Still, I don’t want to seem ungrateful. Name Manager is really cool!!

]]> By: jkpieterse http://www.dailydoseofexcel.com/archives/2008/02/04/bogus-compile-errors/#comment-30464 jkpieterse Wed, 06 Feb 2008 16:39:00 +0000 http://www.dailydoseofexcel.com/?p=1806#comment-30464 <p>Well, it is not certain which exd file(s) may be corrupt. Best is to just remove all of them, if absent they will be recreated the next time Excel needs them anyway.</p> Well, it is not certain which exd file(s) may be corrupt. Best is to just remove all of them, if absent they will be recreated the next time Excel needs them anyway.

]]> By: doco http://www.dailydoseofexcel.com/archives/2008/02/04/bogus-compile-errors/#comment-30462 doco Wed, 06 Feb 2008 14:57:00 +0000 http://www.dailydoseofexcel.com/?p=1806#comment-30462 <p>Is this an issue with all exd files or just those you have listed? Don't know if what I am about to explain is related or not...<br> I also have created an add-in (originally created in Office 2000 and now running 2003) with about a half dozen utilities that require use of tabbed control on a form (custom wizard). I have it on two laptops and two desktops. It always worked great until the last year every now and then I began getting error message stating "could not load an object because it is not available on this machine." I trace the problem to the tabbed control and in fact it is on the machine. Deletion of the add-in and reloading it usually eliminates the problem. I currently have that problem on this laptop, but deleting those exd files didn't seem to do the trick.<br> How is it something like an add-in can work merrily along without a hitch and suddenly its broken?</p> Is this an issue with all exd files or just those you have listed? Don’t know if what I am about to explain is related or not…
I also have created an add-in (originally created in Office 2000 and now running 2003) with about a half dozen utilities that require use of tabbed control on a form (custom wizard). I have it on two laptops and two desktops. It always worked great until the last year every now and then I began getting error message stating “could not load an object because it is not available on this machine.” I trace the problem to the tabbed control and in fact it is on the machine. Deletion of the add-in and reloading it usually eliminates the problem. I currently have that problem on this laptop, but deleting those exd files didn’t seem to do the trick.
How is it something like an add-in can work merrily along without a hitch and suddenly its broken?

]]> By: john http://www.dailydoseofexcel.com/archives/2008/02/04/bogus-compile-errors/#comment-30459 john Wed, 06 Feb 2008 12:26:00 +0000 http://www.dailydoseofexcel.com/?p=1806#comment-30459 <p>hi there<br> now slap me for being stupid ....but do you have to compile your vba<br> as i have never actually compiled mine and it all still works<br> sorry for being a right nana</p> <p>john</p> hi there
now slap me for being stupid ….but do you have to compile your vba
as i have never actually compiled mine and it all still works
sorry for being a right nana

john

]]> By: Jon Peltier http://www.dailydoseofexcel.com/archives/2008/02/04/bogus-compile-errors/#comment-30446 Jon Peltier Tue, 05 Feb 2008 23:33:00 +0000 http://www.dailydoseofexcel.com/?p=1806#comment-30446 <p>It is surprising, because several of us seem to have just recently stumbled across it. I think I've only seen it affecting Excel 2003, and I don't know whether the affected installations had upgraded to SP3.</p> It is surprising, because several of us seem to have just recently stumbled across it. I think I’ve only seen it affecting Excel 2003, and I don’t know whether the affected installations had upgraded to SP3.

]]>