OK, I don't think the fact that you cannot see a suitable ODBC DSN means
that the connections are DDE - in Word 2003 it's more likely that they are
OLEDB, which does not need a DSN.
> Also when I open a new word doc and try to connect it comes up with a data
> source dialogue box - I select new source button (as the IQE is not
> showing
> up) select the DB, and then it shows a ''OLEDB'' dialogue box and I
> select
> ''microsoft access DDE'' but it still comes up with the error problem
I don't think that's what you should be doing. From Word, you need to locate
the .mdb /wherever it is/ When the Select Data Source dialog box opens, all
you see is the files that are under My Data Sources for the user concerned.
So you have to locate the IQE.mdb file by navigatiing to the correct network
path, and select that. Then (as long as Tools|Options|General|"Confirm
conversion at open" is checked) you should see the DDE option and you should
be able to select it.
If you click the New Source button, you get into a dialog which tries to set
up an Office Data Connection file which "points" to the mdb file. A .odc has
a similar function to a file DSN but is for OLE DB connections, not ODBC
connections. This isn't really where you want to be, unless the users with
working systems have the correct .odc and what you need to do is copy it
onto the non-working system.
> You mentioned ''partiularly if the connection details are set up by code
> in
> Access and not in word mail merge doc''.
When you make a connection to a data source in Word, and save the mail merge
main document, the connection is retained - in theory, the next time the
user opens that mail merge main document, Word should re-open the data
source as well (it may ask a question about SQL first).
You can set up that connection in a number of ways:
a. manually in Word
b. using Word VBA
c. using OLE automation from another piece of sofware, such as Access.
The Word VBA could also be set up to run as an "AutoOpen" macro, so that it
would run each time Word opened the document, even if a piece of code in
Access opened it.
Judging from what you have said so far, I would guess that the person who
created your system set up the connections in Word. However, if the word
document is being launched from Access, then it is possible that some code
in there is making the connection. To find out, you would need to open the
Access database, look at the form that is used to initiate the merge, and
see if what Access macro or VBA module is invoked by the form to initiate
the launch.
Peter Jamieson
> Hi Peter
>
[quoted text clipped - 191 lines]
>> >> > Many Thanks in Advance
>> >> > capri
capri - 09 May 2007 15:35 GMT
Hi Peter
Thank you for you quick reply and help with this issue.
Sorry I have not managed to even leave a thank you line, have been snowed in
at work dealing with users queries and report writing.
I appreciate the time and feedback. I would use your reply to try and solve
this problem, hopefully i find a solution.
Once again many many thanks for ur help
capri
> OK, I don't think the fact that you cannot see a suitable ODBC DSN means
> that the connections are DDE - in Word 2003 it's more likely that they are
[quoted text clipped - 245 lines]
> >> >> > Many Thanks in Advance
> >> >> > capri
Peter Jamieson - 09 May 2007 19:19 GMT
Thanks for the feedback - just ask again if you need further help.
Peter Jamieson
> Hi Peter
>
[quoted text clipped - 301 lines]
>> >> >> > Many Thanks in Advance
>> >> >> > capri