Re: Word mail merge with foxpro

From: Peter Jamieson (pjj_at_KillmapSpjjnet.demon.co.uk)
Date: 10/13/04 

Date: Wed, 13 Oct 2004 23:20:18 +0100

Have you tried the OLEDB approach I described? Does Word crash no matter
which approach you use? Does it crash even with a newly created test
database/data file?

> Does anyonw know how to unistall versions of mdac as it seems that may be
> where the problem is.

I don't know - I suspect the best you can do is re-install or install a
later version. 

-- 
Peter Jamieson
"susan crookshank" <susan crookshank@discussions.microsoft.com> wrote in
message news:9D965367-C16F-44D6-AF60-4EAE60D62EFC@microsoft.com...
> I am trying to connect to a dbf fine not the database. I have aslo tried
with
> the command method you have described but word crashes out as soon as t
tries
> to connect to the file. Unfortunately with no error messages to give us a
> clue what the problem is.
>
> Does anyonw know how to unistall versions of mdac as it seems that may be
> where the problem is.
>
> "Peter Jamieson" wrote:
>
> > > Does anyone know how to define what appears in the files of Type list.
> >
> > I do not thnk there is any way to change this.
> >
> > I'm not particularly familiar with FoxPro any more but
> > Are you trying to open a .dbc? If so, the following may help.
> >
> > I do not think you will be able to open a .dbc using ODBC by selecting
the
> > ..odc in this dialog box. I suspect the problem is that there is too
much
> > source-specific hardcoding in the component that connects to these
files.
> >
> > If you are actually getting data from a .dbf file, you should be able to
> > select the .dbf directly in the usual way, selecting the appropriate
ODBC
> > driver in the Confirmation dialog.
> >
> > Otherwise, if you need to However, you can connect programmatically
using
> > OpenDataSource, e.g. using a User/System DSN called vfpdbc, a .dbc at
> > c:\fp\fp.dbc, fetching data from a table called t, you can use
> >
> > ActiveDocument.MailMerge.OpenDataSource _
> > Name:="", _
> > connection:="DSN=vfpbc;SourceType=DBC;SourceDB=C:\fp\fp.dbc", _
> > sqlstatement:="SELECT * FROM t"
> >
> > You do not seem to need the Subtype:=wdMergeSubtypeWord2000 that is
usually
> > needed when Name:=""
> >
> > As long as you have MS Query on your system, you can connect to the .dbc
> > using that approach (in the Select Data Source dialog, open the Tools
menu
> > at the top right and use the MS Query option). However, in that case you
may
> > have to create the ODBC DSN so that it points to a specific .dbc, or you
> > could perhaps create a File DSN for each .dbc and use that.
> >
> > Finally, if you have the VFP OLEDB provider installed, you could
consider
> > connecting using that. Perhaps the easiest way is to create a .udl file
> > using the Microsoft Data Link editor - Word 2003 recognises that as a
data
> > source file type so you do not even need to check
> > Tools|Options|General|Confirm conversion at open. If you leave the
database
> > name blank, you should be prompted for it; If you fill it in, you should
be
> > taken straight to the table selection dialog. You can probably use the
.odc
> > approach instead.
> >
> > FWIW, this sort of stuff seems to work a lot more smoothly in Word 2003
than
> > 2002, at least in part because of some fixes, but the point is that if
you
> > also need to use Word 2002 you may have more difficulty.
> >
> > -- 
> > Peter Jamieson
> >
> > "susan@soulbury" <susan@soulbury@discussions.microsoft.com> wrote in
message
> > news:FE4438C6-A5B8-4D8B-BD02-85E01156A9DD@microsoft.com...
> > > I have the foxpro ODBC driver version 6.1.8629.1 loaded on my machine
with
> > > word version 2003. I am trying to use mail merge to merge with foxpro
data
> > > but when opening the data source in the mail merge helper I hit
problems.
> > >
> > > Firstly the files of type drop down does not give a foxpro option. So
I
> > try
> > > and link to a foxpro table using all file types hoping to get a
confirm
> > > conversion type. Then word crashes with no error message at all. I
have
> > > before now used foxpro coding to control word to perform a  mailmerge
> > > defining the DSN name and it works even if foxpro does not appear in
the
> > > list. But this fails aswell.
> > >
> > > Does anyone know how to define what appears in the files of Type list.
> > >
> > > Does anyone have any idea why it may be crashing and I cannot create
the
> > > merge.
> > >
> > > Thank you in anticipation, I have gone through all of MSDN to no avail
and
> > I
> > > am now stuck
> >
> >
> >

Relevant Pages

  • Re: Word mail merge with foxpro
    ... I am trying to connect to a dbf fine not the database. ... > I do not think you will be able to open a .dbc using ODBC by selecting the ... >> but when opening the data source in the mail merge helper I hit problems. ... >> Firstly the files of type drop down does not give a foxpro option. ...
    (microsoft.public.word.mailmerge.fields)
  • Re: Word mail merge with foxpro
    ... I'm not particularly familiar with FoxPro any more but ... I do not think you will be able to open a .dbc using ODBC by selecting the ... OpenDataSource, e.g. using a User/System DSN called vfpdbc, a .dbc at ... > but when opening the data source in the mail merge helper I hit problems. ...
    (microsoft.public.word.mailmerge.fields)
  • Word Mail Merge with Foxpro data
    ... with the data source being a Foxpro database. ... previous versions, I chose "Open Data Source", chose files ... FoxPro, chose my dbf, and then it prompted me to "Confirm ...
    (microsoft.public.word.mailmerge.fields)
  • RE: Foxpro 2.5 link from Acccess 2000
    ... Thank you for using the Microsoft Access Newsgroups. ... FoxPro is not listed as an option for file type. ... Open the Access database that you want to import into. ... In the Select Data Source dialog box, ...
    (microsoft.public.access.externaldata)
  • Re: Access 2000 run-time error 80004005 - HELP
    ... try changing the column definition (make a backup of the ... > destination table is a linked table originating from a FoxPro v3 database. ... it appears MS is letting FoxPro die a slow death. ...
    (microsoft.public.fox.programmer.exchange)
Loading