Luckily I've worked out the problems customers had with our reports. They are complaining working in the system doing everyday CRUD operations is slow when the EXE is on the network location. I might be an easy way to test test the SYS() setting.
Tracy Rick Schummer <[email protected]> wrote: >>> Looks like something I need to implement in a test build to see if I can >>> work out some reports of slow access.<< > >Slow reports is normally related to hard coded printer information with the >saved printer for the report. VFP is >searching the network for the printer and eventually times out before printing. > >Rick >White Light Computing, Inc. > >www.whitelightcomputing.com >www.swfox.net >www.rickschummer.com > > > > >_______________________________________________ >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. > >Report [OT] Abuse: >http://leafe.com/reportAbuse/[email protected] _______________________________________________ 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.
