Jump to content
The site is updated on a beta version. Maintenance tasks are running so search and index may not function at this time. ×


  • Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About reelsteve

  • Rank
  1. posting a .fmp12 file here which has the environment you describe as well as the behavior you are after (I think). does this work for you or does it stick as well ? unzip it, and click to open without removing it from the folder which is where the referenced url sits. things I would look at. 1) set webviewer has reset and reload as 2 of its available actions. I always forget which is which but one of them never seems to do much and the other does. try them both (in your popup window script). 2) depending on what you find above, try keeping the webviewer source unassigned (when
  2. This post is from entry level user trying to make a quick and easy tool. There are many ways to accomplish this. Yes - the fact that the teams are identified in the teams table and then "re-entered" in the schedule creates an environment not ideal IN CERTAIN situations. You could also argue that the 2010 schedule shouldn't change if the team name changes later because it accurately reflects the game played on that day. Further, the delimited list approach has baggage and is less desirable from the perspective of component scripting (reusable code). I'm using a drop down on
  3. I read this in the initial post " can obviously link team to home team and the portal shows all home games or link it to away team and it will show all away games. How do I link it to show ALL games? " agreed - if you let this solution evolve into a league tracker, there are areas where using name would lose records. As you know, this approach can be modified to remedy the use of name, replacing with an ID structure (but remain portal filter mechanism). given the posts specific request, are you not happy with this solution ?
  4. Perhaps you missed my "or" operator and the second condition which brings both names to the equation. I did an example file which uses portal filtering approach. As far as inefficiency, I would challenge that statement given this usage. This is what portal filtering was designed to do. It is on my list to do some testing to compare "snappiness" when filtering is done thru the relationship versus the portal filter. hope this helps. TEAM_schedule.fp7.zip
  5. Key the two tables together using ID to ID. Set the relationship connector to cartesian ("X" symbol). This will now display all records in the portal. (clarifying: ur Layout uses TEAMS as the primary table. SCHEDULE is the portal on the layout). In the portal settings, select portal filtering. Filter by calculation: Schedule::away_team = teams::team_name Or Schedule::home_team = teams::team_name In portal settings, Select sort, select game date field and choose sort incremental. Enjoy. SCHEDULE (ID,DATE, TIME,LOCATION,HOME_TEAM, AWAY_TEAM)
  6. I wanted to post a quick update on this. I had been interested in AutoNavigator for a week or 2 but seeing this post last week had a dissuading effect. This morning I emailed the author with a number of questions and a request for "signs of life" having mentioned this post. It was no more than 20 minutes that I got a detailed response to all my questions. Further, my follow up questions to the reply were answered in the same timeliness. I have not purchased AutoNavigator quite yet but I wanted to drop a note for anyone who stumbles across this post that David (author) is highly responsive
  • Create New...

Important Information

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