But - Charlie - even U admit 2 not working in VFP w/the list of tech U
mentioned!
Am curious - how long U been on here?
I go a GOOD Ways back here on the forum - joining circa 2008. But - I didn't
stumble upon this great resource until Many years into VFP ! Yeah - like me -
Steve has been
On 10/12/2017 9:20 PM, Kurt at VR-FX wrote:
Charlie - R U saying that YOU have no knowledge of VFP??
:-)
Judge for yourself of course. But I do not propagate incorrect claims
about how VFP "copies down the whole table across the network whenever
you open it" and things like that.
And I
RIP Al.
On 12-Oct-17 4:28 PM, Fred Taylor wrote:
Really sorry to hear of another one leaving our ranks. May he rest in peace.
On Oct 11, 2017 05:32, "Dave Crozier" wrote:
Fellow Profoxers,
I have just been told of some unfortunate news regarding our colleague
Allen
Hi Tracy,
That is getting seriously technical :-) I'll see how it goes.
John
John Weller
01380 723235
07976 393631
> -Original Message-
> From: ProfoxTech [mailto:profoxtech-boun...@leafe.com] On Behalf Of
> Tracy Pearson
> Sent: 13 October 2017 15:04
> To: profoxt...@leafe.com
>
Hi Ken,
An interesting thought! I've used it without parentheses for years and it's
never bitten me on the bum - perhaps this is the first time :-) I'll start
using the brackets.
John
John Weller
01380 723235
07976 393631
> -Original Message-
> From: ProfoxTech
Thanks Dave, I've done as you suggested. There was nothing there, not even
a space.
John
John Weller
01380 723235
07976 393631
> -Original Message-
> From: ProfoxTech [mailto:profoxtech-boun...@leafe.com] On Behalf Of
> Dave Crozier
> Sent: 13 October 2017 15:01
> To:
I've seen it fail both ways. In fact, I've seen projects fail all 3 ways.
With VFP devs only, with New language devs only and with a mix of devs from
both sides. Some failures have been more spectacular than others. And
more expensive.
I've only been involved with 1 project like that, That
On 10/13/2017 1:59 AM, Jerry Wolper wrote:
And it does make the mailing list look funny in GMail:
https://imgur.com/D7qa6Rv
Damn, I look good in shades!
Are you my long-lost twin, Vince?
-Jerry
OMG! It's like looking in a mirror! :-O
___
ThisForm.pgfIncExp.ActivePage = This.Value
ThisForm.Refresh
Probably already thought of but the proper syntax of the command is:
ThisForm.Refresh()
(ie, with parentheses)
Such code would run semi-reliably without the parens in VFP 6 but
less so in later versions. I have had a few
John,
Another way to handle this would be code in two places.
First no code here. Set the ControlSource to the ActivePage property.
Then in any control on the pages, add code to the UIENABLE event, when
lEnable is true, THIS.Parent.Refresh()
We actually added to the PageFrame subclass, during
John,
That implies that you have some code in the refresh event of the form as the
method code is working fine (As can be shown in the RaiseEvent()). Remember
that even a single space in the Refresh method effectively invalidates the
standard refresh code. It is very easy to have a single space
Thanks Dave. I've replaced the line with RaiseEvent(Thisform, "Refresh")
and it works fine. I just need to wait for it to fail again :-) I'd not
heard of RaiseEvent before, what can I expect to happen when it fails again?
I'm certain I haven't any subclassing although all my controls are
John,
Just try and use
RaiseEvent(Thisform, "Refresh")
I know it shouldn't cause any problem but it will allow you to trace into it.
Sure you haven't got any form subclassing code somewhere?
Dave
-Original Message-
From: ProFox [mailto:profox-boun...@leafe.com] On Behalf Of
I have been dragged out of retirement to write a simple accounts package for
a local charity and am realising how much I have forgotten.
The main data entry screen has the usual clutch of controls - a grid,
textboxes, combos, etc. All the controls are on the form and as I set each
one up I run
14 matches
Mail list logo