Peter, Sorry, I completely forgot that I'd said I could do what you wanted - or at least point you in the right direction. That's what comes from not writing it down. DOH! Humble apologies.
I'll revamp my brain after the conference over the weekend and drop you an email with some tips. Dave Crozier -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Peter Hart Sent: 14 September 2007 15:23 To: ProFox Email List Subject: RE: Problem with AddProperty Hi David Thanks for the oGlobal suggestion it worked like a charm. In answer to your question, the properties/objects added were _Screen.AddObject('iLogo','Image') oi = _Screen.iLogo _Screen.AddObject('Title','Label') ol1 = _Screen.Title _Screen.AddObject('Description','Label') ol2 = _Screen.Description _Screen.AddObject('Motto','Label') ol3 = _Screen.Motto _Screen.AddObject('cShadow','Label') ol4 = _Screen.cShadow _Screen.AddObject('CopyRight','Label') ol5 = _Screen.CopyRight These objects are manipulated to show the Customers log etc in the centre of the application desktop. They were left alone as I have had no problems with them The properties consisted of WITH _Screen .AddProperty("nTreeViewWidth",0,1,"Holder for width of Tree menu down side") .AddProperty("dDeliveryDate",DATE(),1,"Holder for Delivery Date") .AddProperty("cStockCode","",1,"Holder for selected Stock Code") .AddProperty("cDescript","",1,"Holder for Description") .AddProperty("cCustCode","",1,"Holder for Customer Code") .AddProperty("nQtyRecvd",0,1,"Holder for Quantity Received") .AddProperty("nQtyOrdered",0,1,"Holder for Quantity Ordered") .AddProperty("nQtyShort",0,1,"Holder for Quantity Short Shipped") .AddProperty("cCustCode","",1,"Holder for Customer Code") .AddProperty("nCostOfGoods",0,1,"Holder for Cost of Goods") .AddProperty("nCOGTotal",0,1,"Holder for Cost of Goods Total") .AddProperty("nCOPTotal",0,1,"Holder for Cost of Packaging Total") .AddProperty("cColour","",1,"Holder for Colour") .AddProperty("cCustColour","",1,"Holder for Customer Colour") .AddProperty("cLeather","",1,"Holder for Leather") .AddProperty("cSample1","",1,"Holder for Sample1") .AddProperty("cSample2","",1,"Holder for Sample2") .AddProperty("cBoxed","",1,"Holder for Boxed") .AddProperty("nTradeIncBox",0,1,"Holder for Trade inc Box") .AddProperty("nRetail",0,1,"Holder for Retail Price") ENDWITH These properties are used to transfer data back to the underlying form grid. When you type the 1st letter of the Style No/Stock Code another form opens up to allow you to pick from a pick list which is populated with all codes that match the letters as they are typed and when narrowed down to a few the operator down arrows and selects a code and then on the form the data held in the code table populates the text box's allowing them to alter and add things like quantity, then the click OK and the grid in the calling form is populated. These properties pass the data from one form to the other. At first there were only five, it was as you say only after I added a few more that the error started to occur. Incidentally when the purchase order is completed it then opens an Excel sheet and populates that to produce the final P.O. I am still struggling with using the report writer to do it as the final P.O. needs to be in PDF format before it is emailed to the manufacturers in India or China. Eurico has sent me something but I haven't had time to experiment with that yet, hopefully this week end. If you have the time and wouldn't mind??? I could come over to see you. Cheers Peter P.S. How do you get the chevrons into the previously posted paragraph. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Dave Crozier Sent: 14 September 2007 13:31 To: 'ProFox Email List' Subject: RE: Problem with AddProperty >Ed, >I admit that it SHOULD work no problem, but like Peter I had an isolated >specific problem with _Screen properties which mysteriously seemed to be in >scope then out of scope which is why I recommended the suggested approach. I >know it sounds totally illogical but it was one of those problems that was >easier programmed around than finding out exactly why - and I could >reproduce it so I guess that I could revisit the code and take another look >even though it was with VFP8 not 9. >This problem only ever manifest itself when I added lots and lots of objects >to _Screen - and I mean lots as in several thousand which was for a specific >project using queuing theory. Simply transferring them to a global object >as a parent made the problem go away, with no other changes. I just wonder >how many properties Peter is adding and if it is related but it sounded >familiar. [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/[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.
