Home |
Search |
Today's Posts |
#1
Posted to microsoft.public.excel.programming
|
|||
|
|||
Kill Delayed?
In my application, by design I move files from one folder to another.
I open the file, makes some changes to cells and save the file to another folder, finally use Kill to remove it from the source folder. The new file is then closed. Most of the time this works, on the corporate network I occasionally get a failure, where the new file is created but the old file is not killed. Users have the right access rights to the server. Q1. Why might this happen? Q2. Can I apply a delay or some other action to prevent, warn or otherwise fix this. Sample of the code sequence in VBA code - as follows ' store old file name sOldFile = ThisWorkbook.FullName ' file saved in different place and name Application.DisplayAlerts = False ThisWorkbook.SaveAs sPath & sFile Application.DisplayAlerts=True ' remove old file Kill sOldFile ' close the new file ThisWorkbook.Close savechanges:=False -- Regards, Nigel |
Thread Tools | Search this Thread |
Display Modes | |
|
|
Similar Threads | ||||
Thread | Forum | |||
How many delayed per week | Excel Discussion (Misc queries) | |||
Delayed Update? | Charts and Charting in Excel | |||
Delayed reactions | Excel Discussion (Misc queries) | |||
Delayed reactions | Excel Discussion (Misc queries) | |||
Msgbox delayed using AFTERUPDATE | Excel Programming |