![\"CompileOnDemand\"](\"http:\/\/regina-whipp.com\/blog\/wp-content\/uploads\/2014\/03\/CompileOnDemand.jpg\")
<\/p>\n<\/p>\n
Recently, while trying to Debug some code a colleague of mine suggested I leave Compile on Demand1 <\/sup><\/b>unchecked.\u00a0 Since in all my years of developing I have always left it checked, I asked why and here’s what\u00a0he said\u00a0got…<\/p>\n Many years ago, Michael Kaplan mentioned that this setting was known to cause problems, at a Pacific NW Access Developer’s Group meeting.<\/p>\n Here is how having this Option checked can bite you in the patooka’s!\u00a0 Suppose you have unfinished code, or some other compile error, in code that you are not currently using. You forget to do a final Debug<\/strong> > Compile<\/strong>, to force all code to Compile. You deliver your app. to your customer. They immediately get a Run-Time error, with the same unused code. Why?\u00a0 Because this setting does not “travel” with your database; it is a global VBA environment setting. With this Option unchecked, ALL code must be compilable before any code can be run. Checking this option (the stupid default setting), allows for partial compliable; in other words, only the Modules that have code that you are running must be compilable. You could still have that experimental new module with code that does not Compile. Personally, I’d rather find these issues myself, instead of having a customer find them.\u00a0 <smile><\/p><\/blockquote>\n