Moin! ;-)

Roman Verhovsek wrote in a message to Steffen Offermann:

 RV> I am using MakeMake now, but there was a problem when I used VB as
 RV> makefile maker. There was /Gm in it but still I had error messages
 RV> while linking. BTW, MakeMake puts /Gm but you need to set options
 RV> in Compile notebook of Workframe.

That's because the /Gm switch is used while compiling but not while
linking! I am repeating myself: Check the linker rule and insert
the missing /Gm plus your private include path(s) there.

This misbehaviour does not occur with Warp 3.

 RV> I know that, but company that I work for wants to use VB. Fly-over
 RV> text worked fine under VB, but fixpacks make it 'out-of-order'(the
 RV> newest one!!!!). 

Have to reported that to the VAC++ support site yet?

 RV> Do your accelerator keys work in menus? 
 SO> Don't yours?

 RV> If I am using OCL classicaly, then YES. But in VB when I put
 RV> MenuItems and set accelerator keys in notebook option, it doesn't.
 RV> It compiles and links O.K., but when I start program I get error
 RV> message that Resource ID doesn't exist (VB should made all visual
 RV> code by itself but it doesn't). 

Well, unfortunately I cannot help you with any VB related problems,
but if these problems only appear with Warp 4, you should report
this as a bug to the support site.

Tschuess,
  Steffen 
--- FastEcho 1.40+