Are CPU, Hard Drive, Keyboard and MSWord, records or fields in the database?
What is the significance of the numbers 1,1,1 and 2 to the left of them?

Aside, from that, you may have a table in the document created by executing
the merge and not realise it. From the Tables menu, select Show Gridlines
and see if there are any which would indicate that the data is actually in a
table.

Why not just however use a Select Query in Access to display the data that
you want and then use the Publish it with Word item under the Tools menu in
Access to get it into Word.

--
Hope this helps.

Please reply to the newsgroup unless you wish to avail yourself of my
services on a paid consulting basis.

Doug Robbins - Word MVP
"JohnB" wrote in message
...
Hi. A search has given me some info on Directory Merge but I need more
help.
The following was from Doug Robbins:

"Use a Directory type mailmerge main document in which you have a one row
table into the cells of which you insert the mergefields. If you have
nothing else in the document, when you execute the merge to a new
document,
that document will contain a table with a row of data for each record in
the
data source"

I have tried this and I don't get what Doug suggests. My source is an
XP/Access 2000 table and I'm merging to Word 2002. The table contains the
following records:

1 CPU
1 Hard Drive
1 Keyboard
2 MSWord

When I create a Catalogue/Directory merge (using "merge it with microsoft
word" from the Access table) and then merge to a new document I get:

1 CPU1 Hard drive1 Keyboard2 MS Word2


If I enter a carriage return after the second merge field, I do get them
forming into columns but not in a table. (i.e in a grid layout like an
Excel
spreadsheet or an Access table).

Am I misunderstanding what is supposed to happen? Also, is it really the
case that you can't have anything else in the document? I was hoping to
merge
to a document containing at least some text and ideally some text and a
second table. I can see what happens when you put some text in - is there
no
way around this?

Thanks, JohnB