If it is the last row then the button will always be there even if there is no record IF you have in the relational graph to 'allow creation of related records' in that portal. There are tricks to make it disappear conditionally depending upon your FM version.
No, that is not the issue.
I have 5 portal rows in a record that I can't delete. See post.
Only in this particular record, on other records I can delete portal rows without any problem.
I think the data are corrupted.
How to fix this I don't know.
When you say that "Only on this particular record, on other records I can delete portal rows...", are we talking about a single layout and the same portal in each case? There's a setting in Portal Setup... that allows the deletion of portal records. If you are dealing with two different layouts here, one layout may have this option selected for its portal and the other may not have it selected. (And scripts/script triggers can take you to layouts that look like the same layout, but aren't so check carefully here.)
There have also been reports of problems where delete portal row sometimes fails on Mac systems though I haven't ever seen a problem here on my Windows XP system nor on a client's.
For More Information see: Delete portal row issue
This is one of many acknowledged bugs that can be found in the Known Bug List here in the Report an Issue section of the forum.
It can also be downloaded as a database file from: http://www.4shared.com/file/8orL8apk/FMP_Bugs.html
If its not what Phil suggested about the delete setting of the relationship.
What is the exact performance of the button make sure that if you copied the button from a previous layout that it is set to delete from the correct table.
yes is the same layout and I'm on Mac and yes, I think I've hit the bug. :(
BTW - Restarting FM Pro Advanced Client solve the issue.
My sys info if any help x debug:
FM Pro server 22.214.171.1249 on MAC OS X Server 10.6.7
Client where I had the portal issue
FM Pro Advanced 11.0V3 on MAc OS 10.6.7
Make sure that you read the link I provided. As I recall, the posters there discuss several work arounds that they have tried.
yes, I'm looking into it. Thanks x your help.