Hi!
 
 RV> If you closely look at makefile you will see that you have /Gm
 RV> option that should be /Gm+ by default but it isn't!!! 
 SO> That's not true. The real problem is, that MakeMake does not insert
 SO> the /Gm switch (or /Gm+, if you like) in the linker command.

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

 RV> BTW, after you have installed fixpacks, does fly-over text class
 RV> work on your machine?
 SO> It works for me (as it always did), but I am not (and will never be)
 SO> using the Visual Builder. According to the VAC++ support there was
 SO> a bug in the Visual Builder concerning fly-over help. I suppose they
 SO> fixed that, because they knew about it long before the current fixes
 SO> were available.

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

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

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

 RV> What about InfoArea? I can get only dismiss, inactive and missing 
 RV> text.
 SO> Are all these problems VB related?

Yes. BTW, fixpacks make RCX files instead of RC (RCX is C coded source) so
RC compiler and binder are not needed anymore. That is good because we had
problems with RC files and binding last too long.


Bye, Roman.


--- Blue Wave/Max v2.12 [NR]