>>>Thanks George,
>>>That looks like a winner. I know little about setting the registry; how would you set that up in code for run-time? We want the user to see only black at run-time & don't want to go to each machine to make the setting.
>>>Thanks again
>>
>>Hi Bill,
>>
>>I'd first find out what the setting would be. Probably, "RGB(0,0,0,255,255,255), Auto, Auto" for the EditorKeywordColor and EditorCommentColor entries. Be sure to check this, however. Since the entries are strings, the registry class that ships with VFP can do the job of writing these. Once the new data is written, call SYS(3056) so the VFP updates the settings.
>>
>>Of course, once this is done, simply checking these values will be all that's necessary.
>>
>>hth,
>Hi George,
>The fellow that brought this syntax coloring issue to me found something that might be of interest to others. He found that if he adds the following to his run-time .EXE:
>SET RESOURCE OFF
>MODI FILE test.txt && this is the file displayed to the client
>SET RESOURCE ON
>then, it seems, syntax coloring is set off. MODI COMM doesn't work in this approach. He's doing it this way, but I'm not sure it's a reliable solution. I am going to try out the registry approach just in case it comes back and bites us again<g>.
>Thanks to all for the help.

Hmm, it works that way in development too. That's odd because I can't find what could be causing this, since the resource file doesn't seem to contain these settings. Then again, with a portable Rosetta Stone and Can-Opener figuring out what's in the resource file is a bit of a shot in the dark.< g >