Help with backwards compatibility

[B Lynn B]

I have a file originally developed w/2003, now converted over to 2007 .xlsm
and updated with new code, formats etc... I have run the compatibility
checker and corrected all the issues it identifies, but when I try to save as
..xls file type, the failure is near universal - all formatting is stripped
away as well as VBA modules. Any hints as to what else the file might need
to be saveable as .xls? Known issues? Thanks for whatever insight you can
share!

 

[ker_01]

in 2007, XLSM is the file format for macro-enabled XL files. Save as XLSM to
continue working in 2007, or save down to 2003 format if you will also need
to use this file on 2003 machines.
HTH,
Keith

 

[B Lynn B]

Maybe I can clarify - it is exactly what responder Keith suggests I should do
that seems to not be doable. I know that's what should be done. My concern
is why it doesn't work, and what can be done to improve the outcome. When I
save my file from .xlsm to a 2003 compatible format (.xls), the translation
fails so dramatically that the result is unusable garbage. I have taken the
prescribed step of using compatibility checker and correcting the
incompatible features/functions. Any other suggestions please?

But thanks anyhow Keith - I do appreciate your effort to be helpful!

 

[Barb Reinhardt]

The VBA modules shouldn't be stripped if you're saving as a .xls. I'd expect
it if you are saving as .xlsx however.

 

[B Lynn B]

Thanks, Barb - I appreciate your input. Indeed what you say is what I would
expect as well - thus my complete bafflement at the current situation when
saving as .xls (not .xlsx) results in near complete deconstruction of the
file.

Any additional clues to what is actually going on would still be really great!