HI Albert
Have look at
www.report-sculptor.comCreating actual booklet (using RS Smart Text) is not as comfourtable as word, but it offer much more flexibility,
(You can actually program text/pages) and works much faster then word automation wld do.
So if booklet is predefined (not entered on the spot by user) then it can be done for sure.
(See help document in RS, it is actualy example of RS Smart Text in action)
I have done one scenario simillar to what you describe (executing report tasks and placing files to given folder)
but for serving NET website with PDFs from FoxPro. You run group of small foxpro exe files and they produce files uppon report request (simple que dbf table)
Works like a charm. Very fast and problem free. If any foxro instance gets busted for any reason, you simply kill it and raise another one. Now, for creation of the word files you would need to purchase XFRX as well but that is not much of a expence.
If they would settle for PDF then you are good to go.
Drop me an email and I wld explain you scenario in more details.
HTH
Sergio
>Hi all,
>
>A client of mine is having me develop a Word automation app to create booklets in Word by pushing across tables etc using Word automation. The overall process of firing up Word and creating the tables and all that is going swimmingly and creating the docs on their PC's if fine (albeit somewhat slow).
>
>Once this app gets into full production, they would rather have this app sit on a server and have a VFP app scan a table looking for data to process into a booklet. That is, it will check a table and if a new record is added, it would fire up this Word automation app, fire up Word, create the booklet and then drop it back in the user's directory (on the server).
>
>I have done something similar with long reports so that user's submit a request for a report and then check back later in their directory - but that all within the VFP report writer. In this case, I am a bit concerned that with Word being somewhat "flakey", creating 100 - 200 instances of Word a day and then destroying them, or just creating that many docs in a Word instance is going to cause Word to fail (memory leak etc).
>
>Anyone done this - offloading Word automation to another server and then crank through lots of docs? Also, your opinion of what might be best:
>
>1) use the VFP app to create a Word instance, process the document and then close (quit) the Word instance each time (to clear memory used by Word - but slower to load and perhaps loading/unloading Word 100 times a day will also have probs)
>
>2) use VFP to create a Word instance but then "recycle" the instance each time so that the docs are closed each run but Word stays open.
>
>Opinions?
>
>Albert
