"guy" <guy@discussions.microsoft.com> wrote in message
news:E76999CE-EE94-4087-A28D-BCAA97D6D7F5@microsoft.com...
> why if i do a select on ablock of text (in vs2003) when i do a
> find/replace
> is find next and replace disabled? replace all is there but i may well not
> want to do that?
> if i pick any of the other 'search' options replace and find next are
> enabled.
> why?
>
> guy

"Terry Burns" wrote:

> Good Question.
>
> I suspect the logic was that instances of the item you want to replace
> should be searched for whever they are with an option to selectively
> replace. Whereas it would make less sense ( or may do ) and is less likely
> to be a requirement to only replace this within the selection. Nevertheless,
> you do have a point, perhaps they should have made this optional. I suspect
> it's a concious design feature. !
>
> --
> Terry Burns
> http://TrainingOn.net
>
>
>
>
>
> "guy" <guy@discussions.microsoft.com> wrote in message
> news:E76999CE-EE94-4087-A28D-BCAA97D6D7F5@microsoft.com...
> > why if i do a select on ablock of text (in vs2003) when i do a
> > find/replace
> > is find next and replace disabled? replace all is there but i may well not
> > want to do that?
> > if i pick any of the other 'search' options replace and find next are
> > enabled.
> > why?
> >
> > guy
>
>