I tried SET TABLEVALIDATE TO 0 with no improvement. However, after more trial and error and more research, I discovered the index named invno was not keyed only on invno, but invno+lineno. I created a new index on invno only, cleverly named invnoonly and boom, the query takes less than a second on VFP6 or VFP9. Odd behavior but problem solved! I do appreciate the reply Michael!
On Tue, Jan 17, 2023 at 6:12 PM MB Software Solutions, LLC < mbsoftwaresoluti...@mbsoftwaresolutions.com> wrote: > I'm just gonna throw out a WAG...... SET TABLEVALIDATE TO 0 in VFP9 and > then re-test fresh. > > On 1/17/2023 12:52 PM, Jeff Roberts wrote: > > I have a large table, about 1.5GB with an index on invno which is a char > 6. > > Files are on a file server, client machine where I am running VFP6 and > VFP9 > > is connected via gigabit ethernet. > > > > I run SELECT * FROM invoicdt WHERE invno = '989426' > > In VFP6 it takes about 6 seconds. > > In VFP9 it takes about 60 seconds. > > Anybody have any idea why it is so much slower in VFP9? > > > -- > Michael J. Babcock, MCP > Fox/VFP dev since 1997 > Developer of FabNet estimating software - mbsoftwaresolutions.com > [excessive quoting removed by server] _______________________________________________ Post Messages to: ProFox@leafe.com Subscription Maintenance: https://mail.leafe.com/mailman/listinfo/profox OT-free version of this list: https://mail.leafe.com/mailman/listinfo/profoxtech Searchable Archive: https://leafe.com/archives This message: https://leafe.com/archives/byMID/camandq8khm23jljdm-iq0wyy_ig8jje+r_6e3_eqfrmpl0y...@mail.gmail.com ** 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.
