several approaches come to mind from both inside and outside VSTO. Outside,
you can use a thread or a timer to force an update. From inside you can take
advantage of the querytable object. The object has an automatic refresh
property and takes a filepath or url as the datasource. Finally, you can
connect your datasource to a dataobject and have the dataobject be
responsible for replenishing itself at regular intervals. Lots of choices
here...

Signature
________________________
Warm regards,
Alvin Bruney [MVP ASP.NET]
[Shameless Author plug]
The O.W.C. Black Book with .NET
www.lulu.com/owc, Amazon
Professional VSTO.NET - Wrox/Wiley 2006
-------------------------------------------------------
> We have an Excel 2003 workbook, automated with VSTO, on a shared
> network drive. The workbook contains pivot tables that refresh from
[quoted text clipped - 8 lines]
> workbook about twice a day at specified times. How should we go about
> accomplishing this?
weisberg39@yahoo.com - 19 Apr 2006 19:04 GMT
Thanks for the suggestions!
It looks like all of them require keeping an instance of Excel running
at all times, presumably on a user workstation (we wouldn't want to
have Excel running on the file server)!
Are there any that don't? I'm looking for a batch file or executable
that I can run as a scheduled task.
Alvin Bruney - 24 Apr 2006 15:34 GMT
It does not. For instance, with the datasource, you can set the option to
refresh data only when the workbook is opened. At that point, data is
refreshed on demand.

Signature
________________________
Warm regards,
Alvin Bruney [MVP ASP.NET]
[Shameless Author plug]
The O.W.C. Black Book with .NET
www.lulu.com/owc, Amazon
Professional VSTO.NET - Wrox/Wiley 2006
-------------------------------------------------------
> Thanks for the suggestions!
>
[quoted text clipped - 4 lines]
> Are there any that don't? I'm looking for a batch file or executable
> that I can run as a scheduled task.
weisberg39@yahoo.com - 24 Apr 2006 19:43 GMT
Hi Alvin,
Thanks for the reply.
Having the data automatically update when the user opens a copy of the
workbook doesn't solve the problem. We need have the data already
refreshed before the user opwens a copy of the workbook.
The reason is that we have about 30 users, and it takes about 10
minutes to refresh all the data. The users can't wait ten minutes for
the refresh, we can't afford to devote 10 hours a day of prouction
server time to these updates, and we don't want to give the users write
access to the shared workbook.
--Howard
--