There's a python desktop package for windows.Mike
Sent from my Sprint Samsung Galaxy S7 edge.
Original message From: Laurie Alvey
Date: 9/10/16 8:12 PM (GMT-06:00) To: profoxt...@leafe.com Subject: Re: M$
giving more support to dbf?
haven't looked at
haven't looked at Dabo, but doesn't Python mean web based apps? Can it do
desktop?
Laurie
On 10 September 2016 at 22:45, Darren wrote:
> V1.02 was first for me. Been with it ever since.
>
> -Original Message-
> From: ProfoxTech
To split a string into words you can use something like this:
n = GETWORDCOUNT(mysring)
FOR i = 1 TO n
? GETWORDNUM(mystring,i) && do something with the word
ENDFOR
Laurie
On 10 September 2016 at 16:02, Stephen Russell
wrote:
> Is there a split function in VFP to
V1.02 was first for me. Been with it ever since.
-Original Message-
From: ProfoxTech [mailto:profoxtech-boun...@leafe.com] On Behalf Of Ken
McGinnis
Sent: Sunday, 11 September 2016 6:08 AM
To: profoxt...@leafe.com
Subject: Re: M$ giving more support to dbf?
True, but change is painful or
True, but change is painful or at least it seems like it would be painful.
I, like some others on this list started with Fox back in the 1980's and
like some others on this list, I hope god will deliver a miracle and
save us. I haven't prayed yet. Maybe that would help?
Note that VFP9 SP2
On Sep 10, 2016, at 6:39 AM, Man-wai Chang wrote:
> Resurrect Visual Foxpro, please! Make it 64-bit at least! :)
Well, Paul McNett and I *tried* to do that when we created Dabo, which does
pretty much everything that VFP does, but with an open license and a future
path
Is there a split function in VFP to take every word of the string into an
array? Then you could parse each array element till done.
C# example here.
string s = FromYourTextfile;
// Split string on spaces.
// ... This will separate all the words.
string[] words =
It could be a fgets moment, or a strtofile(). The problem is that Fox
has at least three *different* solutions to string handling, depending
on whether it's FPD, VFP-old or VFP-newer, and mixing them is asking
for trouble.
Disk I/O pretty much doesn't matter any more, as everything ends up
Is it not an fgets moment ?
> On 10 Sep 2016, at 13:08, foxdev wrote:
>
> Problem with mline approach is the minimum length for memline is 8 bytes.
> Original message From: Ted Roche Date:
> 10/09/2016 21:41 (GMT+10:00) To:
Problem with mline approach is the minimum length for memline is 8 bytes.
Original message From: Ted Roche Date:
10/09/2016 21:41 (GMT+10:00) To: profoxt...@leafe.com Subject: Re: Processing
a long character string one character at a time
Hi, Joe:
Sorry,
Hi, Joe:
Sorry, but my weekend is pretty full, so I can't answer as thoroughly
as I'd like to. String functions in VFP are blazingly fast, but have
to be used correctly in ways that aren't always obvious.
CSV with carriage returns inside fields is not CSV, in my
not-so-humble opinion. ALL DBMSes
You can always write your own routine to do the job instead of relying
on APPEND FROM! I sometimes needed to do that...
On Sat, Sep 10, 2016 at 2:25 PM, Joe Yoder wrote:
> When one imports a .CSV file with carriage returns embedded in a field that
> is delimited by quotation
Resurrect Visual Foxpro, please! Make it 64-bit at least! :)
On Thu, Sep 8, 2016 at 11:16 PM, Stephen Russell wrote:
> Drivers for Access to use should help you with your foxpro files I am
> guessing.
--
.~. Might, Courage, Vision. SINCERITY!
/ v \ 64-bit Ubuntu 9.10
Just done some rough code to check out a 200,000 byte string (too painful
waiting for 2M byte string to process)
Sample below shows huge benefit in the file approach.
The only thing I can think of right now to improve it further would be to do
it in C++ or similar where you can easily treat
When one imports a .CSV file with carriage returns embedded in a field that
is delimited by quotation marks, Foxpro ignores the quotation marks and
assumes any carriage returns it finds indicate the end of a record. The
file I am working with ends up with several hundred extra (garbled) records
15 matches
Mail list logo