Here is the situation:

I have a layout based on STOCKS.

On that layout there is a tabbed interface.

One of the tabs is OPTIONTRANSACTIONS in a portal.

In this portal are all the fields in the OPTIONTRANSACTIONS table.

The OPTIONS table holds: optSymbol and optExpirDate (Option Expiraton Date).

Since the expiration date is all ready in OPTIONS, I want to avoid entering it again when I make an OPTIONSTRANSACTIONS entry on the portal.

I have tried:

• Putting OPTIONS::optExpirDate on the portal.
• Setting OPTIONTRANSACTIONS::expDate = OPTIONS::optExpirDate

and I have even tried to do a lookup starting from the optsymbol.

It seems that if the record pointer is on the correct OPTIONS::optsymbol than the correct OPTIONS::optExpirDate would show up.

But it doesn't

Your thoughts?

Given that OPTIONS and OPTIONTRANSACTIONS are related back to STOCK using the same field (stockid.pk) then it would require a related record in both OPTIONS and OPTIONTRANSACTIONS to exist for any calculations to work in OPTIONTRANSACTIONS.

I'm not sure why you need OPTIONS related using the stockid.pk field, but as a wild guess did you mean to have OPTIONS as a set of standard entries when creating records in OPTIONTRANSACTIONS ??