Thank you so much Yuri, your help was really very valuable!

What I'm expreriencing now is the same that happended with Outlook automation with the "blessed" security patch, some time ago.

I wonder what will happen with ALL Word mailmerge automation VFP programs when users upgrade to Word 2003!

As stated in http://support.microsoft.com/default.aspx?scid=kb;EN-US;825765, registry editing (the MS sugested workaround) could turn into a big nightmare for some of us developers, mainly when there are strict rules in IT departments concerning this issue.

>See if you can follow the Cetin' advice.

Think I'll need further help on this, because I tried to open old mailmerge sets (doc, header file and data file) and experienced the same problem.

Once again, thank you!

Best regards,

Fernando

>Fernando,
>
>
>I believe that you meet the MS new "SQLSecurityCheck" "feature" introduced in MS Office Word 2003 and MS Word 2002 Service Pack 3 (http://support.microsoft.com/default.aspx?scid=kb;EN-US;825765).
>
>In previous Word/Office versions you do not need to reconnect, but after Word2002 SP3, you need to reconnect, and then you need to bypass the Data Source user dialog. Do not know how to help here; it looks like it is "by default" when using Excel file as a Data Source.
>
>See if you can follow the Cetin' advice.
>
>
>>Hi Yuri,
>>
>>>I was not able to reply via email because of:
>>
>>Sorry for that, I realy don't know what happened.
>>
>>>It is not quite clear to me, why do you need to connect again?
>>
>>No, I don't, but it gives me another error message if I don't try to open the data source.
>>
>>I sent you another set of files and snapshots (in case you can find some time to check it), showing what happens when I just doubleclik over the doc file name, and what happens when I try to run the mailmerge without issuing the opendatasourse.
>>
>>I really appreciate your help.
>>
>>Thanks so much!
>>
>>Fernando
>>
>>
>>