after my experience with vb4 I'd say stick with 3.x... If it isn't broke, don't fix it? The forum's VB owns aren't even all on 4 yet. They keep pushing out new releases but if you look at the issues the USERS/OWNERS are reporting, they're not fixing anything that's not a security risk. They've even gone as far as to say a function had "too much code in it anyway, so they didn't use it in 3.x and took it out of 4.x"... Yeah, but WE used it, give US the option to turn it off?
09-22-2010, 05:59 PM
Threaded Mode