This has been confirmed as a timing problem and has been fixed by adding a 0.5 second delay in the appropriate place. Hopefully I can recode it so it only waits as long as it needs to (lesser-powered machines have the problem) Steve