The information in this article applies to:
SUMMARYThis article covers some of the most frequently asked questions (FAQs) about the Windows CE Toolkit for Visual Basic 6.0 (VBCE 6.0). MORE INFORMATION
The following questions are answered in this FAQ:
Questions and Answers
A: There are a number of places to look for documentation on VBCE. In addition to the Windows CE Toolkit online help available from the Visual Basic Help menu, you can also check the following resources: MSDN Library Online
Microsoft Windows CE Toolkits Home Page A: In order to use VBCE 6.0, you'll need the following: Note that Windows NT is required for emulation. A: VBCE is able to provide database programmability via the ActiveX Data Objects control for the Microsoft Windows CE operating system (ADOCE), which provides a subset of ADO for Windows CE. The setup program for ADOCE is included on the VBCE 6.0 CD in the ADOCE directory. Here are some important notes regarding the two current versions of ADOCE: For additional information about ADOCE, click the article numbers below to view the articles in the Microsoft Knowledge Base: Q192531 INFO: Overview of ADO for Windows CE SDK (ADOCE) Q196034 HOWTO: Use ADOFILTR.DLL to Transfer Database Tables A: There are a number of places to look for documentation on ADOCE. In addition to the Windows CE Toolkit online help available from the Visual Basic Help menu, you can also check the following resources:
ADOCE does work in the emulation environment. You'll need to ensure that you install the emulation components as a part of the ADOCE SDK installation from the VBCE 6.0 CD-ROM. You'll also need to ensure that you have copied your database tables to the emulation environment by using the EmpFile utility. For an illustration of how to do this, please see the EmulDB sample that ships with the ADOCE SDK. This sample is located, by default, in the following location:
For additional information about the EmpFile utility, click the article number below to view the article in the Microsoft Knowledge Base:
Q212884 INFO: VBCE: How to Use the EmpFile Utility A: Palm-size PCs can be targeted with VBCE 6.0. The target Palm-size PCs must be running at least the Windows CE operating system version 2.11. Please note that the implementation of the Windows CE operating system on the Palm-size PC devices running the Windows CE operating system version 2.0 does not include sufficient COM support for VBCE applications. In order to target Palm-size PCs, the associated Windows CE Palm-size PC Platform SDK is required: Palm-size PC 1.2 SDK Download (English)For additional information about the Palm-size PC's support for VBCE applications, click the article number below to view the article in the Microsoft Knowledge Base: Q191478 INFO: Palm-size PC Does Not Support VBCE Applications A: VBCE 6.0 can currently target the following Windows CE platforms using the Platform SDKs provided by Microsoft: Hardware Devices, Software Development Kits (SDKs)Also, please note that VBCE 5.0 applications can only be created for H/PC devices. A: Yes. ActiveX is supported in Windows CE and you can use ActiveX controls in your VBCE applications. Currently, however, you cannot develop ActiveX controls using VBCE. Instead, you must use the Windows CE Toolkit for Visual C++ (VCCE) for ActiveX control development. Additionally, there are a growing number of third-party companies that are either developing or looking into developing ActiveX controls for use in VBCE. See one of Microsoft's Windows CE Web sites for the most current information: Microsoft Windows CE Home Page Microsoft Windows CE Toolkits 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, Windows 98, or Windows NT. Yes. The Windows CE Toolkit for Visual Basic 6.0 can be installed on either Windows 95 or Windows 98 to develop Windows CE applications. The emulation environment, however, is available only under Windows NT. Additionally, it is important to note that Windows CE Toolkit for Visual Basic 5.0 cannot be installed on a Windows 95 or Windows 98 machine. 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, click the article number below to view the article in the Microsoft Knowledge Base: Q186266 INFO: What Is Handled Differently in Windows CE and VBCE Q184650 INFO: What Does Visual Basic Have That VBCE Doesn't Have? Q189478 INFO: What Does VBCE Have That Visual Basic 5 Doesn't Have? Q192459 INFO: Unsupported Controls, Properties, Methods and Events A: There are two methods of debugging available for VBCE users. The first is to use the emulation environment to debug your application right on your Windows NT development workstation. 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. For additional information about Debugging VBCE applications and differences between emulation and the remote device, click the article numbers below to view the articles in the Microsoft Knowledge Base: Q192549 INFO: VBCE: Overview of Debugging VBCE Applications Q192998 INFO: VBCE: Differences Between Emulation and the Remote Device A: Distribution of VBCE applications can be accomplished using the Application Install Wizard supplied with VBCE. For additional information about distributing VBCE applications, click the article number below to view the article in the Microsoft Knowledge Base: Q194837 HOWTO: Distribute a Visual Basic Windows CE Application A: Using the new Pocket Outlook Object Model (POOM) you can now read, create, and modify items used by the Pocket Outlook's Calendar, Tasks, and Contacts, as well as accessing and creating cities used by the World Clock. In order to access Pocket Outlook objects, the Pocket Outlook Object Model (POOM) SDK is required: Pocket Outlook Object Model (POOM) SDK A: The current version of VBCE allows you to call many Windows CE API functions directly. You can use the existing Visual Basic API Text Viewer to view the API information from the winceapi.txt file. In certain circumstances, because VBCE does not support structure data type, you may still need to use the Windows CE Toolkit for Visual C++ (VCCE) to create an ActiveX control to wrap the appropriate API calls and then host the control in VBCE. Please note that API calls could not be made from VBCE 5.0 applications. A: You do not need a 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. It should be noted that in order to install ADOCE, Windows CE Services is required. Windows CE Services only ships with the devices. So although ADOCE will work in the emulation environment, currently it cannot be installed without the presence of Windows CE Services. A: The following table lists what is supported and what is not:
REFERENCES
Windows CE Toolkit for Visual Basic 6.0 Online Help Additional query words: vbce vbce5 vbce6 wince
Keywords : kbToolkit kbVBp600 kbWinCE kbGrpVB |
Last Reviewed: January 6, 2000 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |