Discussion Locked

Excel Caching Problem

0 helpful
5 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
I have a client that has what I would call a chaching problem. After making changes to a spread sheet weather it be to add or delete informations from a column or row. She saves the changes via the icon on the toolbar. Next day she comes in bootsher pc, logs into the network and open excel, load the file up and the chages made the day before does not appear to have been saved. Go to another pc on the network open the file through Excel and the changes that pc 1 made are reflected on pc 2.Here the skinny. 1. File is located on a public shared directory to everyone on the server. 2. Both PC1 & PC2 are running Windows 98 and Office 2000 with all the critical patches and updates from Microsoft with the exception of the Office 2000 SR1.3 The Server is a Windows2000 with no Service Release Packs installed. 4. Running sctricly TCP/IP with static IP on all workstatons. Has anyone ever come across this? It seems to be isolated to that pc, have tried opening file on 6 different pc'sand the file reflects changes. Just not on PC 1.

5 replies

by syscokid

The only thing I can think of is that it's *not* the same file. Is she opening it using File-Open, or clicking on the file's name on the Most Recently Used menu under File? If the latter, then it's not pointing to the right file.

by charles

This was the first thing that came to mind for me as well. The file is on a shared directory on the Server. I have verified they are both opening the file within excel from the same location, as a matter of fact this is the only version of file on the entire network. I forgot to give a bit of information, after a couple of times of opening the file at PC1 the changes will then show.

by james_randy

Hey buddy, we all have cash problems. The problem is we always have too little. There 'ya go. Get more.

by charles

I know where you are coming from, but this still hasn't gotten me any futher.

But after playing a little longer with it, I finally discovered the problem was that the computer had a virus. This virus was only detectable at dos level. Updated virus scan file and ran at dos level, this solved the problem.

This discussion is closed to new replies.