I have a user that moved a fox app to a new PC. The new PC is running XP SP2. I am not sure of the details on how they moved it, but i believe they moved it using a copy process as opposed to an install. The program uses Seekford's smtpwizard 2.0 control to send emails. Report options allow output to PDF files that get attached to the emails. The user has Acrobat V7 installed as their pdf reader.

All worked fine before the move from a Win98 PC to this XP PC. Now, when the user tries to email from the program, the email process just hangs. No error msgs, it just sits there on the app's email screen. An end task is required to close it. If the user runs the program in Win98 compatability mode then emailing does work. But this causes Acrobat to error out when attempting to view the generated PDFs. Conversely, if they do NOT run the program in Win98 compat mode, they can use Acrobat to view the PDFs, but as stated above, they cannot email.

Another user in the office also running WinXP SP2 and Acrobat 7 does NOT have any problems (no email, no acrobat V7 problems). There is no need for this other user to run in Win98 compat mode (there was no "copy" install). And other users do not have this problem. And they do not have to use the compatability mode setting when running the program.

They have since tried to reinstall the program on the PC but this has not fixed the email/acrobat problem. In trying to track this down, the problem PC user had informed me that he had multiple logins on the machine w/ different security rights (now with ADMIN rights) when they first moved to the new PC. And i believe another user with admin permissions did the move.

They have tried to manually register the seekford ocx, but this hasnt helped. And its not the typical error one receives due to a register problem anyway. The user has turned off firewall software, but that has not helped. Seekford commented that they are not familiar w/ the problem. I thinks its due to the initial install (copy) and/or the different user logins used when first installing or perhaps some windows registry settings for the ocx that are the cause. Any ideas?