Ken ,
great to here from you,
I kind of found an answer, but not exactly.
Using your code I have the sub see what type it allready is and save as the same extension.

But if the file was a 2007 version in compatible mode that just saves as .xls the file size bloats.

Beyond this, I only have 1 out of 23 users that are in 2007 all esle are 2000-2003,
so the 2007 issues turn out to be a moo point
(who cares what a cow thinks...)
I was over working the error capturing without thinking through the cases

It would be nice to be prepared if the users start upgrading.
How can I limit the bloat on save.
Rather than just pick a name and extension on save, how do I actully fire the save as type procedure to enable any compresion that might be bypassed other wise.

Thanks for remembering me.
Mark