S
sparrow_ce
Is it possible that the process of emailing using Outlook (combined with
company email filters) could do anything to alter the state of vb code and vb
controls? I emailed (using Lotus Notes) a vb document complete with vb
controls/userforms, I had thoroughly tested, to others in remote locations to
do further testing in the true environment. They received document ok, and
the functionality worked when they opened the document there, but when they
returned it to me, it was corrupted, it would open up stuck in design mode,
the code was getting mixed up, the controls were getting renamed, such as
cmdEdit would become cmdEdit1, then cmdEdit11, etc. We thought we pinned it
down to them working on the document while opening it from Outlook instead of
saving first to server/hard drive, then editing, then re-attaching, as they
were also emailing directly from Outlook, instead of saving the document,
then attaching to email. But when they completely saved/closed the document,
then attached it, it was still corrupted upon receipt by me.
I am beginning to wonder if there are any known issues between Outlook/Word,
and/or if spam filtering software used by companies could be tinkering with
the code somehow, because when I receive the corrupted document, it still
works fine on their end, and the only difference is that it's been
transported via email.
Thanks for any suggestions.
company email filters) could do anything to alter the state of vb code and vb
controls? I emailed (using Lotus Notes) a vb document complete with vb
controls/userforms, I had thoroughly tested, to others in remote locations to
do further testing in the true environment. They received document ok, and
the functionality worked when they opened the document there, but when they
returned it to me, it was corrupted, it would open up stuck in design mode,
the code was getting mixed up, the controls were getting renamed, such as
cmdEdit would become cmdEdit1, then cmdEdit11, etc. We thought we pinned it
down to them working on the document while opening it from Outlook instead of
saving first to server/hard drive, then editing, then re-attaching, as they
were also emailing directly from Outlook, instead of saving the document,
then attaching to email. But when they completely saved/closed the document,
then attached it, it was still corrupted upon receipt by me.
I am beginning to wonder if there are any known issues between Outlook/Word,
and/or if spam filtering software used by companies could be tinkering with
the code somehow, because when I receive the corrupted document, it still
works fine on their end, and the only difference is that it's been
transported via email.
Thanks for any suggestions.