Hi Victor;

I had a similar problem with a web application that printed using Crystal. The Crystal runtime would only do one report at a time, so our web app would instantiate a VB hidden form class that would manage the print (and not close until it was time to do so).

A vfp application on the server would do the trick. It would just have to look into a table to see what reports need to be printed.

Now, your big problem is some reports take longer than others to print (meaning calculate, etc. I think, not the actual printing.)

In this case, just run two copies of the vfp print server, as if it were two users. The server might run slow when both apps are processing, but this way your short report gets processed and doesn't have to wait for the long one. Things will still queue at the print server.

All the print server does is run the report (based on passed in parameters that are found in a record) and then mark the report as processed (so the other server doesn't try to run it too!)

Very much like handling web requests!

Doing multiple prints with Crystal, concurrently, might be a problem. Depends if they have fixed their automation server. It's been a while since I used it.


>That's pretty much what I'm looking for. Unfortunately, VFP can't run multi-thread without any third party software involved. Or do you???