Home |
Search |
Today's Posts |
#1
![]()
Posted to microsoft.public.excel.programming
|
|||
|
|||
![]()
I updated a workbook that is becoming widely distributed. I have tried to
keep it running on Office 97 computers but this latest problem has me stumped. On computers with Office 97, Excel will not allow me to open the module to trace the offending code. I added " If Val (Application.Version) 8 Then... " to try and trap the recently added lines. Didn't help. The added lines that I thought were causing this a Application.DisplayAlerts = False .. .. and Application.DisplayAlerts = True I don't think these are causing the problem anymore. Is there a way to decompile an Excel file so that I might be able to again open the file with 97 ? I really need to be able to trace the logic. The program only fails when one macro is called. The rest of the program works fine. |
#2
![]()
Posted to microsoft.public.excel.programming
|
|||
|
|||
![]()
Hi Rich
Unprotect the VBA in Excel 2000 and save the file now open the file in 97 and look at the problem code -- Regards Ron de Bruin http://www.rondebruin.nl "Rich J" wrote in message ... I updated a workbook that is becoming widely distributed. I have tried to keep it running on Office 97 computers but this latest problem has me stumped. On computers with Office 97, Excel will not allow me to open the module to trace the offending code. I added " If Val (Application.Version) 8 Then... " to try and trap the recently added lines. Didn't help. The added lines that I thought were causing this a Application.DisplayAlerts = False . . and Application.DisplayAlerts = True I don't think these are causing the problem anymore. Is there a way to decompile an Excel file so that I might be able to again open the file with 97 ? I really need to be able to trace the logic. The program only fails when one macro is called. The rest of the program works fine. |
#3
![]()
Posted to microsoft.public.excel.programming
|
|||
|
|||
![]()
Duh! I can't believe I didn't even think of that. I found the problem right
away. Thanks Ron Rich J "Ron de Bruin" wrote: Hi Rich Unprotect the VBA in Excel 2000 and save the file now open the file in 97 and look at the problem code -- Regards Ron de Bruin http://www.rondebruin.nl "Rich J" wrote in message ... I updated a workbook that is becoming widely distributed. I have tried to keep it running on Office 97 computers but this latest problem has me stumped. On computers with Office 97, Excel will not allow me to open the module to trace the offending code. I added " If Val (Application.Version) 8 Then... " to try and trap the recently added lines. Didn't help. The added lines that I thought were causing this a Application.DisplayAlerts = False . . and Application.DisplayAlerts = True I don't think these are causing the problem anymore. Is there a way to decompile an Excel file so that I might be able to again open the file with 97 ? I really need to be able to trace the logic. The program only fails when one macro is called. The rest of the program works fine. |
Reply |
Thread Tools | Search this Thread |
Display Modes | |
|
|
![]() |
||||
Thread | Forum | |||
VBA macro runs fine, but freezes if I try to do ANYTHING else whileit runs | Setting up and Configuration of Excel | |||
Excel Macro runs fine, but freezes if I try to do ANYTHING else whileit's running | Setting up and Configuration of Excel | |||
Office 2000 Excel Macro runs very slow in 2003, why? | Excel Discussion (Misc queries) | |||
Loop in my macro doesn't seem to be running; however, it compiles fine... | Excel Programming | |||
Runs Fine In Step Mode But Crashes Excel Otherwise | Excel Programming |