Desmond - I'm buried with stuff here at work at the moment - so will
make this quick. 

Re:PageFrames & "On the Fly". I meant that after you do the conversion -
then you could write a program to open up the generated Screens - by
doing Use Screenname.scx and doing some kinda data manipulation. So -
not quite on the Fly - but, after the Fly...

-K-

-----Original Message-----
From: ProfoxTech [mailto:[email protected]] On Behalf Of
Desmond Lloyd
Sent: Wednesday, October 24, 2012 11:08 AM
To: [email protected]
Subject: Re: FoxPro for Windows: 64-bit Machines

Nothing per se,  there primarily called as validate procedures for
various fields.  Not always consistently used (I was involved in the
original project).

Did a "Conversion" on the original FP:W26 project and it created the
page frames.  So I could edit the screen dataabase and remove the
reference to  the pagef frame on the fly?

Regards,
Desmond




On 24 October 2012 09:56, Kurt Wendt <[email protected]> wrote:
> Hey Desmond,
>
> Hey - what's wrong with a BIG Arse Procedure file? If you compile your
> App eventually as an EXE - does it matter that the Proc file is Big?
>
> Just curious - what's the deal with the PageFrames? R U saying that in
> your old FPW app there were NO PageFrames on your screen designs -
but,
> in trying to import your screens into VFP - it automatically created
> PageFrames and grouped controls into PageFrames???
>
> I don't know if this is any help. But, you could open up the Screen
> design files as though they are DBF files - and then programmatically
> make those changes regarding the PageFrames. Not sure if what I am
> writing makes sense to you - or if it will help - but, there you have
> it...
>
> If you think it might help - but, you need clarifications - just hit
me
> back!
>
> -K-
>
> -----Original Message-----
> From: ProfoxTech [mailto:[email protected]] On Behalf
Of
> Desmond Lloyd
> Sent: Wednesday, October 24, 2012 8:21 AM
> To: [email protected]
> Subject: Re: FoxPro for Windows: 64-bit Machines
>
> Will take a look and see....  Am dealing with the page frame issue,
> along with the original project having this huge procedure file....
>
> Thank You!
> Regards.
> Desmond
>
>
> On 24 October 2012 06:25, AndyHC <[email protected]> wrote:
>> OK I did the archive search - what I was referring to is:
>>
>> an article by Chuck Urwiler: "Convert FoxPro 2.x Apps to Visual
>> FoxPro Gradually". This appeared in the January 1998 edition of
>> FoxPro Advisor
>>
>> There may be archives available online.
>>
>> Can't remember the exact problems with pageframes (nesting?) but I
> remember
>> having to extract all the individual pages
>>
>>   AndyD  8-)#
>>
>>
>> On 24/10/2012 10:48, [email protected] wrote:
>>>
>>> No kidding huh? What is up with the pageframes?.... 8-)
>>> Sent via BlackBerry by AT&T
>>>
>>> -----Original Message-----
>>> From: AndyHC <[email protected]>
>>> Sender: "ProFox" <[email protected]>Date: Wed, 24 Oct
> 2012
>>> 07:48:06
>>> To: <[email protected]>
>>> Reply-To: ProFox Email List <[email protected]>
>>> Subject: Re: FoxPro for Windows: 64-bit Machines
>>>
>>> Try searching the archives for an article on 'converting to VFP
>>> gradually' - and watch out for those pageframes!
>>>
>>>     AndyD  8-)#
>>>
>>> On 23/10/2012 20:02, Desmond Lloyd wrote:
>>>>
>>>> That's the general feeling I am getting....  Go to VFP.  Especially
>>>> with those odd issues.  A conversion has pretty much been needed
now
>>>> for several years...
>>>>
>>>> Regards,
>>>> Desmond
>>>>
>>>>
>>>>
>>>>
>>> <snip>
>>
>>
>>
[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/289ea162f5642645b5cf64d624c66a140e260...@us-ny-mail-002.waitex.net
** 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