DOCUMENT:Q192618 18-SEP-1998 [vbwin] TITLE :INFO: Frequently Asked Questions (FAQ) About VBCE 1.0 PRODUCT :Microsoft Visual Basic for Windows PROD/VER:WINDOWS:1.0 OPER/SYS:WINDOWS KEYWORDS:kbfaq ====================================================================== --------------------------------------------------------------------- The information in this article applies to: - Windows CE Toolkit for Visual Basic 5.0, version 1.0 --------------------------------------------------------------------- SUMMARY ======= This article covers some of the most frequently asked questions (FAQs) about the Windows CE Toolkit for Visual Basic 5.0 (VBCE), version 1.0. MORE INFORMATION ================ The following questions are answered in this FAQ: 1. Can I develop VBCE applications for use on palm-sized PCs? 2. Does VBCE provide database programmability? 3. Are ActiveX controls supported in VBCE? Where can I get them? 4. Can I use Windows 95 or Windows 98 to develop VBCE applications? 5. Will VBCE work with Visual Basic 6.0? 6. Can existing Visual Basic applications be ported to VBCE? 7. Are the same Visual Basic controls supported in VBCE? 8. How do I debug VBCE applications? 9. Can I call APIs in VBCE applications? 10. Do I need a handheld device to run VBCE? 11. Are there any third-party controls available for VBCE? 12. How much does VBCE cost? 13. What other products do I need to purchase to use VBCE? 14. Where can I obtain VBCE? Questions and Answers --------------------- 1. Q: Can I develop VBCE applications for use on palm-sized PCs? A: Currently, applications targeting palm-sized PCs cannot be developed using VBCE. The implementation of the Windows CE operating system on the palm-sized PC devices does not currently include sufficient COM support for VBCE applications. For additional information, please see the following article in the Microsoft Knowledge Base: ARTICLE-ID: Q191478 TITLE : INFO: Palm-Size PC Does Not Support VBCE Applications 2. Q. Does VBCE provide database programmability? A. Yes. Microsoft has released the ActiveX Data Objects 1.0 SDK for Windows CE (ADOCE 1.0), which provides advanced database programmability for VBCE developers. ADOCE 1.0 can be downloaded from the following location: http://www.microsoft.com/windows/downloads/contents/other/ ceactivexsdk/default.asp For additional information, please see the following article in the Microsoft Knowledge Base: ARTICLE-ID: Q192531 TITLE : INFO: Overview of ActiveX Data Objects SDK for Windows CE 3. Q: Are ActiveX controls supported in VBCE? Where can I get them? A: Yes. ActiveX is supported in Windows CE, and you can use ActiveX controls in your VBCE applications. Microsoft has released to the Web the Windows CE ActiveX Control Pack 1.0, which includes the Grid, TabStrip, TreeView, ListView, ImageList, and CommonDialog controls. These controls can be downloaded from the following Web address: http://www.microsoft.com/windowsce/hpc/developer/downloads/ You cannot, however, develop ActiveX controls using VBCE. Instead, you must use the Windows CE Toolkit for Visual C++ (VCCE) for ActiveX control development. 4. Q. Can I use Windows 95 or Windows 98 to develop VBCE applications? A: No. Due to the requirement for Unicode support and emulation capabilities, VBCE currently requires Windows NT version 4.0 (with Service Pack 3). For additional information, please see the following articles in the Microsoft Knowledge Base: ARTICLE-ID: Q184851 TITLE : INFO: VBCE Does Not Run on Windows 95 or Windows 98 ARTICLE-ID: Q181943 TITLE : INFO: System Requirements for Windows CE Toolkit for VB 5.0 5. Q: Will VBCE work with Visual Basic 6.0? A: No. VBCE was developed to work specifically with Visual Basic 5.0. Microsoft is actively investigating how to best bring VBCE to Visual Basic 6.0. Information will be posted at the following location when it becomes available: http://www.microsoft.com/windowsce/hpc/developer/products/ 6. Q: Can existing Visual Basic applications be ported to VBCE? A: You cannot directly port an existing Visual Basic application into VBCE due to some limitations and unsupported features in VBCE. The amount of work required to "port" an existing Visual Basic desktop application to VBCE will depend on many factors, including the complexity of the application and whether it uses features not supported in VBCE. It may be significantly easier to create a VBCE application from scratch than to port an existing Visual Basic application. For additional information, please see the following articles in the Microsoft Knowledge Base: ARTICLE-ID: Q186266 TITLE : INFO: What Is Handled Differently in Windows CE and VBCE ARTICLE-ID: Q184650 TITLE : INFO: What Does Visual Basic 5.0 Have That VBCE Doesn't Have? ARTICLE-ID: Q192459 TITLE : INFO: Unsupported Controls, Properties, Methods and Events 7. Q: Are the same Visual Basic controls supported in VBCE? A: Most Visual Basic intrinsic controls (such as CheckBoxes, TextBoxes, CommandButtons) are supported in VBCE. There are some differences in control appearance and behavior corresponding to differences in the Windows CE user interface model, however, and there are also differences in the Visual Basic built-in functions corresponding to differences in operating system features. For the most part, you will find that creating VBCE applications is very similar to creating Visual Basic applications on Windows 95/98 or Windows NT. 8. Q: How do I debug VBCE applications? A: There are two methods of debugging available for VBCE users. The first is to use the H/PC emulator (provided with VBCE) to debug your application right on your Windows NT development workstation. This method is fast and convenient, and is ideal for applications that are being developed for hand-held PCs. The second is to use the remote debugging tools provided with the Toolkit. These tools let you execute your VBCE application remotely on your Windows CE device, while at the same time monitoring and controlling its execution from your Windows NT development workstation. 9. Q: Can I call APIs in VBCE applications? A: The current version of VBCE does not allow you to call API functions directly. Instead, you may use the Windows CE Toolkit for Visual C++ (VCCE) to create an ActiveX control wrapping the API call and host the control in VBCE. 10. Q: Do I need a handheld device to run VBCE? A: You do not need a handheld device to begin developing VBCE applications. You can create and debug Windows CE-based applications from your desktop. Built-in emulation technology provides the look and function of a device, right on your PC. 11. Q: Are there any third-party controls available for VBCE? A: A growing number of third-party companies are looking into developing controls for use in VBCE. See Microsoft's Windows CE Web site for the most current information: http://www.microsoft.com/windowsce 12. Q: How much does VBCE cost? A: The retail price of VBCE is $199, and it is available now. 13. Q: What other products do I need to purchase to use VBCE? A: You will need to obtain a copy of Visual Basic version 5.0, and you will need to be running the software on Microsoft Windows NT, version 4.0 with Service Pack 3 or later. 14. Q: Where can I obtain VBCE? A: VBCE is available from retail channels, including mail order software retailers. Additional query words: kbDSupport kbWinCE100 kbdss kbVBp500 kbWinCE kbVBp vbce kbToolKit ====================================================================== Keywords : kbfaq Version : WINDOWS:1.0 Platform : WINDOWS Issue type : kbinfo ============================================================================= THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY. Copyright Microsoft Corporation 1998.