[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference utrop1::linkworks_v3

Title:LinkWorks V3.0 Notes Conference
Notice:LNX_APO = APO issues, LINKWORKS_V3 = V3.0 issues
Moderator:tacklr.apd.dec.com::TACK_Lm::TACK_L
Created:Tue Jun 28 1994
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:2269
Total number of notes:8338

2222.0. "Distributing a Compound Object to Many Users" by TROOA::ras024p03.tro.dec.com::WORKBENCH () Thu May 08 1997 18:13

We need to distribute a compound object to 1000 users.  We also need to ensure 
that the owner of the object will be the user it gets sent to.

It is a very time consuming process to create a copy, change the owner and 
forward it to each user.

Is there a better way of doing this?

Is it possible to create a tool or compound tool, hand it over to the users, 
then run a script to change to object class to the correct compound object 
class?

Can we go into the database and change the class to a compound object?

Thanks,
Robert McGuire
T.RTitleUserPersonal
Name
DateLines
2222.1elec5.uto.dec.com::maandag_jMon May 12 1997 11:4211
Robert,

Instead of handing over a compound tool and later change the class, you can better create
a script that searches the compound obect (with a fixed nav. string) copies it to the 
desk of the current user and changes the ownership. Distribute this script to each
user.
Alternatively, if you don't want to ask the users to execute the script, you can also
override their OpenDesk() method and automatically execute the scipt. (of course you
can do this only if you don't use the LinkWorks system class Desk)

Jos