Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
DiscussionsAccessExcelInfoPathOutlookPowerPointPublisherWord
DirectoryUser Groups
Related Topics
Outlook ExpressInternet ExplorerWindowsMS Server ProductsMore Topics ...

MS Office Forum / Word / Mailmerge and Fax / February 2006

Tip: Looking for answers? Try searching our database.

mailmerge filename limits

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
christophe - 08 Feb 2006 10:40 GMT
Hi,

Could it be that there are limitations about the table/filename
which contains the mergefields ?
for example 8 characters long without the fileextention

regards
christophe
Signature

              \|||/
             (o o)
----ooO-(_)-Ooo-------------

Graham Mayor - 08 Feb 2006 12:06 GMT
Fieldnames should ideally be ten characters or less with no spaces.
Filename length depends on the operating system.
What *exactly* are you have problems with?

Signature

<>>< ><<> ><<> <>>< ><<> <>>< <>><<>
Graham Mayor -  Word MVP

My web site www.gmayor.com
Word MVP web site http://word.mvps.org
<>>< ><<> ><<> <>>< ><<> <>>< <>><<>

> Hi,
>
[quoted text clipped - 4 lines]
> regards
> christophe
christophe - 08 Feb 2006 13:04 GMT
When opening the doc
It's says it can't find the table
then I click the button to point again
to that table.  After choosing the proper table,
again it says it can't find ?!?
When I make the tablename smaller then it accept it.
Ok, this is not a big deal, I solved it (not so easy to think/find that
one...)
but I was also looking for documentation about this limitations

regards
christophe

Signature

              \|||/
             (o o)
----ooO-(_)-Ooo-------------

> Fieldnames should ideally be ten characters or less with no spaces.
> Filename length depends on the operating system.
[quoted text clipped - 8 lines]
>> regards
>> christophe
Peter Jamieson - 08 Feb 2006 13:24 GMT
Just a guess, but...

Assuming you are accessing a FoxPro data source (as you suggest in another
thread) this limitation is probably imposed by the method Word uses to
connect to the data. Word always used to connect to .dbf files using Jet
(Access) . Jet uses "installable ISAMs (IISAMs) to connect to "foreign" data
sources such as dBASE. The Jet IISAM is designed to connect to various
versions of dBASE, up to version 5 (V) I think. My guess is that all those
versions of dBASE are so old that they only allow the old DOS 8.3 filename
format and that that is the source of this limitation.

I assume that as FoxPro developed, this limitation was relaxed, but that the
IISAM has not been updated to allow for the changes.

For recent FoxPro files (whether .dbf or .dbc) you have to use the
appropriate ODBC or OLEDB driver for FoxPro (these can be downloaded from
the Microsoft web site).

Peter Jamieson

> When opening the doc
> It's says it can't find the table
[quoted text clipped - 21 lines]
>>> regards
>>> christophe
christophe - 14 Feb 2006 09:21 GMT
Thanks Peter,

Does this mean that all users must download
this OLEDB driver ?
Or can it be included in a word document ?

regards
christophe

Signature

              \|||/
             (o o)
----ooO-(_)-Ooo-------------

> Just a guess, but...
>
[quoted text clipped - 41 lines]
>>>> regards
>>>> christophe
Peter Jamieson - 14 Feb 2006 10:22 GMT
> Does this mean that all users must download
> this OLEDB driver ?

Yes, if I am correct.

Peter Jamieson
> Thanks Peter,
>
[quoted text clipped - 51 lines]
>>>>> regards
>>>>> christophe

Rate this thread:






 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.