I have a database that I'm working on with a People table. So far so good. Well, I go to try the find function, and I can't find records that I know are there. In fact, it NEVER finds anything.

I've tried finding on text fields and number fields. Nada.

I have full rights, so that isn't the problem.

I figure I'm missing something basic. Clues?

Thanks!

-Jeff

Attach a copy of your file, and let us check it out. Be sure to delete confidential, or sensitive information. You can always replace it with nonsense if necessary.

Lee

I can do that...

Is there a recommended fast way to do that?

I went and just imported the table, but then the find worked.

The DB is on a server, so I can't easily copy the file. Any tips?

-JEff

Do a Reply using the button in the Body of this Post. When your file is ready, you will see:

File Attachments: About half way down, you will see:

[color:blue]Valid file types zip, txt, pdf, bmp, gif, jpg, png, sit, mov

[color:blue]Preferred is Zipped

[color:blue]click on the [color:orange]Manage files

A second box will appear.

First select [color:blue] Browse locate your file on your hard drive

Next select [color:blue]Add When it is finished, you will see it loading if it is of any size

Click on [color:blue]Finish

You will then be able to Add Post.

HTH

Lee

Sorry, Lee, I should have been more specific.

Is there a *fast* way to send you a cleaned copy of a DB that is on a server, that is cleaned of records (except a couple of fake samples) and cleaned of usernames and passwords?

I could do it manually (And I will when I get back to work after the break) but I was wondering if there was an easier way that I didn't know of.

-Jeff

Hi Jeff,

When finds fail to locate records you know are there, that generally indicates a problem with the field index (or indexes) of the fields you are performing the find on.

Turning indexing explicitly off (the None setting, with Automatically create... disabled, in the Storage tab of the Options For Field dialog for a given field), then closing the file, re-opening it and then turning field indexing back on, will prompt a rebuild of the field's index.

While you're at it, also check the setting for Default Language for Indexing and Sorting (though that applies only to text fields, so it's unlikely to be the cause of the problem you've described). :wink2: