It sounds like you're either in the wrong data session or the report alias is not current before running the report.
Have you explicitly selected the workarea before your REPORT FORM command? Are you using the data environment in the FRX? If so, any code in any of those methods? Do your report objects have explicit table/cursor refs (i.e. mytable1.myfield1, mytable2.myfield1)? -- rk -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Kent Belan Sent: Thursday, April 21, 2011 8:57 AM To: [email protected] Subject: RE: Weird report error Removed NOCONSOLE but still get the error. Here is a weird thing. If I step thru the code with the debugger, the report works fine. When I run the app by itself, without the debugger open, I get the error. So if I browse the table or have the debugger open or add the PREVIEW option, the report prints fine. Problem is, I don't want to do any of those options -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Richard Kaye Sent: Thursday, April 21, 2011 7:10 AM To: [email protected] Subject: RE: Weird report error What happens if you get rid of the NOCONSOLE keyword? I also have this vague recollection that VFP cares about the order of the syntax when using PRINTER PROMPT & PREVIEW. -- rk _______________________________________________ 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/DF1EEF11E586A64FB54A97F22A8BD0441923ED56DF@ACKBWDDQH1.artfact.local ** 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.
