The latter is particularly true when the Office version in which your “application” will run, is 64bit. So, if you are not very familiar with Windows APIs, you might have trouble adjusting the API functions into your VBA code. While this totally OK, the VB 6.0 solutions will probably rely on one or more Windows APIs. In other words, he/she might try to find solutions based on some old examples. To answer the last two questions, somebody might think to search for some old Visual Basic 6.0 code snippets. However, what if your VBA “application” needs to know how many printers are installed and available on a particular computer? What if your “application” must set the default Windows printer to “Adobe PDF”, hence, printing in a PDF file, instead of a paper? The obvious reason is that the VBA was not designed for this kind of purpose. Although VBA is a great language for building Office “applications”, when it comes to handling Windows devices, such as a printer, for example, things start to become difficult.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |