Hi Randy!

Quoting Randy Cornish <rlcornish@c...>:

> I am soon going to be moving a large enterprise application to VB6 from
> I am looking
> for the unexpected when I go to compile old VB5 code with the VB6 
> compiler.  

Well, you can NEVER KNOW... most times, just expect everything and it will 
happen! Hehehehehehe.

> For example, Microsoft REQUIRES IE 4.01 for VB6, but 
> RECOMMENDS IE 5.0 or higher.  If I use only 4.01, any surprises?  

From this point of view, I'd recomment the IE 6. I've had problems with some 
flavours of IE4, and some with IE5. If it's not a company's issue (something 
related to update policies or something like that, go ahead and recommend and 
install IE 6. It works just fine. 

> Microsoft REQUIRES MDAC 3.5, but RECOMMENDS 3.6.  If I only have 3.5 (or
> a kind of "in between" mix), any surprises?

Once again, be sure to have uniformity of deployment, but, this specific issue 
should not raise any problem. I know MS has released the latest MDACType, but I 
don't know about the very latest differences between implementations... 
basically, I guess it's strictly related to the environment you are going to 
interface and develop your solutions (for example, you might be interested in 
CUBE/SHAPING relational recordsets using SQL, and there's a difference between 
different releases of MDACType...)... as far as I know, nothing stands out 
really clearly... sorry I can't help you that much about this!
 
> [insert your anecdote here - this might be entertaining AND
> educational]

Everything has an end... but hot dogs have two!
(liberally translated from Italian, hope it sounds nice).
 
> Thanks,
> R
>