That's actually a pretty good idea... but it only speeds access to existing dbs, and doesn't easily let me know if db's have been added or deleted :( But, just to let eveyone know how it turned out, I just build a run-time cache (with dbID in it for each db) and refresh it each launch cycle. Then all parts of the app use the cache. If any parts of the app invalidate the cache, I reload. Works quite well... now launch 'em 2 is as fast as the built-in apps program! Finally... BTW - keith, thanks again for POSER profiler! Alan Pinstein Synergy Solutions, Inc. http://www.synsolutions.com 1-800-210-5293 >> What about storing a quick checksum on the some of the data >> cardNo and dbID point to and validating that before launching an >> app from your cached dbID? If it doesn't validate, you could >> always use DmFindDatabase as a backup... (?)
