In message <[EMAIL PROTECTED]>, MAJ
Programming <[EMAIL PROTECTED]> writes
Could all of this SETPTR stuff be in a table that's easier to maintain. I've
added such to my UD and D3 clients.
I had a similar system. All the users names were stored in a file read
at login, which contained amongst other things their default printer.
(If the login program couldn't read their details, it prompted the user
to create such a record.)
And all the printers had the relevant SETPTR command (and other stuff,
like escape sequences for landscape etc) stored in another file.
So when a user logged in, the login procedure read their default printer
from the user file, then passed that to another routine that read the
printer details from the printer file and set that up.
When you've got some 10 printers scattered round an open-plan office,
you need something like that ... especially when users have a habit of
moving too ...
Cheers,
Wol
--
Anthony W. Youngman <[EMAIL PROTECTED]>
'Yings, yow graley yin! Suz ae rikt dheu,' said the blue man, taking the
thimble. 'What *is* he?' said Magrat. 'They're gnomes,' said Nanny. The man
lowered the thimble. 'Pictsies!' Carpe Jugulum, Terry Pratchett 1998
Visit the MaVerick web-site - <http://www.maverick-dbms.org> Open Source Pick
-------
u2-users mailing list
[email protected]
To unsubscribe please visit http://listserver.u2ug.org/
