Wrong Search Result

[damon_albran]

Hello,

I am using FM7 Server(v3) on windows 2000 server, with several clients running FM Pro 7 on WinXP.

I am facing a very strange problem, when we search the calculation fields (cannot indexed), it always return the wrong result.

However, this problem only exist for those users login name other than "admin", if we use the "admin" account login and perform the same search, it did not have such problem.

I believe the problem mainly coming from the Filemaker Server, because when we stop the server and open the file directly as single user mode. It did not obtain the same error at all.

Does anyone know how to solve this problem?

Thanks in advance!

Damon

[Vaughan]

Would you care to tell us: what was searched for; what the result was; why you consider this wrong; and what you believe is the right result.

How does the faulty account differ from the admin account, specifically with regard to any record level access restrictions that may be defined.

[Lee Smith]

I agree with vaughan,

We do not have enough information to help you much. It may help us to know what kind of field are you searching. Tell us what the Define Field info is.

Is this a date, text, number container field. Is it tied to a relationship, is in a portal, etc.?

HTH

Lee

[damon_albran]

Sorry for lack of information provided, here are the sample :

In the table, there is a field "outstanding qty" which is a calculation cannot be indexed because it is calculate with related field.

For example, the table contains 5 rows of record like below :

O/S Qty

----------------

100

200

0

0

500

When I search ">0", it returned also the 0 record. When I search "=0", it return other records such as 500, 200. Anyway, the result is not correct.

Actually, I used the recover function and recovered the file, now it works fine again. I believe it is because the file is damaged before, maybe the server was not shut down properly.

Thanks for your help and good luck to you all!

Damon

[Lee Smith]

Hi Damon,

The good news is: You figured out your problem.

The bad news is: You figured out your problem.

The improper closing of a file certainly can cause corruption. That is why, it is wise to have a good back up procedure in place.

In any event, it is not wise to continue to use files that you suspect may have corruption, or that you have had to use the Recovery Function on. That is, unless you want to gamble with your data.

The Recovery Function is there to help you retrieve data from files that have failed. Once a File has been Recovered, you should revert back to a clean backup, and import the data into it.

There has been plenty of discussions about corrupted files, recovered files, the Recovery Function, backup procedures, etc., in the Forums. Just do a search for Recover and Corruption and you should get plenty of reading.

HTH

Lee

[Amanal]

I am not going to be a huge help - but I hope that I can point you in the right direction.

I just had an issue finding the fields that start with say the letter "A". To do this the search text is ==A*

Now from what I understand the need to find all zeros would need a search of ==0* for a text field and/or ==0 if the field is numeric.

Hope that helps.