Microsoft KB Archive/186174

= XL98: Conditional Compilation Code Lost With 5.0/95 Format =

Article ID: 186174

Article Last Modified on 6/17/2005

-

APPLIES TO


 * Microsoft Excel 98 for Macintosh

-



This article was previously published under Q186174



SYMPTOMS
If you use the Save As command on the File menu to save a document in Microsoft Excel 5.0/95 Workbook format, you lose any Conditional Compilation directives in your Visual Basic for Applications code.

NOTE: When saving your document in Microsoft Excel 5.0/95 format, you are not warned that your code will be lost.



CAUSE
Conditional Compilation directives are not used in earlier versions of Visual Basic for Applications and Microsoft Excel.



RESOLUTION
If you have already saved your document in the Microsoft Excel 5.0/95 Workbook format, you must open the file in Microsoft Excel 98 and retype the Conditional Compilation directives.

If you have not saved your file in the Microsoft Excel 5.0/95 Workbook format and you want to preserve your Conditional Compilation directives, comment out the Conditional Compilation directives and save the file in the Microsoft Excel 5.0/95 Workbook format.



MORE INFORMATION
You can use Conditional Compilation directives (for example, #IF...THEN...#ELSE) to run selective blocks of code. Typically, this is used in cross-platform Sub procedures. The #IF...THEN...#ELSE directives evaluate expressions containing conditional compiler constants to determine what code to execute in the macro.

Microsoft provides programming examples for illustration only, without warranty either expressed or implied. This includes, but is not limited to, the implied warranties of merchantability or fitness for a particular purpose. This article assumes that you are familiar with the programming language that is being demonstrated and with the tools that are used to create and to debug procedures. Microsoft support engineers can help explain the functionality of a particular procedure, but they will not modify these examples to provide added functionality or construct procedures to meet your specific requirements. The following macro provides an example of using conditional compilation:

 Save and close any open workbooks, and then open a new workbook. Start the Visual Basic Editor by pressing OPTION+F11. On the Insert menu, click Module.  In the module, type the following code: #Const test = 1

Sub Cond_Comp

#If test Then MsgBox "test evaluates to True"

#Else MsgBox "test evaluates to False"

#End If

End Sub  Run the Cond_Comp macro.

Because the conditional compilation constant "test" has a value of one, a message box will display the message "test evaluates to True".  Change the first line of code in the module to: #Const test = 0 </li> Run the Cond_Comp macro.

Because the conditional compilation constant "test" has a value of zero, a message box will display the message "test evaluates to False."</li></ol>

Conditional compilation constants can also be specified in the Project Properties dialog box instead of in a module. To use this technique in the previous example, follow these steps:

<ol>  Comment out the first line in the module so that it looks like the following: '#Const test = 0 </li> On the Tools menu, click VBAProject Properties, and click the General tab.</li>  In the Conditional Compilation Arguments box, type the following: test = 1 </li> Click OK.</li> Run the Cond_Comp macro.

Because the conditional compilation constant "test" has a value of 1, a message box displays the message "test evaluates to True".</li></ol>

NOTE: If you want to specify more than one Conditional Compilation constant in the Conditional Compilation Arguments box, use a colon as a separator. For example, you would type the following into the Conditional Compilation Arguments box: first = 1 : second = 0

<div class="references_section">