>>>>>This must have been asked and answered many times before, but I can't find it.
>>>>>Is there any way to prevent VFP from saving printers settings in the .frx?
>>>>>I have a written a utility that removes them, but it would be nice if they weren't there.
>>>>
>>>>Your way is the only secure one in your version.
>>>>
>>>>The only thing you can improve is to write a project hook (i guess it was introduced with V 6) that will do the job on every project compile.
>>>>For all I remember on V 6 it was wise to pack vcx's (possibly scx's) an the same place.
>>>>
>>>That's a good thought but this is an SBT application that doesn't use a project.
>>>So I have to remember to run the utility or wait till the client complains.
>>
>>The link to SBT is very strange. :)
>>
>>Without a project there is nothing that can hook on changes. :(
>>
>>OTOH if it is not compile into anything you can do the remove just before REPORT FORM in the running prog.
>
>Good thought, Lutz.
>I wonder if that would be an issue if someone else had the report in use.

If you try something like USE EXCL with an on error handler (No TRY CATCH on this version I think). Possibly you mark the frx dirty (SYS(2007) for lookup?) and run only one time. Or just look with USE SHARED to check the fields to minimize the risk