In the querytable properties, there should be a property for allow
background refresh I believe. This should be unchecked. I can't
positively say this will help, but I believe it will.

--
Regards,
Tom Ogilvy

"no bosh" <please_just_post@the_newsgroup.com> wrote in message
news:41e4df61.46181996@news.localaccess.com...
> I am looking for suggestions.
> How would you suggest I pull this data into reports?
>
>
> I created created a fairly elaborate (for me) set of queries in Access
> reading FoxPro data.
> There is a table created from all this in Access which varies
> depending on the date ranges entered and depending on what periods are
> being analyzed.
>
> Anyway, I currently pull external data from this table into an Excel
> sheet but have it autorefresh on opening. I am using this
> autorefreshing sheets filtered data in lots of other worbooks.
>
> I am doing this in the course of a macro running. It opens a sheet
> which autorefreshes and then closes. I am not sure this is the best
> way to do that. I am not sure enough time is elapsing if I do this in
> code.
>
> Perhaps I should try ADO, (which I am less familiar with) to connect
> to the table directly.
>
> Ultimately all this is to track sales performance, accounting for all
> new invoicing by salesmen but then also tracking their credit returns
> and adjusting.
>
> So I am storing the data pulled from this table at certain points in
> time and then tracking the progressive adjustments and finally
> adjusting commissions based on original and final thresholds.
>
> I value all the accumulated wisdom here so I am asking if the kludge
> way, which works, could be done in a much simpler way by learning a
> different way to get at the data table.
>
> Thanks,
> ScottD
>
>
>