Jump to content

badna

Newbies
  • Posts

    2
  • Joined

  • Last visited

badna's Achievements

Newbie

Newbie (1/14)

  • First Post
  • Conversation Starter
  • Week One Done
  • One Month Later
  • One Year In

Recent Badges

0

Reputation

  1. /headdesk. That fixed it! Thanks so much, I nearly went cross-eyed trying to figure it out yesterday! I had made the portal fields before I established the filter relationship (and the duplicate table). 5 second fixes are my favorite.
  2. I have a portal on a layout which is filtered by a drop-down list immediately above it, yet, when filtered, displays multiples of the same record. The filtering menu appears to do SOMETHING, as selecting an option alters the portal. Currently the portal is displaying the appropriate amount of records; the problem is that the portal only ever displays one record, and instead of displaying the appropriate records, displays the same record repeatedly. Pictures are below. Thank you so much in advance for your help! I have a decent understanding of SQL, relationship and database structure, though no formal training. I am computer-science acquainted, however, and understand scripting. [color:green]Background information: This is a financial aid add-on to a school admissions database. The relevant tables are admissionstest, which holds "Student Number"(pk)/student information and FinancialAidApp, which is connected to admissionstest via the field "Student ID". For the filter portal, I have also created another instance of FinancialAidApp, Year Filtered FinAidApp. This is linked to a global g_year in the parent table.(admissions test) In the layout itself, the drop-down list is tied to the field admissionstest::g_year and the portal is tied to the table Year Filtered FinAidApp Pictures attached:
×
×
  • Create New...

Important Information

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