Clark,

I'm not certain, but I would think the only good reason to turn off

Rushmore optimization is if you are working with really large tables and

writing complex queries against them. I say this because one of the

features of Rushmore is to build an in-memory bitmap of matching

records. I could see on large tables where the bitmap(s) would require

too much memory, requiring VFP to do lots of extra work just to make

room for the bitmaps.

Another idea that comes to mind is if you have non-discriminating

indexes. In this case, Rushmore would choose to use the indexes but they

would be more of a burden than a help. However, a better choice would be

to drop these indexes instead.=20

Just ideas from the top of my head. I've never seen a reason to turn it

off in my experience.=20

-Chuck Urwiler, MCT, MCSD, MCDBA

http://www.eps-software.com=20

-----Original Message-----

From: White, Clark [mailto:WhiteC@jsc.mil]=20

Sent: Friday, September 13, 2002 9:23 AM

To: Multiple recipients of ProFox

Subject: VFP6: Rushmore/Network Performance

I have found a lot of interesting information on removing the deleted()

index tags to improve performance on a network.

Has anyone on the list ever tried using the NOOPTIMIZE clause to turn

Rushmore off to increase performance? If so, does this help at all?

Clark