对奇怪的构造感到好奇：“#If OutlookEnabled” [英] Curious about odd construction: "#If OutlookEnabled"

问题描述

我有一些我不理解的继承代码。它涉及使用OLE和Outlook从Access发送电子邮件。我已经把它剥离到了相关位。具体来说，（我知道）我不明白的结构是：

I have some inherited code that I don''t understand properly. It involves sending email from Access using OLE and Outlook. I''ve stripped it down to the relevant bits here. Specifically, the construction that (I know that) I don''t understand is this:

展开 | 选择 | Wrap | 行号

推荐答案

你好，prn。


" OutlookEnabled"可能只是用＃Const声明的条件编译器常量条件编译器指令。检查Access帮助。


问候，

鱼

Hello, prn.

"OutlookEnabled" could be nothing but conditional compiler constant declared with "#Const" conditional compiler directive. Check Access help for this.

Regards,
Fish

谢谢，FishVal。我不知道该怎么做，但我很感激。


我看到至少有两个测试，我认为这是一个条件编译常量。


首先，我搜索了整个项目。字符串OutlookEnabled的每次出现都是在#If OutlookEnabled中构造，没有一个#Const OutlookEnabled实例。或者甚至是#Const任何地方，在该模块或任何其他模块中。


其次，如果我构造一个条件常量的明确案例：

Thanks, FishVal. I''m not sure what to make of this, but I appreciate it.

There are at least two tests that I see for the hypothesis that it is a conditional compilation constant.

First, I have searched the entire project. Each and every occurrence of the string "OutlookEnabled" is in the "#If OutlookEnabled" construction, There is not a single instance of "#Const OutlookEnabled" or even of "#Const" anywhere, in that module or any of the others.

Second, if I construct a clear case of a conditional constant:

展开 | 选择 | Wrap | 行号

@prn


:)寻求，寻求。它一定是。

...对不起这个老笑话。

@prn
:) Seek, seek. It must be.
... Sorry for the old joke.

其次，如果我构建一个明确的案例条件常量：

Second, if I construct a clear case of a conditional constant:

展开 | 选择 | Wrap | 行号

这篇关于对奇怪的构造感到好奇：“#If OutlookEnabled”的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！