Basic embedded microsoft pc pocket runtime visual

Sign in to ask the community. Home Technical Support Why should I register? Mobile Computers. System Article Number. Last Modified Date. Why does my EVB application not work? Applies To. Additional informations: Windows Mobile does not support eVB at all. Now create another form of the same size and add a label at the top left.

Adjust the width to cover the left half of the screen. Set the alignment property to vbRightJustify. Copy the same label six more times and position them below each other.

Add a textbox on the top right half in the same row as Description :. Copy and paste down to the same rows as the existing labels. Add two buttons named cmdCancel and cmdSave, as shown in Figure 5. Add a grid and set the name property to grdItems. Add four command buttons and call them cmdAdd, cmdDelete, cmdView and cmdCreate. Add a label and a textbox called txtItem. The form should look something like Figure 4.

Now that you have created your forms, you can begin writing code. To add code to your form, simply double-click on the form itself.

If you don't want to type all of this code, you can download it from:. First, add a few global settings to the form's object properties, in case we do not set them in the properties window at design time, as shown in Listing 1. The next set of code is your setup code.

Setup code for a form typically goes in the Load method of the form. Listing 2 demonstrates changing default properties of the form and grdItems control. Because this is a new database application, you need to create your database from code. Listing 3 illustrates how to create a Pocket Access database.

Once you have a database, you can begin adding records. Listing 4 initializes a number of default variables, shows the secondary editing form and adds the new item to the grid. Later examples demonstrate saving to the database. The next step is to provide a mechanism for deleting data. Listing 5 prompts the user for deletion, creates a connection to the database and deletes the data specified by the user. When a SKU is entered by keyboard or scanner, I change the caption of the cmdView button and do the same when the button gets focus, as shown in Listing 6.

Write the methods to handle housekeeping chores for the form and the rest of the objects, as shown in Listing 7. When you click the grid control, copy the current item to the text box.

Note that as you select the whole row, the value returned is controlled by the Col property of the grid object. This is a zero-based column counter.

Although it defaults to 0 the first column , we may want to document the fact and allow for changes in the code. The code in Listing 8 runs when the form is closed. This is the last place to make sure everything is clean and tidy. Now that you have the main form and supporting procedures completed, you can create a second form to handle the data entry. Note that although eMbedded Visual Basic supports the use of multiple forms using the Show and Hide methods, the Unload statement and the Unload event are not supported.

This means that whatever forms get loaded stay resident until the application closes. All of them are global and take memory so you should try to keep your forms small and few. Remember that in a Pocket PC, everything is in RAM at all times, so it is easy to read information from another form even if it is not visible. When the data entry form loads, we want to set the controls to default values, reading the current SKU and setting today's date.

The remaining controls are set to blank values. You can also change this code to load data from a previously entered item. The code for this is found in Listing 9. Double-click on each of the buttons to enter their event code. For the Cancel button, you want to clean the entries for later use and hide the form, therefore showing Form1 the main form , as shown in Listing The next step is to code the Save button.

The first thing to do is to validate the data entered. The first item to verify is that a SKU was entered. The code should exit immediately if a SKU was not entered. We would typically not get to this point without a SKU, but a little defensive programming never hurts. The next step is to assign the control values to variables, open a database connection and prepare the data for saving. The idea is to collect new records for every purchase so we do not update existing records.

Before inserting the new record, you should trap for errors and display them to the screen. As you have seen, we have not given much attention to validating entered data.

I downloaded the files all 38 of them from the Microsoft web site. Then moved them to my PPC. I did not see any file that was a CAB and tapped them all.

Robert Levy [MS]. That is actually a. CAB file. Copy it to your device and open it from there to complete the installation. I have also seen the described error message. However loading the vb runtime is only a temporary fix. For some reason, even though it's already loaded, once in a while I get the error message.

If I load the vb runtime on top of the old install, then the error message goes away. I haven't done anything obvious like cold boot.