C
Chuckles123
Excel 2003 on a LAN:
I have VBA code stored in two .xlA files (not installed as an 'AddIn
in Excel): one macro fires at 9 am and the other fires at 5 pm. The
pm macro imports data from an accounting server and updates two .xl
data files and saves them using constant filenames (the .xlS file
contain zero VBA code). The 9 am macro, using the preceding day's dat
files plus data imported from another server, crunches all the data an
sends out e-mails based on the values in specified cells. All of thi
usually works.
However, there has occasionally been a problem with a macro crashing (
pop-up error message indicating that a 'read-only' file cannot b
accessed <-- this really means that it cannot be saved). Of course
this only occurs on the .xlS files since the .xlA files are never save
when the macros are executed. However, when revising code in the .xl
files, I occasionally get the same message; this is true even thoug
the .xlA macro will run just fine when the .xlA file is opened on a
unintended 'read-only' basis (regardless of the setting o
'Application.DisplayAlerts=?').
I am currently in a testing mode; my ultimate goal is to locate thes
macros and data files on an Autosys server -- therefore, zero pop-ups.
I am not sure what causes the above sickness, but here are the symptons
the .xlS file or the .xlA file is "tied up" on my network login, eve
though when I go into 'Windows Task Manager - Processes', EXCEL.EXE i
not listed; also, no change in "tied up" status when powering th
machine down and re-powering and re-logging-in to our LAN; the file ca
be copied but it cannot be deleted. The only solution has been to cal
our LAN Administrator and request that the "tie up" be severed; he doe
so by making a few mouse clicks, I guess.
I think this situation may even be caused by "stepping through"
macro, allowing the macro to open various files and then shutting th
macro down without allowing the macro to close files and shut-dow
Excel (is it good form to close all files prior to shutting-down Exce
in a macro?).
I have coded another macro that opens each of these files, saves eac
of these files, and then closes each of these files; currently, th
macro sends me an e-mail if all procedures are completed OK and i
sends me an e-mail if one or more of them could not be saved, includin
an error message and the name(s) of the files that could not be saved.
I have scheduled this macro to fire at 9:10 am and 5:10 pm (shortl
after each of the other two macros).
Can anyone shed any light on this situation?
Thanks in advance,
Chuckles12
I have VBA code stored in two .xlA files (not installed as an 'AddIn
in Excel): one macro fires at 9 am and the other fires at 5 pm. The
pm macro imports data from an accounting server and updates two .xl
data files and saves them using constant filenames (the .xlS file
contain zero VBA code). The 9 am macro, using the preceding day's dat
files plus data imported from another server, crunches all the data an
sends out e-mails based on the values in specified cells. All of thi
usually works.
However, there has occasionally been a problem with a macro crashing (
pop-up error message indicating that a 'read-only' file cannot b
accessed <-- this really means that it cannot be saved). Of course
this only occurs on the .xlS files since the .xlA files are never save
when the macros are executed. However, when revising code in the .xl
files, I occasionally get the same message; this is true even thoug
the .xlA macro will run just fine when the .xlA file is opened on a
unintended 'read-only' basis (regardless of the setting o
'Application.DisplayAlerts=?').
I am currently in a testing mode; my ultimate goal is to locate thes
macros and data files on an Autosys server -- therefore, zero pop-ups.
I am not sure what causes the above sickness, but here are the symptons
the .xlS file or the .xlA file is "tied up" on my network login, eve
though when I go into 'Windows Task Manager - Processes', EXCEL.EXE i
not listed; also, no change in "tied up" status when powering th
machine down and re-powering and re-logging-in to our LAN; the file ca
be copied but it cannot be deleted. The only solution has been to cal
our LAN Administrator and request that the "tie up" be severed; he doe
so by making a few mouse clicks, I guess.
I think this situation may even be caused by "stepping through"
macro, allowing the macro to open various files and then shutting th
macro down without allowing the macro to close files and shut-dow
Excel (is it good form to close all files prior to shutting-down Exce
in a macro?).
I have coded another macro that opens each of these files, saves eac
of these files, and then closes each of these files; currently, th
macro sends me an e-mail if all procedures are completed OK and i
sends me an e-mail if one or more of them could not be saved, includin
an error message and the name(s) of the files that could not be saved.
I have scheduled this macro to fire at 9:10 am and 5:10 pm (shortl
after each of the other two macros).
Can anyone shed any light on this situation?
Thanks in advance,
Chuckles12