Bug with updating related field

[Stick]

Not sure if this is a bug in FM7 or a bug within my database - I can recreate this over and over.

I have a layout that contains fields from that table (ids), related fields (codes and cost) and 1 related field from a table more than 1 table away (product name).

When I add a record to this layout, the related codes and costs get filled in correctly but the product name does not.

To make this appear I need to go to define databases (on the relationship tab), then double click on a relationship and then close the dialogues back to the layout and it magically appears!?

Any ideas?

Emma

[RalphL]

Try go to preview mode then back to browse mode. It maybe just an updating problem.

Also you may want to reconsider using related data for costs. When costs change you don't want that change to happen to odder records. Use a lookup instead.

[Stick]

That is madness - all I did was change the formatting of the related field to the same as the other fields small, black (it was big and blue - just testing the fields) and it works!

Change it back to big and blue and stops working again!

This isn't a problem for me, but any ideas why this should happen?

[Alan H]

Are you sure that the field doesn't overlap the header or footer of the page? I have had lots of update problems related to this. Also, if you are using scripts, sometimes a commit record step will fix this problem, sometimes a "Go to Field" to make sure that you have the insertion point out of a field.

(Strangely, a Go to Field [no field] step and a Commit Record step should do the same thing. However, I have found that sometimes one and sometimes the other fixes my update problems. Often a "Preview Mode"/"Browse Mode" will do it also, but sometimes not.)

[Vaughan]

Make sure that none of the relationships are defined to sort on a field that has been deleted. This has caught me before. The relationships acts all weird.

[Stick]

Alan H - I think I am going to assume that it is something like overlapping - even though it doesn't appear to be. When the font is larger, the field is still within the body - and the other occurances of it in the list are relating back fine - its just the new one that you enter.

I'm not using scripts for this. And none of the relationships are defined to sort on a field that has been deleted..

curiouser and curiouser......