I wonder about your Me.fFullName - does it return a full, absolute path (eg,
"C:\path1\filename.xls") or a relative one ("filename.xls")? If it's
relative, the question is where is it saving it.



Do you get an error of some kind? Can you step through the code and see
what's happening? When it hits the SaveAs line, you should be able to tell
if you flip back to the Workbook and see if it is now saved or not and with
what name. And if you then try File/SaveAs you should be able to tell in
which folder it's saved too.

The me.ffullname does provide a full  path in every instance.
I've also tried seperating the saving of the new workbook  from the
creation. When i run the code until the saving I notice that in the
succesfull runs a workbook "book2" is created, in the unsuccessfull
runs nothing is created and subsequently ofcourse nothing is saved.

What I would do is step through the code in the debugger and see if I could
catch it failing to see under what conditions it fails. It's so hard to
track down bugs that only happen sometimes, so I always try to figure out
what the conditions are that cause the failure. I would also break out each
action into a separate line of code so you might be able to narrow it down
even further. In this case, I would split up the .Add from the .SaveAs and
see if that helps you at all.