> > One other way, although it is the lamest suggestion I've ever seen, is to > > include one of the Palm dlls (I forget which one it is) and ask it what the > > Palm directory is.. then do the same as above... > > Actually, this is the _preferred_ way to get the path to the user's Palm > directory - include the ConduitMgr.dll with your installation and ask it. > This is the safest method - it works no matter what underlying architecture > is used to come up with the path.
<backpedaling> Did I say "lamest"? Oh... I guess I did... ok.. there, that's the DLL name you're supposed to include. (I didn't realize this was the preferred Palm way.. I first saw it in one of the Palm programming books). </backpedaling> -- For information on using the ACCESS Developer Forums, or to unsubscribe, please see http://www.access-company.com/developers/forums/
