>>I am creating a word document from VFP data and have noticed that this process run extrememly slow on the average machine (p166) and relatively slow on fast machines (pII 400). My question is this, are there any general tips someone can give me that I may have over looked in having vfp communicate to word. Some little known or not well documented thing I need to do or failed to do that would make creating a word document slow. The process write now does the following: Get the data, open a word template, place the data into the template, then save the word doc under a new name. The document created can range from 5 to 50 pages. Any help would be appreciated. By the way, the document does get created and the process works great, but it is very slow.
>
>Bret,
>Word automation is slow naturally it uses VBA :) But slow is a loose definition you know. Before I attempt to say anything could you give ie: how much it takes to complete now. Till then Application.datatoclip and preformatting what will be put in word in VFP speeds up a lot relatively ;) I mean, if possible do one InsertAfter in word rather than many.
>Cetin

Thanks for the reply Cetin. Yeah I know VBA is slow, but I never thought it would be this slow. If I am processing a say 20 page document, the user is telling me that it takes about 20 minutes to create the document on their P166 machine. On mine the document gets created in about 7 minutes (PII 400). This is creating a pretty complicated document. Reading from memo files and table data. Bolding and underlining where told. What do you mean by Application.DataToClip?