Hi,

I've installed my fmdbase in a network pc/mac that has an NT pc-server with Filemaker Server on it.

Merging with filemaker is working ok on my little network (I open the Word doc and activate merge) but seems to be causing problems on this network.

Should I install the Merge documents on the server? Or should I install the Word documents locally? How do I refer to fmfiles managed by filemaker server?:

I could open the document through filemaker with applescript but this is soooo slow and I very often get error messages!

And above all how do I get my links right...pffff, this might all seem a bit confusing but I hope someone gets my question.

Thankyou for reading this question even if you haven't got an answer.

"Merging with filemaker" is a little vague. What exactly are you doing? How are you accessing FM, exporting a merge file, etc.?

-bd

Why use Word at all: everything can be done in FileMaker Pro using layouts with FM's own merge codes. Much easier!

Merging with filemaker means that Word connects to Filemaker through ODBC for the PC's and uses the build in Filemaker Merge in Word.

quote:

---

Originally posted by LiveOak:

"Merging with filemaker" is a little vague. What exactly are you doing? How are you accessing FM, exporting a merge file, etc.?

-bd

---

I know what you mean,

but... we're talking about merging files on which there's a lot of text (terms and stuff) that shouldn't be kept by the database as it just takes up unnecessary space.

Still the possibility must exist to modify this text, in a few cases, even though it is of no 'database' importance.

So I can't just 'type' this text on the layout as it needs to be changed a little in certain cases (but not through the whole database).

The only way to keep this text in a database is to store it in a field and that's a waste of space.

Also Filemaker doesn't offer the ease and possibilities of a text editor. This is no reproach as it is a database and no text editor.

That's why I want to export these records and merge them with Word which would exactly give the possibilities we're looking for that Filemaker can't offer (yet).

quote:

---

Originally posted by michele:

Merging with filemaker means that Word connects to Filemaker through ODBC for the PC's and uses the build in Filemaker Merge in Word.

---

I know what you mean,

but... we're talking about merging files on which there's a lot of text (terms and stuff) that shouldn't be kept by the database as it just takes up unnecessary space.

Still the possibility must exist to modify this text, in a few cases, even though it is of no 'database' importance.

So I can't just 'type' this text on the layout as it needs to be changed a little in certain cases (but not through the whole database).

The only way to keep this text in a database is to store it in a field and that's a waste of space.

Also Filemaker doesn't offer the ease and possibilities of a text editor. This is no reproach as it is a database and no text editor.

That's why I want to export these records and merge them with Word which would exactly give the possibilities we're looking for that Filemaker can't offer (yet).

quote:

---

Originally posted by michele:

Merging with filemaker means that Word connects to Filemaker through ODBC for the PC's and uses the build in Filemaker Merge in Word.

---

A bit off of this problem, but FM can do all things like stand alone Word document usually used for mailmerge.

And why not export addresses from FM and use Mailmerge purely in Word?