"David Thacker" <> wrote in message news:[EMAIL PROTECTED] > > I want to detect if the current device is a PalmOS 5.x Treo. I know I can > check the sysFtrNumOEMDeviceID and compare against known Treos, and that > is what I have been doing to this point, but I'd rather use a detection > scheme that can detect both current and future PalmOS Treos. I don't care > about pre-PalmOS 5.x Treos.
Hmmnn, maybe I'm not over this idea just yet... All existing PalmOS5 Treos have some common ROM databases that are not on other PalmOS5 devices, for example: HsExtensions... type 'aexo' crid 'HsEx' and HsSysResource... type 'rsrc' crid 'HsSr' Odds are that the next PalmOS Treo will have these databases with the same type and creator too. I can use DmGetNextDatabaseByTypeCreator to look for it. This looks like the way to go to *possibly* get forward compatibility with a future Treo. Even if this does not work on a future PalmOS Treo and I have to update this code, I would have been no worse off than if I had used specific device model checking like I have been doing to this point. Regards, -- David Thacker http://www.SatelliteForms.net The Premier RAD Tool for PalmOS & PocketPC -- For information on using the ACCESS Developer Forums, or to unsubscribe, please see http://www.access-company.com/developers/forums/
