No condescension intended. Although Excel does warn of lost features in
Excel proper it does not re VBA code. The Excel warning is for features the
file format itself does not support. The VB file format does support the
retaining of all object methods, etc. It isn't until it arrives in a
specific version of Excel that the problem arises.

Remember that VB changes with every version of Excel and there is no way to
know what version of Excel you will be opening the XLS in. So you'd have to
get a warning for every line of code that wouldn't work in Excel 2003, 2002,
2000 and 97 separately since the XLS file could be opened in any of them.
What a nightmare I'm sure you'd agree, my friend.

--
Jim
"DanF" wrote in message
...
| Thats not the point my friend.
|
| If you create and save the file as a '97 - '03 format i would expect it to
| inform me of possible problems.
|
| There's no need for the condescending comments.
|
|
| "Jim Rech" wrote:
|
| I hope there isn't any more little surprises like this!
|
| Why not? Do you think MS should not make object model changes because
they
| will not work in earlier versions? It would be hard to add features
| wouldn't it?
|
| --
| Jim
| "DanF" wrote in message
| ...
| | It's OK, I've changed the code to the way the Office 2003 PC wants to
see
| it.
| |
| | I hope there isn't any more little surprises like this!
| |
| | "DanF" wrote:
| |
| | Howdy
| |
| | I've got a worksheet I created in Excel 2007, and saved as a .xls
(Excel
| | '97-2003) with a macro that uses the following line of code:
| |
| |
| |
|
ActiveWorkbook.Worksheets(combinedEMDataTypes).Aut oFilter.Sort.SortFields.Clear
| |
| | When I run the sheet in Excel 2003, it bungs out an error that
states
| | "Object doesn't support this property or method"
| |
| | I don't think this PC has been updated since it got built as it's
| supposed
| | to be 'offline', so would an update fix it, or am I going to have to
| figure
| | out another way of making my code work?
| |
| | Cheers peeps
| | Dan
|
|
|