This worked in FM 6 but it just refuses to in FM 7.02

When I do a find on a Calculation Field, using > or < the find comes back with no matches found or the wrong results (>3 would give you 1,2,3).

Is this a new feature that I overlooked?

This application is running on FM server 7.

Is the calculated field text or number?

Originally text (worked in FM 6), then changed it to number when it did not work in 7. (did not work in either one)

Sounds like the file may be corrupted or indexing may be confused. Try setting the calc field to be unstored, closing the file, opening it, changing the storage back to indexed, then finding again. Does it help?

Thanks, I'll try that in the morning and let you know!

Note that if the field is used as a right side key for a relationship, it will break the relationship when you unstore it, until it's re-indexed.

Ok, this is starting to look like a bug in 7.02.

The field that I can not do a find on using < or > is a calculated field that references a related field.

Strange thing is this works when you take the application off the server, put it back on and you get the same thing. I made a test app with two releated files, it does the same thing.

It appears that they don't want you to use related files and are pushing to convert all your apps to tables (?).

Perhaps it's a bug with Server. It sounds very odd though. Could you possibly zip a small example for us to see?

"It appears that they don't want you to use related files and are pushing to convert all your apps to tables."

I doubt that this has anything at all to do with it. It will be helpful to provide more detail or better yet sample files.

By the way - did you in fact set both files to be mulit-user?

Thanks -Queue- & BruceR.

I'm off for the rest of the week so I may not get to play with this until Monday. I would not mind sending an example, its' just that it contains lots related files and would take awhile to make a safe version. Its' a highly customized version of ebase.

>set both files to be mulit-user?

I did not think to try that, that is a good thought, I'll give it a try.

I think it has something to do with the new way FileMaker shares or opens files now on the Server mode. Since this feature works in local mode.

I did have another problem that makes me think that it does have something to do with related table changes and the push to migrate to tables.

It was with the import of a Found Set from a related file, it would import the whole file not just the found set. Found out via FM tech support that this feature will not work in this current version and suggested to convert related files to tables.

I now have temp fix for both problems (by doing exports to fixed files or globals, but it is/was a lot of work!)

I've read that the import issue is a bug that only occurs when the file is closed. Are you saying that FM tech support told you otherwise?

You only need attach the files that relate to the problem. We'll ignore the 'file cannot be found' error for the rest.