If you use DateBk5 you have the ability to split off a part of your DataBk data in a separate database, the so called history. This makes it possible to maintain a large database with older appointments (that still can be inspected and searched) without affecting the performance of the daily operations. For a clarification: I'm running DateBk5 on a PalmV which is a very old PDA. JPilot has much more power and it has no problems with a big database. Ideally, it would be nice if JPilot could deal with the two databases simultaneously. So everything before a specific cut-off date would be in the history (and read-only!) while all newer data would be in the normal DateBook. On screen, it would look like one single database. Has anyone ever considered something like this? -- Johan
More information about the jpilot mailing list