Hi,

This file is the core of a accounting system I made a few years ago.

It was first developed in FM 6 and then translated to FM 7, so far no problem.

A few weeks ago I tried to run it over FM 8, everything works fine just for a small detail: I can't perform finds in date fields, when I try it gets a very strange error and then quits FM.

It took me some time to "isolate" the problem, because everything else works fine.

- First a supposed it was an script error, so I eliminate it (and eventually all of them).

- Then all the relationships.

- Then all the fields but one, "the" date field.

So I ended with a file (36k) containing a single field with no relation nor fields, file references or scritpt.

And the problem persists: I cant perform a find in that field.

Any ideas?

ZZ

I just had a similar "find" problem and think it's a bug in the program, but the way I solved it was by going to the definition of the date field and turned indexing off. Then doing a search on a specific date, then range. The file started working for me after that.

Don't know why the problem occured for me, but hopefully that will help you.

Peter

Thanks Peter,

But it doesn't work.

The same problem, the same message. I really want to avoid the re-writing.

Take a look at the file (is the one where I erased everything, only the date field remained) (attached)

ZZ

Error_file.zip

Can't open it, the file is asking for a password and user name.

sorry I didn't realize that.

This one doesn't have a password.

accountname: Admin

password:

Thanks again.

ZZ

Error_file.zip

OK, I don't have a reason for your problem, and noticed the same problem you did with your file, but the fix seems easy enough. "Save as" the file as a clone, no records. (I did this and then created new records, entered data into the date field and was able to search on it without trouble.)

If you have existing data, you can simply import it into your new, blank, cloned file, just use matching fields on the import and it should also work for you.

I suspect that somehow the file (internally) got corrupted and the only way to fix the problem is to have FileMaker recreate the file.

Let me know if this works for you.