I tried to grep for the client id under /nsr/res/* and could not find
anyhthing so I falsely assumed it was not in there. Clearly, it is as I
can see it when I run nsradmin and turn Hidden option to 'On'. My bust.

George

Darren Dunham wrote:
>
> > I just wanna be clear about this and confirm that it's not the index
> > where the id is stored, nor the res file but rather the database itself
> > since you can query for the id with mminfo, correct? In this case, since
> > the resource id is irrelevant, then there would be no need to recover an
> > older version of the nsr.res file?
>
> There have to be two copies, otherwise the one copy could never be in
> conflict with anything.
>
> One copy is associated with the saved data, and is stored in the media
> database for the savesets (visible with mminfo).
>
> The other copy is associated with the client, and is in the resource
> files for the client (visible/modifyable with nsradmin).
>
> --
> Darren Dunham                                           ddunham AT taos DOT 
> com
> Senior Technical Consultant         TAOS            http://www.taos.com/
> Got some Dr Pepper?                           San Francisco, CA bay area
>          < This line left intentionally blank to confuse you. >
>
> --
> Note: To sign off this list, send a "signoff networker" command via email
> to listserv AT listmail.temple DOT edu or visit the list's Web site at
> http://listmail.temple.edu/archives/networker.html where you can
> also view and post messages to the list.
> =*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=

--
Note: To sign off this list, send a "signoff networker" command via email
to listserv AT listmail.temple DOT edu or visit the list's Web site at
http://listmail.temple.edu/archives/networker.html where you can
also view and post messages to the list.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=