I just caught a funny little glitch after an hour of pulling my hair out.

In my FM7 database I have a relationship with a global on the left and a number on the right. The global is always 1 and the number is either 0 or 1. Since globals can't be indexed the relationship appears as broken on the TOG, but as we all know, this doesn't matter for glabals -- they can be used as the LHS of a relationship and it still works.

Except that it doesn't work as far as FX is concerned. I have a portal based on this relationship. Looks fine on my FM layout, but FX always returns an empty result for this field in my browser window, as if there were no related records.

So I switched the global to an auto-entering number field that enters 1 at the record's creation. Now it can be indexed, and it works in FM and FX.

Has anyone else come across this?

Hope this helps.

Dan

Dan,

FMSA uses a different syntax to access Global fields:

table-name::field-name.global

This is perhaps causing a problem with FX accessing Global fields.

Good Luck.

Garry

Howdy! Also, I think I remember a Knight/FMwebschool post about there being a FM7 version of FX now, too. Maybe they've made adjustments to fx.php to account for that.

--ST