Ok, I thought I had it working, but not yet. I put a messagebox() in the Run Expression on Entry and a function to reset the work area on Exit.
The report worked fine, but when I removed the messagebox, I get the error again. I am not even working with the original report. I created a new test report with only one text box. There are no relations and I am working with a flat cursor with 1 record. I hate errors like this ... -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Malcolm Greene Sent: Thursday, April 21, 2011 9:06 AM To: [email protected] Subject: RE: Weird report error Kent, It sounds like the debugger/browse may be selecting a table that you think is selected and that is why your report works in these scenarios. I think something in your code (another function, a timer routine, etc) may be accidentally changing your selected table. As an experiment, can you add a function to each band of your report that explicitly selects your master table or that logs the state of your open/selected tables? Malcolm [excessive quoting removed by server] _______________________________________________ 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/64A1FE645BC149EBB48D97C6E5D0608E@LaptopW7 ** 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.
