MB Software Solutions, LLC wrote: > Rick Schummer wrote: >>>> But I'm not trying to hardcode it one way or the other...I want to know >> why the VFP app/report is NOT respecting the Windows default setting for >> that printer?<< >> >> That is what Peter is trying to tell you. You need to ensure it is not coded >> in the FRX. Make sure it is removed from the EXPR column. > > > Aaah...so get rid of the COLOR= line? Ok...will do. >
That fixed it!! Thanks, guys! Now I'll have to go and manually review all of the reports I guess for this. Sounds like a job for code to open us the FRX files and identify where there's a COLOR= setting. In all my years with VFP (10), I never had this issue pop-up before. I recall years ago I had a project hook that would remove the TAG, TAG2, and EXPR values from the FRX files. Sounds like I need to apply that here at the day-job too. Can you think of a reason why I would NOT want to blank out those report file columns??? -- Mike Babcock, MCP MB Software Solutions, LLC President, Chief Software Architect http://mbsoftwaresolutions.com http://fabmate.com http://twitter.com/mbabcock16 _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/[email protected] ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
