Tim

>If he changed the index and things started going slower, than it's pretty
>logical that the searches, etc. are not using available indexes. With
>Locates, for example, you have to specify the loCaseInsensitive switch to
>match a case-insensitive index.

OK so if he had loCaseInsensitive in the .Locate and he took it out would that solve the problem?

Roy Lambert [Team Elevate]

Roy,

<< OK so if he had loCaseInsensitive in the .Locate and he took it out would
that solve the problem? >>

I don't know for sure since I have no idea what his tables or indexes even
look like.  I'm just speculating at this point, and don't even know if he's
using Locate.

--
Tim Young
Elevate Software
www.elevatesoft.com

Tim

>I don't know for sure since I have no idea what his tables or indexes even
>look like. I'm just speculating at this point, and don't even know if he's
>using Locate.

Whew. Same as me then. I was getting a bit concerned there.

Francisco can you post table structures and code please.

Roy Lambert [Team Elevate]

Tim

Of course, i can prepare an unit in that you can see the problem but i must prepare it.

When i prepare i post to you, ok?

Thank you

Francisco


Post to the binaries. 1) that guarantees it gets round my anti-spam measures and 2) Tim and others can have a look.

Roy Lambert [Team Elevate]

Francisco


I've put the solution in the binaries.

Roy Lambert