JExpenseCSV2PDB - A Java Jar File to create the built-in ExpenseDB.pdb for the Palm. It should be compatible with all kinds of Palm os. Up to now the file format of the ExpenseDB has not been changed. Use JExpense2CSV to generate the IFO file. The ifo file is supposed to be called like the CSV file with the suffix IFO (Example: CSVFile.CSV -->> CSVFile.CSV
JExpense2CSVFull - A Java Jar File to dump the built-in ExpenseDB.pdb of the Palm. It should be compatible with all kinds of Palm os. Up to now the file format of the ExpenseDB has not been changed. Export the Database using tools like pilot-xfer or backup Buddy. The labels of the columns are listed in the first line of the dumpfile
JExpense2CSV - A Java JAR File to export the ExpenseDB.pdb to a CSV File. Because of Java it is OS independent.
What's New in This Release:
· - length check of AppInfo removed (on MAC it is 512 bytes ?!)
· -STARTER class is now public
· - only the indexes of the label fields will be exported
JDatebook2CSVCat - A small framework written in java to list the internal DatebookDB (Creator: date, Type: data) of the Palm. It is compatible with PalmOS 2.0 or better. PalmOS 1.0 should work too, but isn't tested. Up to now, the format of the DatebookDB has not been changed
JAddressCSV2PDB - A Java Jar File to create the built-in AddressDB.pdb for the Palm. It should be compatible with all kinds of Palm os. Up to now the file format of the AddressDB has not been changed. Use Address2CSV to generate the IFO file. The ifo file is supposed to be called like the CSV file with the suffix IFO (Example: CSVFile.CSV -->> CSVFile.CSV
JAddress2CSV - A small framework written in java to list the internal AddressDB of the Palm. The output file is a CSV (comma Seperated values, ok here is a semicolon used). It is not the File used by the PalmDesktop; use Pilo-xfer or other tools to export the database from your palm to the platform you prefer. It runs with Java 1.1 or better
DB View is intended as a developer's tool to view the contents of Palm databases at a low level. I've found a few times when debugging applications that I really need to see what is being stored without relying on the application in test, DB View lets you do exactly that and a few other things too
