Compatability Checker Question

[RJQMAN]

I have a workbook designed in Excel 2003. When it is opened in Excel
2007 oe 2010, it functions fine. However, when the user goes to save
it (even if they have not changed it at all) the compatability checker
pops up and says there is data outside of the acceptable range on one
sheet. But it is not true. When I unprotect the sheet, the FIND
function goes to some totally blank cell in the middle of the
workbook. Then when I try to save it again, it tells me that there
are data validation issues where on one sheet, another sheet is
referenced. But there are no such references in my workbook. And
again, the FIND function in the checker simply does not find them, and
the message then disappears. But others pop up. All bogus.

If I go ahead and save as a 2003 file anyway, it appears that the file
functions fine with no loss of functionality as far as I have been
able to discover. Is there anything I can do so that users other than
me are not intimidated by this Compatability Checker message that
appears to be in error?

Or is there something wrong with my workbook? Is the Compatability
Checker faulty? I am at a loss as to how to deal with this. I know I
can switch the Compatability Checker off when I personally use the
workbook by unchecking the option, but the 'soccer moms' that use the
program are intimidated by the message. If I try to block the message
using VBA, the workbook crashes when opened on Excel 2000 or 2003.
Can anyone shed some light on what might be going on?

 

[GS]

RJQMAN wrote :

I have a workbook designed in Excel 2003. When it is opened in Excel
2007 oe 2010, it functions fine. However, when the user goes to save
it (even if they have not changed it at all) the compatability checker
pops up and says there is data outside of the acceptable range on one
sheet. But it is not true. When I unprotect the sheet, the FIND
function goes to some totally blank cell in the middle of the
workbook. Then when I try to save it again, it tells me that there
are data validation issues where on one sheet, another sheet is
referenced. But there are no such references in my workbook. And
again, the FIND function in the checker simply does not find them, and
the message then disappears. But others pop up. All bogus.

If I go ahead and save as a 2003 file anyway, it appears that the file
functions fine with no loss of functionality as far as I have been
able to discover. Is there anything I can do so that users other than
me are not intimidated by this Compatability Checker message that
appears to be in error?

Or is there something wrong with my workbook? Is the Compatability
Checker faulty? I am at a loss as to how to deal with this. I know I
can switch the Compatability Checker off when I personally use the
workbook by unchecking the option, but the 'soccer moms' that use the
program are intimidated by the message. If I try to block the message
using VBA, the workbook crashes when opened on Excel 2000 or 2003.
Can anyone shed some light on what might be going on?

Robert,
You'll need to write your own 'Save' routine OR hook Excel's 'Save'
procedure so you can run your own code to turn off this feature
temporarily, save the file, then turn it back on.

Example:
In your own 'Save' routine...

With Application
.EnableEvents = False: .DisplayAlerts = False
ThisWorkbook.Save True
.EnableEvents = True: .DisplayAlerts = True
End With

 

[RJQMAN]

RJQMAN wrote :












Robert,
You'll need to write your own 'Save' routine OR hook Excel's 'Save'
procedure so you can run your own code to turn off this feature
temporarily, save the file, then turn it back on.

  Example:
  In your own 'Save' routine...

    With Application
      .EnableEvents = False: .DisplayAlerts = False
      ThisWorkbook.Save True
      .EnableEvents = True: .DisplayAlerts = True
    End With

--
Garry

Free usenet access athttp://www.eternal-september.org
ClassicVB Users Regroup! comp.lang.basic.visual.misc

Thanks again Garry. I will try it again. I did not have much luck
with the displayalerts=false on my first attempt. I still got the
error on 2007. Then when I used the code that actually worked on
2007, 2003 crashed with that code (I found it on this group, but I
have fogrtotten what it was). I even tried to presort if it was on
2003 or 2007, but 2003 crashed before attempting to run the code
saying that the code was invalid.

Bob

 

[GS]

RJQMAN formulated the question :

Thanks again Garry. I will try it again. I did not have much luck
with the displayalerts=false on my first attempt. I still got the
error on 2007. Then when I used the code that actually worked on
2007, 2003 crashed with that code (I found it on this group, but I
have fogrtotten what it was). I even tried to presort if it was on
2003 or 2007, but 2003 crashed before attempting to run the code
saying that the code was invalid.

Bob

Can you post the code? What I posted is a snippet from my XLA shutdown
procedure which runs problem free in both early/current versions.