Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Io performance
Message
From
07/02/2008 00:58:31
Dragan Nedeljkovich (Online)
Now officially retired
Zrenjanin, Serbia
 
 
To
06/02/2008 23:30:27
General information
Forum:
Visual FoxPro
Category:
Other
Title:
Environment versions
Visual FoxPro:
VFP 9 SP2
OS:
Windows XP SP2
Database:
Visual FoxPro
Miscellaneous
Thread ID:
01290048
Message ID:
01290300
Views:
15
>>I think bypassing the memo fields is going to be the way, do the read fill in the table with the important fields along with numeric byte locations to the original data files, then do all the matching and sorting, and at the point of export back to text file read directly from the original files. it'll be the same effect as if
>>I had the memo field but with a little more code to avoid foxpro handling that part of the data.
>>
>>Thanks for the suggestions, if I do find a good way around this I'll report back.
>
>Pumping out differently is the thing I want to try - as the dump to text is fast enough that can be a fallback.

I used a technique like that once - to sort records that couldn't be indexed or sorted otherwise because there wasn't room on the disk :). So I had a narrower version of the table (but covering the whole year) as a simple sequential but sorted, i.e. a textfile, and then had an indexed table with just keys and offsets into the first record of any item in that textfile. The reports which were coming out of that were blazingly fast.

That was in VAX Cobol and VAX Basic, winter '87-88 :).

back to same old

the first online autobiography, unfinished by design
What, me reckless? I'm full of recks!
Balkans, eh? Count them.
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform