I have a particular excel macro-enabled tool that has been in place for approximately 9 months working very well. The files are stored on the company shared drive, with users accessing via read-only files. Everyone using the tool has been running Excel 2003 until this past week. After the upgrade, I have seen several errors occuring that make it appear that certain lines of code are being ignored. Most often, it is a command to close an open workbook. I started with "ActiveWorkbook.Close", then tried "Workbooks("the name.ext").Close" but neither seems foolproof. Nor does the error happen consistently.
I have also seen instances where the command is an "Exit Sub" command within an IF statement. We confirmed that the IF statement was working as we were receiving a pop-up message, but even with the EXIT IF right after the message box, code after the IF statement was performed.
Does anyone know of anything that would cause 2007 to skip lines of code?
Thanks,
Andy
I have also seen instances where the command is an "Exit Sub" command within an IF statement. We confirmed that the IF statement was working as we were receiving a pop-up message, but even with the EXIT IF right after the message box, code after the IF statement was performed.
Does anyone know of anything that would cause 2007 to skip lines of code?
Thanks,
Andy
