Jump to content
Sign in to follow this  
rdhaden

Correct # of portal rows, incorrect record though

Recommended Posts

I have an FM7 file I'm trying to convert from 2 FM6, turning 2 files into 2 tables in one file. I have 2 tables, PayrollEmployees and PayrollLineItems. I have a self-join relationship called InFoundSet, cOne (of PayrollLineItems, a constant = 1) matched to boolInFoundSet (a number field toggled by script between 1 and 0)

so the InFoundSet relationship is cOne = boolInFoundSet, both fields from the PayrollLineItems table.

On a layout in the context of PayrollLineItems, I have a portal showing records from InFoundSet. There are 2 fields in a portal row, InFoundSet::cdEventDate and InFoundSet::ctEventName. This portal seems to show the correct number of rows (i.e. as many portal rows as there are records in PayrollLineItems with boolInFoundSet = 1), but they all show the cdEventDate and ctEventName of the first matching record. The fields are one pixel below and one pixel to the right of the top left corner of the portal.

Can anybody see what I'm doing wrong?

Share this post


Link to post
Share on other sites

Duplicate rows usually implies the portal fields are not using the same relationship as the portal.

Share this post


Link to post
Share on other sites

Can you attach a stripped-down copy of the file?

Share this post


Link to post
Share on other sites

In trying to strip it down for you, I think I figured out where the problem is. It's in my field definitions for cdEventDate and ctEventName. I think I need to find some instructional reading on what the heck context means in field definitions. Thanks for the help.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  

×

Important Information

By using this site, you agree to our Terms of Use.