Hello all,

I set up a portal and wanted it to work in a way where it wouldn't
create a new blank portal row below the one you were currently
entering. So I did the following:

1) Made the original relationship between the primary and secondary
table unable to create related records
2) Added a new instance of the secondary table and linked the related
field in the secondary table to a global variable in the primary table
3) Wrote a quickie script that a) sets the related field in the new
instance of secondary table equal to the related field in the primary
table, b) sets the related field in the new instance of the secondary
table equal to itself (to refresh), c) does a commit, d) jumps to the
last portal row, and e) sets which field to start in.

The script works, but for some reason I have to click on the script
button twice for it to work. I've put the database up here at
http://jpollock.web.wesleyan.edu/ if someone were able to take a peek
and see if I've done something wrong in the database relationship or
script.

Thanks as always to all the helpful folks who read this forum!

In article <1132941985.278518.123750 (AT) z14g2000cwz (DOT) googlegroups.com>,
jbpollock (AT) gmail (DOT) com says...
Near as I can tell, your script worked more by coincidence.

I've sent you your sample back in working form.

Couple general comments on what I did:

1) You had a relationship based on a global for the add new records.
That was unnecessary. I modified the relationship to work on the normal
keys. (All you need is two relationships... one allowed to create new
records, and one not.)

2) You must view a portal, and goto the bottom row to create a record
via a portal, you can't just set a field via the relationship... that
only works if they're are NO related records. Once a related record
exists, you just end up edititing it instead of creating a new record.

I modified your script to switch to a utility layout, create the related
record, and switch back.

I sent you the file back via email. Let me know if its doing what you
want now; as I may have mis-understood your post. Please respond via
this newsgroup.

Hope that helps.

-regards,
Dave

Dave,

It appears to me that Google's news feed to usenet might be broken, as
it shows the last update to comp.databases.filemaker to be yesterday at
8:16 AM. Actually, that's the last update time for any group that I can
see. I've tried viewing google's feed both from google's webpage and
from a separate newsreader, but it's the same issue. Fortunately, I'm
able to use Verizon's news feed instead, which works fine. Anyway,
that's all beside the point.

Thanks very much for your comments and changes to my Filemaker database!
It certainly works properly now. FYI, in terms of the way I had done
it (using the global field to define the secondary relationship, etc), I
was basically following the recommendation of various people on the
'net; it wasn't something I had come up with myself. I actually
wound up copying your method to set up another portal similarly, which
is great.

As always, I am extremely impressed with the caliber of knowledge and
willigness to assist that I've found in this group!

Cheers,
John