File Errors

After checking your code for syntax errors, the toolkit consolidates all code and property values for your application into a .vb file for transport to the emulation environment or to a Windows CE-based device. The following list shows the error messages you may receive when compiling an application.

Your Project Specifies <control name>.<property>

The toolkit supports a subset of properties that are enabled for intrinsic controls in Visual Basic 6.0. Unsupported properties in Windows CE retain their default values, which the toolkit verifies while creating the .vb file. The toolkit displays each unsupported property in a separate dialog box. You can cancel the listing of unsupported properties by choosing the Cancel button.

Your Project Specifies a Control Array <control name>

The toolkit does not support control arrays. Each member of the control array has the same name, but a different non-negative value for the Index property. A control that is not a member of a control array has a name that is unique to the form and an Index value of – 1. If you receive this error message, verify that the indicated control has an Index value of – 1.

No Write Permission for File

The toolkit found a prior version of the local .vb file for your project, and the prior version either has its read-only property set or has not enabled you with write permissions. To correct this, you can change the permissions for the file, or you can change the local path to a different location where the toolkit can create a new .vb file.

File is Currently Being Used

The toolkit detected a prior version of the local .vb file for your project, and another application currently is accessing the file. Close the file or exit the other application, as appropriate.

VB File Larger than the Available Space

The space on the local disk drive is inadequate for the .vb file. Delete unnecessary files on the local disk or select an alternate location with sufficient space for the .vb file.