|
Posted to microsoft.public.excel.programming
|
|
|
Macro suffers from premature exiting
Fred,
On Feb 12, 8:28 pm, "Fred Smith" wrote:
ThanksMarchand, I'll take a look at CleanProject.
The code starts out as follows:
Option Explicit
' About 30 Dims
Sub PrepareMeetingPackage()
' Format Holdings sheet
On Error Resume Next
ValueAsof = InputBox("Verify valuation as of date", , Date - 1)
If Err < 0 Then Exit Sub 'Cancel clicked
Set Book1 = ActiveWorkbook
ActiveSheet.Name = "Export" 'After executing this statement, the
macro quits
Range("C2").Select 'If I step around the above, macro
quits at next ActiveSheet
ActiveWindow.FreezePanes = True
On Error Resume Next
Application.DisplayAlerts = False
Sheets("Sheet2").Delete
Sheets("Sheet3").Delete
Application.DisplayAlerts = True
On Error GoTo 0
Sheets.Add
ActiveSheet.Name = "Holdings" 'If I step around this statement, macro
quits at the copy
DLCol = Application.Match("Security", Sheets("Export").Range("1:1"), 0)
If IsError(DLCol) Then GoTo MissingData
Sheets("Export").Columns(DLCol).Copy Destination:=Columns("B")
' About 500 more lines of code which used to work
' Code in other modules has been changed recently, but not this one.
--
Regards,
Fred
wrote in message
oups.com...
Fred,
A snippet of code would be helpful here just to be curious about it.
If it's been wokring for years, though, you might try running your
code through Rob Bovey's wonderful "CleanPorject" utility. It clears
up a lot of odd and inexplicable behvaior, particularly for long-used
(and long) VBA code. You can find it at:
http://www.appspro.com/Utilities/CodeCleaner.htm
=Marchand=
On Feb 11, 1:54 pm, "Fred Smith" wrote:
One of my macros, which has been working for years, now quits prematurely. It
will consistently quit about the 5th statement in on a activesheet.name
command.
It executes the command, but then quits, with no error message. If I step
past
this command, it will quit about 5 statements later on a copy command (after
executing it as well).
The project is 3 modules long, and about 1000 statements in each module. I've
exported each module to a .bas file, and reimported them, to hopefully get
rid
of any fragmentation. There is no protection on the workbook.
I'm using XL2002 SP3 on Windows XP.
Any suggestions from the gurus?
--
Regards,
Fred
|