A bit of followup: I just ran the Process Explorer utility from
sysinternals, and found out an amazing thing. It is NOT running the file I
think it should! Our systems have Altiris on them, and files are being
copied to C:\fslrdr. My script apparently is tripping up that, and my
updates are not being moved to that location, and the old version persists.
So, this appears to be an Altiris issue.
Kevin
"Kevin Nechodom" wrote:
> I am running Windows XP SP2 and Office 2003 SP2. In my startup script, I
> have a batch file that copies an Access MDB file from a network share to my
> local file system. Because it uses Oracle, I turn the Read-Only flag off,
> copy the file, then turn the flag back on.
>
> It appears to be holding the previous copy of the file, even though it shows
> the fileinfo of the new file. If I manually delete the file, when I refresh,
> it shows the older file with its older fileinfo. If I delete again, it seems
> to to work, and the copy is successful.
>
> I thought it might have something to do with the Indexing Service, but I
> turned it off, and I continue to have the same problem. I wondered about
> Volume Shadow Copy, but the service is set to Manual.
>
> Any idea what is causing this? This is keeping my database updates from
> being seen by my clients.
>
> Thanks,
>
> Kevin
|
Similar Threads
