CompuServe Messages

George, My wish list for VB would probably not fit on a single CIS message. There is a lot of room for improvement and refinement. On the top of the list though is real EXEs. Really, I don't think there's a single argument I would buy that it can't be done. Support for LIBs and OBJs is crucial, too. It would also help our third party vendors. Easier interface with certain API functions would be icing on the cake. I think that as far as the API goes, it was only a bad marketing decision. The API functions *are* part of VB's language just as much as they're part of C, TPW, Actor, etc. Unfortunately, the API functions were marketed as if they were something exotic, kind of like CALL INTERRUPT in the land of QB, PDS. There's nothing remotely similar to CALL INTERRUPT in the API. I have full sympathy for fellow users that don't have access to the forum and the great examples that are posted here daily. All I'm saying is that if VB was marketed properly the API functions would be in the Programmer's Reference right besides the old favorites like, Open, Close, Print, etc. There wouldn't be any distinction as there shouldn't be any distinction. IOW, VB has over 600 undocumented functions, I hope the next version documents them. Costas There is 1 Reply.