Greetings -

We recently converted to FM7. We are having dificulties with searches:

1) Searches on calculated fields are producing result sets of all records or none. We have a calculation integer field that produces a 1 or 0 depending on criteria, then we search for a 0 or 1 depending on what we want to find. Searching for zero produces the result of all records. Searching for a 1 produces no records. The field contains both 0 and 1 (doing a sort on the field shows both values).

2) No matter what field I choose, wildcards are not functioning. Both the * (asterisk - something there) and = (equal - empty) are producing no records found.

Any one have any clues.

Thanks In Advance.

Greetings - Found it.

The problem was when we cleaned the file references the only file reference entry we had was fmnet:/xxx.xxx.xxx.xxx/filename. When I added the file:filename reference to it, the searches on calculated fields started working.

Hope That Helps

Greetings - FYI...

I found an additional condition in which searches on calculated fields are not working.

In FileA there is a calculated field C_Banana that is bringing a field via a relationship FileB::i_Banana. When the field on the layout is C_Banana and i search for a specific value if finds nothing. When the field on the layout is FileB::i_Banana the search works correctly.

I checked the FM5.5 backup of the files before conversion and searching on C_Banana on the screen works properly. And just to make sure it was not my imagination I showed it to two individuals and they saw the same behaviour.

Hope That Helps

Greetings - FYI...

This has been verified by another FM7 user. This other user is also having a tremendous slowdown with calculated summary fields.

If information is power, how come I am not feeling more powerfull? <grin>

Enjoy!

I have experienced a similar problem in version 7, our databases are hosted over Filemaker Server 7.

When the files are local on my computer everything works perfectly, but when hosted on the server finds do not work when the field is a calculation based on a related file. The confusing part is that with some calculations it happens and with others it doesn't. It is driving me nuts!

I am developing a theory on this. Can you tell me if your files are hosted on Server 7 and could you also give me examples on the file names?

Greetings -

Our files are being hosted on a FM7 server.

When I did preliminary testing, I copied the database from the FM5.5 server directory into my local driver, converted to FM7 and checked out the results. And I experienced no problems. Imagine my suprise when I moved everything to the server.

Also, we have an incident opened with FM support. We have a file that is not pulling through calculated fields from another file. We sent them both files so they could see what was happening. No response yet.

What is your theory. At this time I am willing to try most anything. If I have to rename files and or fields I can see what I can do.

Are these files too big and cumbersome to post? That would be helpful.

Reguarding the "0" vs "1" thing... are the results a number or text?

Have you checked the File References to ensure they are pointing to the correct files and there aren't duplicate or invalid references?

Greetings Bruce -

The 0/1 is a numeric result.

I have attached the files that were mailed to the FM support group. Bellow is the text of the email.

There are two files in the relationship, co_codes.fp7 and rate_cntr_def.fp7.

"co_codes" has three relationships into "rate_cntr_def". "co_codes" is

supposed to be bringing in some calculated fields based on these

relationships. It is not happening. The three relationships are based on

calculated fields, the individual component keys, and text fields. None of

the relationships seem to bring any data into "co_codes".

The first four fields in "co_codes" that are supposed to be brought in, are

the first two fields in "rate_cntr_def". If you check out the file

definitions and relationships you will find other fields that are supposed

to be brought in from "rate_cntr_def".

FM7_20041201.zip

Greetings Queue -

The file references have been cleaned up and verified.

There is an extra space at the end of each s_State field in co_codes. Remove it or add a Trim(s_State) to your key calc and the calcs will work.

Greetings Queue - Thank you.

I added the Trim(s_State) to the key on both files.

That got it working. I inherited this database and since it was working in FM5.5 I did not know what to look for. Something new learned.

I wonder how long the FM support group will take to figure this out.

Again, thank you.

You mean 'if' they figure it out?

Greetings Queue - Oh!

Methinks I be a nice guy and let them know by email that it was solved. I will let you know if they ask for the solution.

Thank You.

Enjoy your weekend.