Database / Phonebook

Large DataBases (or Phone files) on FlashRAM can be slow! (95LX) (100/200LX)

The time it takes the Palmtop to write to FlashRAM is slow compared to the same process on an SRAM card. This difference is not a problem with small files. But if you use FlashRAM for large databases or Phone files that are updated frequently, this slowdown can become counterproductive. The entire database file must be updated each time you add to or edit an item. Following are some solutions to this problem:

1. 1. If the database is small enough, you can move your working copy to the C drive and keep a current back up copy on the A drive.
2. 2. If the database is too large for C drive, keep a full copy on the FlashRAM card, and a smaller edited version on the C drive. Make any additions and changes to the smaller file and periodically merge it with the full copy on the FlashRAM card.

On the HP 100/200LX

You can make a smaller copy of your database by defining Subsets to select the desired portions of your data.

Tag all the entries you want in your smaller database, then press (MENU), File, Extract..., give the file a name like, C:\SUBA.GDB, and press (ENTER).

After using the smaller database file on the C drive you will need to merge the smaller, changed file back into the big file. Open the large database on the A drive, press (MENU) File Merge..., select C:\SUBA .GDB and press (ENTER).

On the HP 95LX

This is not a problem with the PHONE application on the 95LX because the entire file is in system memory and is only saved to the FlashRAM card when you exit. However, if you are using a DOS database, i.e. dBase III, InfoManager, etc., the same problem occurs. You can use the two strategies mentioned above, but the commands for splitting and merging databases will be unique to your DOS database program.

Ed Keefe

CompuServe ID: [75300,3667]