Re: PRO*C defines

Can it be that Visual Studio adds something to the command?

How can I see what is actually passed to PRO*C?

Thanks!
Olav

olavb_at_yahoo.com (Olav) wrote in message news:<eef39a63.0106070347.3951e254_at_posting.google.com>...
> In Visual Stuidio C++ I have this define as conditional a
> compilation step for a PRO*C file:
> d:\orant\bin\proc oraca=yes threads=yes DEFINE=VLVF_FULL_VERSION
>
> But it does not affect the compilation in the EXEC ORACLE IFDEF step:
>
> #ifdef VLVF_FULL_VERSION
> EXEC ORACLE IFDEF VLVF_FULL_VERSION;
> EXEC SQL ENABLE THREADS;
> LocalCtx = MyOraAgent->GetSessionContex();
> EXEC SQL CONTEXT USE :LocalCtx;
> EXEC ORACLE ENDIF;
> #endif
>
> I know that the problem is the define, because it works if I do a:
>
> EXEC ORACLE DEFINE VLVF_FULL_VERSION
> *****
>
> Is there any way to have PRO*C "see" the C-define of VLVF_FULL_VERSION?
>
> Thanks!
>
> Olav
Received on Sat Jul 21 2001 - 23:51:44 CEST