Platforms: Symbian OS, Pocket PC, Palm, Series 60, BlackBerry, Smartphone
Categories: Databases
Upload date: 18 Sep 11
Developer: Henk-Sjoerd Duijst
License: Freeware
Downloads: 89 File Size: 5 Kb
Palm Markup Language Tags for HanDBase - Palm Markup Language (PML) reference to create Palm eBooks.
Like it? Share with your friends!
If you got an error while installing Themes, Software or Games, please, read FAQ.
Requirements:HanDBase v.2.7x or greater
Supported operating systems:
Palm OS 3.x, Palm OS 4.x, Palm OS 5.x, Pocket PC 2002, RIM BlackBerry OS 4.2, RIM BlackBerry OS 4.3, RIM BlackBerry OS 4.5, RIM BlackBerry OS 4.6, RIM BlackBerry OS 4.7, RIM BlackBerry OS 5.0, RIM BlackBerry OS 6.0, S60 1st Edition, S60 2nd Edition, S60 3rd Edition, S60 3rd Edition FP1, S60 3rd Edition FP2, S60 5th Edition, Windows Mobile 2003, Windows Mobile 2003 Smartphone, Windows Mobile 5.0, Windows Mobile 5.0 Smartphone, Windows Mobile 6 Classic, Windows Mobile 6 Professional, Windows Mobile 6 Standard, Windows Mobile 6.1 Classic, Windows Mobile 6.1 Professional, Windows Mobile 6.1 Standard, Windows Mobile 6.5 Professional, Windows Mobile 6.5 Standard
FamilyInfo Keeps track of vital family information
Simple Support Beam for HanDBase Calculates bending moment and support reactions for uniformly distributed load & a single point load on a simply supported beam
NHI Stroke Index for HanDBase Applet calculates the NIH Stroke Index based on selections of descriptive patient findings then stores index by patient
Vacuum Leak Rate for HanDBase Vacuum Leak Rate for HanDBase - Calculates the leak rate for a vacuum chamber, in Torr. Enter the vacuum readings in Torr (power of 10 separate, minus assumed, default to 4), set the start and end times (which can be anything from 1 second to 1 hour+) and get the 1 hour leak rate
OERlog, OERaddress, OERofficer for HanDBase OERlog, OERaddress, OERofficer for HanDBase - Set of three connected tables for managing Army officer evaluations. I put in some dummy data to illustrate use. The concept was to put ratings in one file, with all officers in a separate file, placing unit addresses in a final file. Names in OERlog are DB look-up from OERofficer
