I can recall being bitten by something similar with an FRX created by another 
developer who put some code in one of the DE methods that made certain 
assumptions which turned out to not always be true. Of course this was long 
after he made the report and figuring out why it was blowing up took some time.

The other thing that comes to mind is variable scope. 

Are you getting this in the dev environment? The debugger is your friend. 

--
rk

-----Original Message-----
From: ProfoxTech [mailto:[email protected]] On Behalf Of Jack Skelley
Sent: Thursday, October 03, 2013 9:07 PM
To: [email protected]
Subject: VFP9: Very Weird Report Behavior

Good Evening:
At wits end on this one...
I have a prg where I create a cursor to populate a report. Works fine from the 
prg.
I then take that same code and copy it to a method in a form and the when the 
report runs from the form I get a variable not found error. That variable that 
is not found was used in the same cursor name for a previous report. After the 
report runs in the first report the cursor is closed.
The report that errors has never had that variable in it. The other report that 
has the variable not found in the second report runs fine. I have looked for 
the variable in the frx and it does not exist.
Even when I create the variable on the second report it still reports variable 
not found.
What am I missing? Even when I create a new report with 1 field from the cursor 
on it the error is the same.
Is there some clandestine dataenvironment on the form?
Thanks for any help.
Best regards,

Jack


_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: 
http://leafe.com/archives/byMID/profox/DF1EEF11E586A64FB54A97F22A8BD044228CEE93A8@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.

Reply via email to