Re: Mailmerge from MDE not working

I tried this Ian and when I try to nominate the database that I want the
data link with, and then choose MS Acess Database (*.mdb; *.mde), I get an
error that says "Word cannot re-establish a DDE connection to Microsoft
Access to complete the current task." I have done an extensive internet
search on this and have not turned up anything helpful at this stage.

dixie

"Ian Hinson" <pparagon@xxxxxxxxxxxxxx> wrote in message
news:pTncf.13077$Hj2.8329@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx
>I reckon the best way forward to debug this is to see whether you can
>create a mail merge against the MDE file "by hand" ie. from within Word
>itself interactively, both with the MDE opened and with it not opened.
> This will enable you to test your assumption of whether the opened MDE is
> somehow locking you out of the data.
> Once you can do it by hand, then you should be able to do the same thing
> using automation.
>
> Ian.
>
> "Dixie" <dixie@xxxxxxxxxxx> wrote in message
> news:437140ee$1@xxxxxxxxxxxxxxxxxxxxxxxxx
>>I have a mailmerge that works fine from an MDB database using the
>>OpenDataSource method to send its data from a query within Access as part
>>of an automation sequence. Now, if I compile that mdb into an MDE, when I
>>click a button on the Access form that should produce the mailmerge, the
>>template opens on the screen with the fields visible, then an error
>>message.
>>
>> "File in use. <Filename> is locked for editing by 'another user'."
>>
>> I then have to shut the Word document down and when I return to the
>> Access App form, the Microsoft Access Error "Word is unable to open the
>> data source." is visible. I have previously run mailmerges by the
>> DoCmd.TransferText method and had the mail merge main document find the
>> small textfile produced with the data in it, but I want to use this
>> OpendDataSource method to send out the name of the query in Access where
>> the merge data is to be found.
>>
>> The query works fine. What seems to be stopping it from working is that
>> it sees the MDE as being locked for editing by another user (but it is OK
>> if it is an MDB) There must be something I am missing here and I can't
>> believe it hasn't happened to others.
>>
>> If you have run into this before could you please explain why this is
>> occurring?
>>
>>
>
>


.