P
Pasquale Scorca
I have an Excel workbook that uses two other *.xlss.
Before that I added some instructions the following
statement functions:
"ActiveWorkBook.SaveCopyAs PathDest", where PathDest is a
string containing the entire path of the new copy of the
active workbook.
But when I write a sub (without any calling of it) Excel
2000 has crashed, with a violation for VBE6.dll.
This crash has occured on tuo PCs:
the first, with Windows 2000 SP2 and Excel 2000 SR-1;
the secord, with Windows 2000 (no SP) and Excel 2000 SR-1.
On another PC, with Windows 2000 SP 2 and Excel 2000 SR-1
this crash HASN'T occured.
I have the original file of this *.xls that functions, but
when I add some instructions Excel 2000 crashes.
The dimension of this *.xls is about 240 kb.
How can I solve this issue?
Do I must update my Windows system?
Do I must update my Excel?
Do I must update my RAM?
Does a log exist to capture this violation for VBE6.dll?
Many thanks for your suggests.
Best regards
Pasquale
Before that I added some instructions the following
statement functions:
"ActiveWorkBook.SaveCopyAs PathDest", where PathDest is a
string containing the entire path of the new copy of the
active workbook.
But when I write a sub (without any calling of it) Excel
2000 has crashed, with a violation for VBE6.dll.
This crash has occured on tuo PCs:
the first, with Windows 2000 SP2 and Excel 2000 SR-1;
the secord, with Windows 2000 (no SP) and Excel 2000 SR-1.
On another PC, with Windows 2000 SP 2 and Excel 2000 SR-1
this crash HASN'T occured.
I have the original file of this *.xls that functions, but
when I add some instructions Excel 2000 crashes.
The dimension of this *.xls is about 240 kb.
How can I solve this issue?
Do I must update my Windows system?
Do I must update my Excel?
Do I must update my RAM?
Does a log exist to capture this violation for VBE6.dll?
Many thanks for your suggests.
Best regards
Pasquale