RE: Linked Excel File

[Klatuu]

I believe it is a timing issue.
It can take a little time for the copy from the pc to the network to take
place. I suspect the when access tries to open the table, the copy process
has not yet completed.
--
Dave Hargis, Microsoft Access MVP

"Weste" wrote:

> I have an MS Access 2003 app that has a linked Excel file. There is a
> process that copies the Excel file from the user’s pc to the network, then
> refreshes the link. If this process is run, then a user makes a change in
> the file and runs the copy/refresh process again, the updated file doesn’t
> get copied to the network if this is done within about a minute of the first
> copy/refresh. It seems like the app is holding a copy of the old Excel file
> temporarily in memory. I have tried deleting/creating a new link vs. refresh
> and this doesn’t fix the problem. I have also killed the file on the network
> before copying the updated file, and the old file still gets copied. If I
> wait approx 1 minute, the updated Excel file gets copied. Is there a way to
> flush the old copy out of memory? Thanks.

[Weste]

It seems like a memory issue. Access is copying over the old file if the
copy function is run witin a minute of each other. I manually deleted the
file, then looked at the file on the network and it is the old file. I don't
think Access flushed the original version from memory. If I wait about a
minute before I run the copy process again, the updated file gets copied. I
tried running DBEngine.Idle(dbRefreshCache) but this didn't help.