Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
Problems when calling Excel from Scheduled task
Message
De
11/08/2004 23:30:32
 
 
À
Tous
Information générale
Forum:
Visual FoxPro
Catégorie:
COM/DCOM et OLE Automation
Titre:
Problems when calling Excel from Scheduled task
Divers
Thread ID:
00932571
Message ID:
00932571
Vues:
56
Hello,

I have a very strange problem which never happened to me before. I work for a company that has a Win2k SP2 network which has a domain. I have a .Bat file that calls a VFP .EXE that is a process (it doesn't show up and thus has no user interface) that calls Excel with CREATEOBJECT("Excel.Application"). When I run the .BAT from the command line window or Windows Explorer, it works fine, in other words the .BAT runs MyProcess.EXE which loads Excel in invisible mode with the CreateObject function and begins to create several worksheets using the Excel object instance. However when the .bat is run from an Scheduled task created specially for running the .bat at certain time in the night, the program stops when Excel is instantiated, it doesn't show any error. This happens with all users that are used in the "Run As" text box of the scheduled task except one user which is the domain administrator user. I don't want to use that user to run the task, we even created a user specially for running scheduled tasks but the task doesn't work with that user. Why is this? This is very strange. Are there security levels in Win2K that prevent Excel from working as a COM automation server? Why just that user (the domain user) can make Excel work fine as an automation server? I use VFP 7 SP1 and Win2k SP2. I need your help because this the las stage of a project and it's driving me mad.

Thank you in advance,

Luis
Répondre
Fil
Voir

Click here to load this message in the networking platform