B
Beelymagee
The college has a timesheet app that requires Excel Macros be enabled, which
I've done. A user tries to execute the spreadsheet w/macro which should open
the spreadsheet and a navigation window. Has worked flawlessly prior to her
get a new PC - her previous PC Windows XP "profile" was moved over to her new
PC. Now, when she runs the timesheet and enables the macro, a 2nd window
appears (Visual Basic editor?) with the word BREAK tacked on to the file. The
interface for the timesheet appears to be functioning, but none of the
options work - dead clicks.
The debug window lists the timesheet script, it displays a password window
when I try to access the script. If I close the VB script window, the
following is displayed, "This command will stop the debugger." and then I can
close the failed timesheet window.
Any ideas how this script debugging got turned on and how to turn it off?
I've done quite a bit of searching and no luck.
I've done. A user tries to execute the spreadsheet w/macro which should open
the spreadsheet and a navigation window. Has worked flawlessly prior to her
get a new PC - her previous PC Windows XP "profile" was moved over to her new
PC. Now, when she runs the timesheet and enables the macro, a 2nd window
appears (Visual Basic editor?) with the word BREAK tacked on to the file. The
interface for the timesheet appears to be functioning, but none of the
options work - dead clicks.
The debug window lists the timesheet script, it displays a password window
when I try to access the script. If I close the VB script window, the
following is displayed, "This command will stop the debugger." and then I can
close the failed timesheet window.
Any ideas how this script debugging got turned on and how to turn it off?
I've done quite a bit of searching and no luck.