On 03/04/2011 11:44 AM, Cathy Pountney wrote: > When I said compare the 2, I meant to actually dig into the FRX and compare > each record and each field of the before and after FRXs. In theory, adding a > field and then deleting a field SHOULD leave the FRX the same as before you > started. The only way you can confirm that is to compare the FRXs against > each other. Maybe something was changed in the first record. Maybe something > was inadvertently changed in another record. I'm not sure what you'll find > but if the reports work just fine day after day UNTIL you make a minor > change, that leads me to believe that something in the FRX is getting > changed and causing a problem. > > Cathy Pountney > > >> -----Original Message----- >> From: [email protected] [mailto:[email protected]] > On >> Behalf Of Jeff Johnson >> Sent: Friday, March 04, 2011 11:41 AM >> To: [email protected] >> Subject: Re: Strange Report Behavior >> >> Hi Cathy! I have done this many many times. I start with an frx that >> worked fine - add a field to it and it hangs on the preview. When I >> delete the field I just added, it continues the behavior. I can delete >> almost every control on the frx and it still does it. Any frx that I >> add a control to does this now. >> >> Like I mentioned to Fred, VMP creates a temporary .frx and that is what >> it previews. When it goes to delete it (normal behavior) it is now >> asking me to save it (not normal behavior). When I try to save it, it >> won't save. It just keeps coming up to ask me to save. This in turn >> doesn't allow the form to destroy and the application hangs. It almost >> seems like I can't write to the temporary folder. >> >> Jeff >> >> --------------- >> >> Jeff Johnson >> [email protected] >> (623) 582-0323 >> >> www.san-dc.com >> >> >> On 03/04/2011 09:28 AM, Cathy Pountney wrote: >>> I've heard of this but never been able to reproduce it. By any chance, > when >>> you save the report is the Printer Environment being saved. >>> >>> My suggestion is to save a backup of the FRX, change the original, > change it >>> back so it "should be" the same as when you started, then compare each > field >>> and record to the backup and see what is different. >>> >>> Cathy Pountney >>> >>>> -----Original Message----- >>>> From: [email protected] > [mailto:[email protected]] >>> On >>>> Behalf Of Jeff Johnson >>>> Sent: Thursday, March 03, 2011 7:40 PM >>>> To: [email protected] >>>> Subject: Strange Report Behavior >>>> >>>> I use VMP2005 with VFP9 SP2. I have built several applications with >>>> this combination and ran into a strange problem when I was about to >>>> deliver the app. VMP uses the init of a form for running reports. It >>>> calls a standard .frx. With this one app, I could run the report fine. >>>> I added a field and the report ran fine but when it was done, the > report >>>> came up in the design mode - which I did not know was available in the >>>> run time .exe. I deleted the field and it did the same thing. >>>> >>>> So I can have a perfectly fine .frx - add a field and it runs but tells >>>> VMP it could not process the data - delete the field and the same thing >>>> happens. I created a new .frx from scratch several times and the same >>>> thing happens. >>>> >>>> I am at a loss on this one, so if anyone has any ideas - especially you >>>> VMP gurus. >>>> >>>> -- >>>> Jeff >>>> >>>> --------------- >>>> >>>> Jeff Johnson >>>> [email protected] >>>> (623) 582-0323 >>>> >>>> www.san-dc.com >>>> >>>> Cathy: I finally got a chance to look into this. I took a good frx and the only change I made was to change the value of a label and it reproduced the bad behavior. The only difference (other than the horizontal position and value in the label) was CURPOS. CURPOS of the good report is set to T for the last record in the frx and all others are F. The CURPOS of the bad report is set to T in the first record and all others including the last record is F. I changed the first record to F and the last record to T and the report ran correctly.
I looked into what CURPOS was and didn't fully understand it. If this is causing the problem, what is setting CURPOS incorrectly? This appears to only be affecting one customer's application. Thanks! Jeff --------------- Jeff Johnson [email protected] (623) 582-0323 www.san-dc.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.
