Robert:
I believe what he is suggesting is that you have one workstation that
uses the 4D license. All requests for printing that require the 4D
write are handled by that workstation. Essentially any computer
needing printing will create a record in the data base with the
necessary information. The workstation that is using 4D write will
continually poll for a record that tells it to create the document.
When if finds a record it uses the information in the record to
perform the task using 4D write.
This take planning, and extra code, but once done works very well. We
use this concept for many tasks.
Jody
On May 12, 2008, at 9:31 PM, Robert Broussard wrote:
>
> On May 12, 2008, at 2:11 PM, Robert Broussard wrote:
>
>> At the moment, offering 4D Write to all users (which would be
>> required with the current architecture) is cost-prohibitive. So, I
>> guess the solution is either: a) code without 4D Write somehow...
>> or b) get one 4D Write License and recode the DB so that the
>> letters are tagged for printing and another user logs in and prints
>> the letters... or c) somehow the print job is sent to another
>> workstation that can print the job.
>
> I would also like to pursue option c.
>
> How would you use 4D Write like this? Assume that 4D Write is
> always logged in via 4D Client and that another client somehow
> prints a letter using 4D Write... How?
>
> Thanks,
>
> Robert
Jody Bevan Jonoke Software Dev. Inc.
**********************************************************************
The 4D v11 SQL Roadshow - coming to a city near you!
http://www.4D.com/roadshow/index.html4th Dimension Internet Users Group (4D iNUG)
FAQ:
http://www.4d.com/support/faqnug.htmlArchive:
http://dir.gmane.org/gmane.comp.lang.inug-4d.techUnsub: mailto:
4D_Tech-Unsubscribe@...
Post: mailto:
4d_tech@...
Options:
https://lists.4d.com/mailman/listinfo/4d_tech**********************************************************************