CompuServe Messages

Costas, You're absolutely right in everything you say. I'm sure that standard API calls will survive the version change. MS wouldn't dare change the basics. As I have said before, I love this environment. And you're right, stuff like making some calls internal would just be go-betweens, but isn't that what's happening throughout VB. My concern comes when some particularly useful stuff *requires* API calls. In QB, it was all there. I used external stuff only when it resulted in a dramatic speed increase, sometimes ignoring a built-in function. It's just that not everyone who buys VB is going to be as dedicated as you and I and the rest of the people on this forum to exploring the external possibilities. I look at the guy who just wants a little app that prints sheets of his clip art files. With internal commands available, VB could do that app in about 10 minutes. Without them….it could take forever. I actually tried a Point/PSet version of a graphics printing utility. It worked, but printing a 300X300 mono BMP file took over an hour! A simple method added to the Printer and Picture Box objects could mediate this problem. I want Scalex, Scaley, and PrintImage available. It'd be a lot simpler for MS to add that to VB than it will be for all those users to figure it out. George There are 2 Replies.