Known Issues for Satellite Forms 6.1
- If a SatForms application has custom menubars defined, users must add
at least one item to the custom menubar before downloading the
application on Palm devices. Otherwise, a Fatal Exception is displayed
when launching the menu on Palm. (24393, 24037)
- A limitation of the ActiveX control used for the App Designer table
editor allows only tables with fewer than 514,100 characters to be
displayed or saved. Table data that exceeds 514,100 characters will be
truncated and saved in a temporary file. (25115)
- For the PPC platform, there is a known issue with the Symbol Control
barcode scanner extension. When an application containing that
extension is run on a non-Symbol device, an error message is displayed
and the application will not run. See the Satellite Forms
KnowledgeBase for the solution.
- Due to a known issue with Pocket PC 2002 devices, you must close
an application on the device before you can synchronize the
application.
- Due to limitations in the Palm OS, clear buttons must be
implemented differently, depending on the Palm OS version. For
Palm OS 3.5 or earlier, the clear button must be set to the back.
For Palm OS 4.0 or greater, the clear button must be set to the
front. You can place clear buttons both behind and in front of the
overlapping control in order to work on both Palm OS 3.5 and Palm OS
4.0 and higher. (14514)
- The application definition database (ExxxxMMnn$AppName.pdb) contains
definitions of objects that runtime engines will use to render your
Satellite Forms application on the Palm. Because the Palm OS limits
the size of individual records to 64K, individual records in this
database cannot exceed 64K in size. App Designer will display an
error message when this limit is exceeded. If your application
exceeds this limitation, you will need to separate the information
into multiple fields.
Objects that are contained in this database are: form attributes,
control attributes, table & column attributes, and compiled scripts.
- The Bitmap and resource extensions will not work with Palm OS 5.0.
- The Bitmap extension will not compile with Palm OS 5.0 SDKs. The
SDKs for Palm 4.1 and lower should be used.
- SF 3.1 applications can use a lot more fields in a single
application than allowed by SF 3.5 and later. This situation may be
corrected in future Satellite Forms versions.
- You must specify all 4 icon files in your project for Palm OS
(large and small monochrome and color icons). Missing icons will
appear as "hearts" on the device.
- Applications or databases installed using HotSync Manager 4.0.0 will
always have the backup bit set. This overrides the settings in your
project properties. Palm has not issued a fix for this problem.
- Importing Tables containing Number fields that use "Replication ID"
as field sizes does not work. This problem may be corrected in
future Satellite Forms versions.
- Checkboxes on Pocket PC 2002 targets will sometimes revert to a
height of 11 from their default height of 18. To reset the
checkbox height to the default, click the form and then
double-click the checkbox.
- The Symbol Control Extension's Aim() function is not supported on
Symbol's Pocket PC 2002-based devices.
- Using "Download App & Tables to Handheld" will not rebuild the app
if you just saved your project. If you have saved since your last
change you must use "Rebuild All" to incorporate your recent changes
into the app you wish to download.
- Adding a new target to your project will not inform App Designer
that it needs to save when it closes. After adding a new target to
an App Designer project always remember to save.
- The Color Graphics extension for the Pocket PC platform uses a
different INF file than Palm OS Color Graphics extension. Palm
targets using this extension will not automatically transfer this
extension to a derivative Pocket PC target.
- Changing the data source a radio button is linked to without first
specifying an index value for the radio button will result in
errors. Avoid errors by specifying an index value for your radio
button.
- When compiling an application, if the App Designer stops responding
and the following error message appears: "AppDesigner: Out of
virtual memory", more total memory (RAM + Virtual Memory) is required
to compile the application. Any ratio of physical memory to virtual
memory can be used; for example, either 128MB RAM/570 MB Virtual
Memory or 256 MB RAM/440 MB Virtual Memory.
Keywords: bugs, known issues
KB ID: 10019
Updated: 2005-11-17
Satellite Forms KnowledgeBase Online