Johan, On Mon, 02 Jul 2007, Johan Vromans wrote: > 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? I think it's a good idea (but I'm not sure any cut off date is required?). It wouldn't *have* to be read-only I think. It might get more complicated when jpilot gets new-style Calendar database support, as the history database is only ever in the old-style DatebookDB format. A quick-option would be to add a toggle, same as the jpilot Memo support has, to switch between the two databases. The sync process can easily sync both DatebookDB and the history database. This would be read/write for history. Nick -- Nick Piper, Developer, LogicaCMG http://www.nickpiper.co.uk/ GPG Encrypted mail welcome! 1024D/3ED8B27F Choose life. Be Vegan :-) Please reduce needless cruelty & suffering !
More information about the jpilot mailing list