Jump to content

Guy Smith

Members
  • Content Count

    15
  • Joined

  • Last visited

Community Reputation

0 Neutral

About Guy Smith

  • Rank
    member

Profile Information

  • Gender
    Not Telling
  1. Thank you all so much for walking me through this seemingly simple but actually quite complicated calc! It was very enlightening to see how different developers can come up with different solutions from different angles to solve the same problem. Comment: Your "Countem" file not only solved the problem, but taught me a number of processes I can use in future calculations - you rock! Best Regards to all and thanks again, Guy
  2. Vaughan: Thanks much for your response. I checked to make sure that there are no extra spaces and the problem pops up for every status type - the calc is only returning 1 for each type, regardless of how many there really are. Another field is showing the total number of status types correctly: A summary field in the body of the layout: count(LineStatus) and, on another layout, a portal is displaying all of the production lines and their status correctly. A piece of slate and some chalk is starting to sound pretty tempting right about now!
  3. AAAARRRRGH!!! I still can't get it to work! I can never get any results to be greater than 1, even though there are many facilities with multiple production lines that are active and multiple ones that are idle, etc. I even modified the calc formula from Comment to: ValueCount ( FilterValues ( List ( ProductionLines::LineStatus) ; "Active" ) ) and I put the choices (active, idle, etc.) in a value list...Still won't work. Any other ideas? Thanks, Guy
  4. Aha! That explains why my clever use of the Count() function fell flat on its face!! Thank you very much for your help on this, Comment - it exemplifies why I enjoy this community so much: People with real brains actually take the time to teach the unteachable! Best Regards, Guy
  5. Hmmm...Good point. Unfortunately, I changed it to Case( ProductionLines::LineStatus="Active" ;1; "" ), thinking it would then count all of the ones and give me what I'm looking for, but I still get just the question mark. Any ideas on how to correctly count the number of Active/undergoing maintenance/idle production lines? Thanks again.
  6. I have a bunch of different facilities that each have a (variable) number of production lines. Each production line record has a field (called "LineStatus") to indicate whether the line is active, undergoing maintenance, idle, or shut down. I need to be able to print a management report with each facility listed and how many production lines are currently active, undergoing maintenance, etc. I tried to use a calculation field: Count(Case(ProductionLines::LineStatus="Active";"")) [and so on for all LineStatus field choices], but all i get for an answer is the infamous questi
  7. LaRetta: You Rock, You Rock, You Rock!!! Despite all of my reading, it didn't sink in until you broke it down with there being two distinct steps to the Set Field step - I can't thank you enough for sharing your brain cells and making me a little smarter: I made the corrections and it works perfectly. Thanks to you, a chore that used to take over two hours each time now takes just a few seconds. Wishing you all the best in the new year! Sincerely, Guy
  8. LaRetta: Thank you VERY MUCH for your time and assistance - I'd definitely be sunk without it! I didn't realize there was a category below "Noob", but I think I'm there! :-) I tried to run the Set Field scripts and for some reason they won't put any data in the fields, so I'm sure I have something out of whack: When I try to use Set Field, I cannot get the wording to look like your example: The semi-colons refuse to show up and the closest I can get is to put in some Equals signs. When you select the Set Field script step, which options do you use? The 'Specify' button to the ri
  9. This is only my second attempt at writing a script, so please bear with me for the exceedingly high noob factor! Background: My club has some members that pay their dues annually and some that pay every month. I'm trying to build a script that will find the monthly dues payers and automatically fill in the date, reason, and amount fields in a related record. I am using two related tables called 'People' and 'Expenses'. I identified the Monthly Dues payers in the People table and allow creation of records in the Expenses table. The script that I have come up with so far proper
  10. We already have TroopMaster and it is used extensively by the ScoutMaster, but I do not have access to a Windows machine - I've got a Mac and the program doesn't run on a Mac. Thanks for the heads-up, though.
  11. You rock!!! I somehow came up with three join tables and a bunch of headaches. Your solution is MUCH cleaner and easier - thanks very much for your insight.
  12. Each scout is assigned a temporary patrol for each outing: Scout 'Joe' could be in Patrol #1 for outing A and in patrol #3 for outing B, etc.
  13. My three remaining brain cells just went AWOL trying to resolve this one: I am building a database for a Boy Scout Troop (I'm the new Treasurer) and have much of it up and running, but can't figure out how to properly relate the following: Many (dozens) of scouts attend many outings each throughout the year. Each outing has many (4-5) scout patrols attending. Each scout patrol at each outing has many scouts (8-12) in it. Many scouts (2-3 out of each group of 8-12) in each patrol buy food for their patrol. All scouts in each patrol pay their fair share of the food costs for
  14. Yep - That'll work! Thanks very much for the answer: I got so wrapped around the axle trying to adapt the database to the duplexing printer, I forgot the KISS principle! Having people like you on the forum is one of best advantages of having FMP - you rock! Thanks again, Guy
  15. I thought this would be pretty easy, but I had an extra bowl of Frosted Dingbat Flakes for breakfast! I am trying to make some simple 'Flash Cards' for my school: Each record has a question, a category, the answer, and the reference. The question and category fields need to go on the front of the flash card and the answer and reference fields need to go on the back of the card. The blank cards are set up "four to a page": Each standard 8.5" x 11" piece of paper (heavy cardstock) has perforations down the vertical and horizontal centers of the page to separate them once they are pri
×
×
  • Create New...

Important Information

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