|
Hi, I use the following commands for reading records and
populating them in my constructors which gets initialized in AppStart(): DmQueryRecord
and MemHandleLock They work fine on Treo 600, Treo 650, LifeDrive –
takes less than 1 second. But with Treo 700p the same constructors which read data
take more than 6 seconds. In the developer documentation there is no mention on
record fetching modifications for 700p – is there a way to improve our
application performance by eliminating the delays in DmQueryRecord and
MemHandleLock? Is the architecture modified for 700p that using DmQueryRecord
and MemHandleLock together will cause delays – DBCache/NVFS problems? Hopefully someone from Palm can answer it? (Kind Attn: Ben) Looking forward for a solution. Thanks. Regards, G. Kalyana Sundaram. -- For information on using the PalmSource Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/ -- |
- DmQueryRecord and MemHandleLock - replacements in 700p... G. Kalyana Sundaram
- Re: DmQueryRecord and MemHandleLock - replacement... Jan Slodicka
- Re: DmQueryRecord and MemHandleLock - replacement... ksundaram
- Re: DmQueryRecord and MemHandleLock - replacement... Jan Slodicka
- Re: DmQueryRecord and MemHandleLock - replacement... Ben Combee
- Re: DmQueryRecord and MemHandleLock - replacement... Dmitry Grinberg
- Re: DmQueryRecord and MemHandleLock - replacement... Ben Combee
- Re: DmQueryRecord and MemHandleLock - replacement... Dmitry Grinberg
- Re: DmQueryRecord and MemHandleLock - replacement... ksundaram
- Re: DmQueryRecord and MemHandleLock - replacement... Dmitry Grinberg
- Re: DmQueryRecord and MemHandleLock - replacement... ksundaram
