John W. Colby
jwcolby at colbyconsulting.com
Fri Jun 3 10:08:28 CDT 2005
It is quite cool watching this populate the map with pushpins. I just setup a couple of timer classes to time how long it takes to do this. To "map" 3686 agencies took 217 seconds for about 60 milliseconds per agency. This on an AMD64 3ghz laptop with 1.2g ram and a fast hard drive. Remember though that this processed 3686 agencies but didn't resolve all of those to a single location. I didn't count the actual number resolved (sigh) and pushpins created. John W. Colby www.ColbyConsulting.com Contribute your unused CPU cycles to a good cause: http://folding.stanford.edu/ -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Michael R Mattys Sent: Friday, June 03, 2005 10:37 AM To: Access Developers discussion and problem solving Subject: Re: [AccessD] MapPoint location class ----- Original Message ----- From: "John W. Colby" <jwcolby at colbyconsulting.com> To: "'Access Developers discussion and problem solving'" <accessd at databaseadvisors.com> Sent: Friday, June 03, 2005 10:09 AM Subject: [AccessD] MapPoint location class > Paul, > > This code (see below this message) is a class clsLocation that I > developed > '**************************************** > 'The class code > '**************************************** John, Nice ! You could optionally add another recordset to populate addresses that MapPoint can't find and present it at the end of your routine. ---- Michael R. Mattys Mattys MapLib for Microsoft MapPoint http://www.mattysconsulting.com -- AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com