PDA Toolbox FAQ (Frequently Asked Questions)
The following are questions that seem to come up over and over. I've tried my best to boil down the collective wisdom of the user community (Believe me, these guys figure these problems out faster than me) and include them here. Please check the list carefully before posting a problem to the Forum, or E-Mailing about it.
You can print this page off if you like. I'll make it part of the Help file (with an index) when I get time. I'd also appreciate if some of you 'long timers', would check my answers to see if I'm all wet. You can post suggested changes (or new FAQ questions) to the Forum and I'll try to include them.
- What is the layout for the Database Files?
The following link will take you to a page that describes the layout of PDA Toolbox database files (.PDB) that are backed up to your computer when you hotsynch. These files can be converted to Text files (and visa versa) via the conversion utility 'PDATCONV' that is included with PDA Toolbox. This Layout page is for those of you who would like to create a custom conversion utility (or were just curious).
Click here to see the PDB Database File Layout
- What is the layout for the Transfer Definition File (.XDF) and what does it do?
The .XDF file tells the data conversion utility what creator ID, database name, field names, and types to use when converting a text file into a Palm Database (.PDB)
The layout for this file is....
Path and Name of the Text File
Path and Name of the PDB (Database) file
Database Name , DataBase Type , Creator ID , Number of Fields
Field1Name, Field1Type, ... FieldNName, FieldNType
(Field Types: 0=Text, 1=Boolean, 2=Date, 3=Time)
This file will be created (if you answer yes) automatically after converting a PDB file to a TXT file. An Transfer Definition file is only 'required' when converting a TXT file to a PDB file. - Do I 'need' a transfer definition file? How do I get one?
The Transfer definition (XDF) file is only 'required' for conversion from text file (.TXT) to Palm (.PDB) It tells the program what creator id, database name, field names, and types to plug in when creating the database.
When converting from Palm Database (.PDB) to Text (.TXT) it's main function is to help the program 'remember' where the PDB and TXT files are. If you are going to import the text file into another program, it also forces the fields to align in columns the same way each time (Each record in a PDB database can have fields in a different order, go figure!).
You don't really 'need' a XDF (transfer definition) file to convert a .PDB to text. The program will figure out the creator, database name, types, field names, etc, on it's own. Just select the radio button to convert from .PDB to .TXT, select the .PDB file to convert (the source), and the directory where the .TXT file should be created (the target), and select to Convert.
When it finishes, the program will ask you if you would like it to create the .XDF file for you. Answer 'Yes' and it will create it for you.
You can then use this .XDF file to convert your text file (after adding data, etc.) back to .PDB format. Just select to convert from .TXT to .PDB, Select the .XDF file that you created (when converting from .PDB to .TXT), and it will fill in the names and directories of the files. Press the 'Convert' button and it will create the .PDB file with the new data. - What is the limit on the number of forms / fields in an application?
PDA Toolbox is limited to 64 forms and can have up to 64 fields per form (if you can squeeze them on). - Why do I get a ‘Creation Error’ when my application starts?
Creation errors are usually the result of duplicate Creator ID’s on multiple databases. Be sure that each application you create has a unique Creator ID, and that all tables it creates (‘Primary Database Forms’) have that Creator ID in the Form Properties. - How do I create the databases for my application?
The databases are created to match the fields setup in ‘Primary Database’ forms. Select this option from the ‘Forms Properties’ window, and set a unique ‘Database Name’. Create the fields you wish to store in this database on the form. The database will automatically store data entered into these fields. - Can my program read data from other PDA Toolbox Applications?
Yes. Be sure that the Database Name, Type, and Creator ID match the PDA Toolbox database you want to access. - Can my program read data from Palm’s ‘built-in’ functions?
No. PDA Toolbox cannot read from the Palm’s built-in functions (Address Book, Date Book, To-Do list, etc.) with this current release. This may be incorporated into a future release. - My app won’t run on a Palm with OS 3.5! What’s wrong?
You have an old version! Download and re-install the latest version (This was fixed 07/31/2000). Currently PDA Toolbox does have a problem with the OS3.5 DEBUG rom on the emulator (use the RELEASE rom instead). - How do I put graphics in my applications?
Graphics can be ‘cut’ from any graphics program using the Window’s clipboard functions, and pasted onto a form as a background, or onto a button (to make it a graphical button). The graphic should be in black & white, and small enough to fit on the Palm’s screen (160 by 160 pixels). See the tutorial for an example). - How do I get data from my Palm to my PC (or visa versa)?
All versions after 1.0 have a conversion utility that will convert PDA Toolbox databases (.PDB) to text files (.TXT) and visa versa. - Can I distribute the applications I create with PDA Toolbox?
Absolutely! Applications you create with PDA Toolbox are yours to distribute as you see fit. Several applications created with PDA Toolbox are being distributed as shareware on PalmGear™ right now.
However…. You cannot legally dis-assemble, redistribute, or change any of the files distributed with PDA Toolbox. (Registered users can distribute the conversion utility) - Can I change or remove the ‘All’ selection on Pop-Up lists?
Users have reported that this is possible but that cannot be confirmed. - How does PDA Toolbox handle ‘Time’ fields?
Selecting a time field for editing will bring up a selector screen, that will allow you to set the hour, minute, and AM/PM using arrow buttons. This is only supported on Palm OS 3.1 and higher.
On OS 3.0 or lower, time fields are treated as simple text data. - Can I create calculated fields (sum, avg, etc.)?
Calculated fields are only supported in the retail version of PDA Toolbox. - Can I capture signatures or drawings?
Yes, using 'Digital Ink, a special field type that allow capture of signature or drawing onscreen (Registered users only). - What will registering give me (other than a warm feeling of contributing to the PDA Toolbox development effort)?
Registered users can add the following functions to their apps:
Record Beaming.
Calculated fields (Sum, Avg, etc.).
Ability to sort Databases by Key fields.
Digital Ink (Signature Capture and drawing) - How do I create my own ‘About this Application’ screen?
In the current version you can enter text you want to appear on the Application Information window. The 'About' form will be created automatically. - Why doesn’t data in certain fields get saved?
Be sure that any fields that save data (fields, checkboxes, dates, etc.) have a unique Field Name. If you leave this blank the data will disappear when you exit the form (This is a pretty common mistake). Also make sure you have the ‘Primary Database Form’ box checked in the form’s properties. Unfortunately field type 'integer' is selectable but not fully implemented yet. (Use Text) - I get a ‘Resource for System not found’ error when hitting a button.
This is commonly caused by trying to access a form that does not exist. Make sure you didn’t delete a form that a button references. If so, change the ‘Action’ properties of the button to point to the correct form. - I get a ‘Resource for System not found’ error when tapping a table item.
This can happen in a table if you don’t have the Table’s ‘Edit form with:’ parameter set to the ‘Primary Database’ form that allows editing of the records displayed in the table. This allows tapping an entry in the table to bring up the edit form with that record for display or editing. - Drop Down boxes give me weird errors in the emulator but not on my Palm.
On the emulator go to the ‘Settings’, ‘Debug Options’ and uncheck the ‘Free Chunk Access’ option. This seems to be one the emulator catches but doesn’t affect operation on the Palm. This is on the ‘to fix’ list. - Can I have more than 5 columns displayed in a table?
Five columns per table is the current limit. This may be raised in the future. - How do I get a table to only show items that match certain criteria?
Short Version:
‘Secondary Database Field’ is the column in the table to check.
‘Primary Database Field’ is a Pop-Up on the form to compare against.
Long Version:
Create a ‘Pop-Up’ field on the form (outside the table) that lists the criteria you want to match. The possible values for this field can be from a ‘Static List’, or created dynamically by pulling values of a field from another database (Pop-Ups are explained in the tutorial). Make sure this field has a unique name.
Setup your table as normal, picking fields out of a database to put in each column.
In the ‘Record Set Selection’ box of the table’s properties window select the ‘Show Related Records’ radio button.
In the ‘Source Database Field’ enter the name of the Pop-Up field that is on the form (outside the table).
In the ‘Secondary Database Field’ enter the name of the field (in the table) that should be ‘tested’ against the value of the Pop-Up (This has to be the same as the ‘Field ID’ of one of your columns).
When the table is displayed it will test the value of the ‘Secondary Database Field’ (from the record pulled up) against the value of the ‘Source Database Field’ (The Pop-Up) and display if there is a match, or if ‘All’ is selected on the Pop-Up. This is probably the feature that most people find the hardest to get working (It had me stumped!).