T
ThermoZan
So we ran into this problem too. The first workaround we tried was printing out the Visio so as to keep a visual record of the data in case it was completely lost.
What has been working though so far and keeps all of our data is going to File and choosing Send To. Now at our company they have limits for size of emails, so like a 30 Mb attachment would get discipline. So to avoid this, we send it to ourselves, BUT before even sending it we click to open the Attachment File, and choose to Save As, and save it to the desktop. It seems to bypass the problem that seems to create the #3400 Error, and we get a copy with all the current data.
I hope this works; as well, I expected this problem not to exist anymore with the Visio 2003 product and latest service packs/updates, but obviously yet again 'It's Microsoft.'
Z
EggHeadCafe.com - .NET Developer Portal of Choice
http://www.eggheadcafe.com
What has been working though so far and keeps all of our data is going to File and choosing Send To. Now at our company they have limits for size of emails, so like a 30 Mb attachment would get discipline. So to avoid this, we send it to ourselves, BUT before even sending it we click to open the Attachment File, and choose to Save As, and save it to the desktop. It seems to bypass the problem that seems to create the #3400 Error, and we get a copy with all the current data.
I hope this works; as well, I expected this problem not to exist anymore with the Visio 2003 product and latest service packs/updates, but obviously yet again 'It's Microsoft.'
Z
EggHeadCafe.com - .NET Developer Portal of Choice
http://www.eggheadcafe.com