Mike, As Woody says ... leave well alone.

I wrote a system once where I added a timer to _VFP and it ran like a total dog. I guess the timer events were screwing up the VFP event loop. Once I attached it to _Screen the problems all went away. Never ever used _VFP as a Holding object ever since.

Dave Crozier Software Development Manager Flexipol Packaging Ltd.

--------------------------------------------------------------- This communication and the information it contains is intended for the person or organisation to whom it is addressed. Its contents are confidential and may be protected in law. If you have received this e-mail in error you must not copy, distribute or take any action in reliance on it. Unauthorised use, copying or disclosure of any of it may be unlawful. If you have received this message in error, please notify us immediately by telephone or email.

Flexipol Packaging Ltd. has taken every reasonable precaution to minimise the risk of virus transmission through email and therefore any files sent via e-mail will have been checked for known viruses. However, you are advised to run your own virus check before opening any attachments received as Flexipol Packaging Ltd will not in any event accept any liability whatsoever once an e-mail and/or any attachment is received.

It is the responsibility of the recipient to ensure that they have adequate virus protection.

Flexipol Packaging Ltd. Unit 14 Bentwood Road Carrs Industrial Estate Haslingden Rossendale Lancashire BB4 5HH

Tel:01706-222792 Fax: 01706-224683 www.Flexipol.co.uk ---------------------------------------------------------------

Terms & Conditions:

Notwithstanding delivery and the passing of risk in the goods, the property in the goods shall not pass to the buyer until the seller Flexipol Packaging Ltd. ("The Company") has received in cash or cleared funds payment in full of the price of the goods and all other goods agreed to be sold by the seller to the buyer for which payment is then due. Until such time as the property in the goods passes to the buyer, the buyer shall hold the goods as the seller's fiduciary agent and bailee and keep the goods separate from those of the buyer and third parties and properly stored protected and insured and identified as the seller's property but shall be entitled to resell or use the goods in the ordinary course of its business. Until such time as the property in the goods passes to the buyer the seller shall be entitled at any time

-----Original Message----- From: ProFox profox-bounces@leafe.com On Behalf Of Jürgen Wondzinski Sent: 19 March 2018 21:38 To: 'ProFox Email List' profox@leafe.com Subject: AW: _VFP vs _SCREEN

Think of _VFP as "the engine" and _SCREEN as the "visual representation". Don't fiddle with the engine!

wOOdy

-----Ursprüngliche Nachricht----- Von: ProFox profox-bounces@leafe.com Im Auftrag von mbsoftwaresolutions@mbsoftwaresolutions.com Gesendet: Montag, 19. März 2018 21:21 An: ProFox profox@leafe.com Betreff: _VFP vs _SCREEN

(I checked the ProFox archive but searching for _VFP _SCREEN (with underscore, with underscored escaped, and without underscore) did not turn up any matches or at least the ones applicable). I know we've discussed this somewhere in the past but could not find the reference.)

I was adding another "global" application attribute for a signal flag for later code to reference, and I realized I've always used the _SCREEN object. Would seem more logical to reference the _VFP object. Your thoughts on this design decision?

tia, --Michael

[excessive quoting removed by server]

_______________________________________________ Post Messages to: ProFox@leafe.com 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/019901d3bfca$8a4d7f30$9ee87d90$@wondz... ** 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.

On 2018-03-20 08:41, Ted Roche wrote:

On Mon, Mar 19, 2018 at 4:21 PM, mbsoftwaresolutions@mbsoftwaresolutions.com wrote:

...

I was adding another "global" application attribute for a signal flag for later code to reference, and I realized I've always used the _SCREEN object. Would seem more logical to reference the _VFP object. Your thoughts on this design decision?

If you have more than one GLOBAL application attributes, why not keep them in a GLOBAL object? All sorts of functions can be built in: push, pop, load from an INI file, persist to a database, store universal application settings, manage user settings, etc...

I do actually have a custom global object (oUtils)...and honestly I'm rethinking now why I didn't attach them to that instead of _screen. My first guess is that this was due to INI values being read in at startup BEFORE the oUtils global object was created.