SAY command change

I'm not sure how to explain my problem.
I have to "transform" standard SAY command in
my Clipper application to do something else
than just diplaying text. I have to transform
the string that I want to display (for example
put all of the text in uppercase).

I don't want to change every line of my
prog. and put my user function instead
of SAY command.

Any ideas?

Thanks

> It seems that no matter what method you choose, you will have to change
> every line of code where "foo" is currently displayed unformatted.

Thanks

:-((

"Libero" <zmikasek@vz.htnet.hr> wrote in message
news:cmqa2k$nq5$1@ls219.htnet.hr...
> I'm not sure how to explain my problem.
> I have to "transform" standard SAY command in
> my Clipper application to do something else
> than just diplaying text. I have to transform
> the string that I want to display (for example
> put all of the text in uppercase).
>
> I don't want to change every line of my
> prog. and put my user function instead
> of SAY command.

I would think it would be easy to search & replace "SAY foo" with "SAY
FormatFoo(foo)".

Another option would be to add a picture clause to those SAYs (e.g. for
uppercase "@!") using a constant for the picture.  Search and replace "SAY
foo" with "SAY foo PICTURE FooPicture".  Should you then change your mind,
you need only change the constant.  The first idea seems to allow for more
flexibility, especially if your formatting requirements go beyond the
capabilities of the picture clause.

It seems that no matter what method you choose, you will have to change
every line of code where "foo" is currently displayed unformatted.

--
Ray Marron

On Tue, 9 Nov 2004 09:09:42  Ray Marron <me@privacy.net> wrote
>"Libero" <zmikasek@vz.htnet.hr> wrote in message
>news:cmqa2k$nq5$1@ls219.htnet.hr... 
>
>It seems that no matter what method you choose, you will have to change
>every line of code where "foo" is currently displayed unformatted.


Not true; you can use the pre-processor:

Copy the standard header file STD.CH to MYSTD.CH

Edit the translation directives for the @..SAY command to get the result
you want.

Use the /U compiler option to compile using MYSTD.CH instead of the
built-in one.

--
Douglas Woodrow

"Douglas Woodrow" <doug@nospam.demon.co.uk> wrote in message
news:U1Tz$nEgiPkBFwvK@acuity-ltd.demon.co.uk...
> On Tue, 9 Nov 2004 09:09:42  Ray Marron <me@privacy.net> wrote 

> Not true; you can use the pre-processor:
>
> Copy the standard header file STD.CH to MYSTD.CH
>
> Edit the translation directives for the @..SAY command to get the result
> you want.
>
> Use the /U compiler option to compile using MYSTD.CH instead of the
> built-in one.

I did it that way! It works great!

Thank you once again!

Greetings from Croatia...
Zvonimir Mikasek