Joe,
Wouldn't '$GROUP$ like ("100012;" + "%")' depend on "100012;" being the first
group on the list?
How about '$GROUP$ like ("100012;" + "%") or '$GROUP$ like ("%;100012;" + "%")'?
That would still eliminate "1100012".
Dwayne Martin,
James Madison University
---- Original message ----
>Date: Wed, 17 Sep 2008 16:09:41 -0700
>From: Joe DeSouza <[EMAIL PROTECTED]>
>Subject: Re: Similar Group Names
>To: [email protected]
>
> **
>
> Depending on how you have structured your Group ID's
> you are less likelier to get this error if you base
> your search criteria on the Group ID of the group.
> It is a good practice therefore to have a good group
> ID naming convention wherein a like search for a
> group say $GROUP$ like ("100012;" + "%") would not
> result in finding another group that has its ID say
> 1100012. Remember to include the semi colon at the
> end of the Group ID as that is how the Group ID's
> are separated in the database in the C104 column of
> the T table belonging to the User schema..
>
>
>
> Take a good look at the contents of the C104 column
> in your T table of the User schema to arrive at what
> might be the best search for you..
>
>
>
> Joe
>
> ----- Original Message ----
> From: Robert Molenda <[EMAIL PROTECTED]>
> To: [email protected]
> Sent: Wednesday, September 17, 2008 6:46:07 PM
> Subject: Re: Similar Group Names
>
> **
> Don't you just have to "love" the LIKE %<Groupname>%
> functionality?
>
> That's HD 5x for you... it is because of the LIKE
> queries...
>
> To get "around" this in the past we put a
> non-descript character in the group name which is
> getting 'duplicated' so your your example if you
> change "Quest" to "Quest." (with a period) that will
> correct (circumvent) the issue although people might
> not like it but you get what you got.
>
> HTH
> Robert
>
> On Thu, Sep 18, 2008 at 8:33 AM, Shane Buchholz
> <[EMAIL PROTECTED]> wrote:
>
> **
>
> I ran into an interesting problem today with group
> names that are similar. One group is called
> Quest, and another group has the word Request in
> it. Members of the group with Request in the name
> are seeing tickets assigned to the group called
> Quest without actually being members of the
> group. When I change the group name to have
> anything other than just Quest it works
> correctly. Has anyone seen this before, and maybe
> know the cause? I could not find anything on the
> Remedy Support site or in the ARList Archives.
> Any help would be appreciated.
>
>
>
> AR System – 6.3
> Help Desk – 5.6
>
> Windows 2003 Server SP2
> SQL 8.0
>
>
>
> Thanks,
>
>
>
> Shane Buchholz
>
> Information Security Specialist
>
> Remedy Administrator
>
> Account Services – Information Services
>
>
>
> __Platinum Sponsor: www.rmsportal.com ARSlist:
> "Where the Answers Are" html___
>
> --
> If it were not for the gutter, my mind would be
> homeless!
> __Platinum Sponsor: www.rmsportal.com ARSlist:
> "Where the Answers Are" html___
