Jump to content

gfr92y

Members
  • Content Count

    20
  • Joined

  • Last visited

Community Reputation

0 Neutral

About gfr92y

  • Rank
    member

Profile Information

  • Title
    Sales Rep
  • Industry
    Staffing

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. I apologize for introducing unnecessary confusion in my last post. (Once I am finished answering your questions, I will go back and revise/delete heavily.) A customer can have any number of sales reps assigned to it; No, a customer can only have one sales rep assigned to it. A sales rep is assigned to only one customer; No, a sales rep is assigned to either 10, 11, or 12 customers. A sales rep can make any number of calls; Yes, a sales rep may call a customer as many times as they like. A call is made by one sales rep only. Yes. It is rare that two sales reps would participate in a call. I believe you when you say Max( CallReports:CallDates ) will work. Why it will work escapes me, but isn’t that to be expected; at least initially. I will create a table: Customers:CustomersName, SalesReps:SalesRepsName, CallReports:CallDate, and LastCallDate , a new calculated field: Max(CallReports:CallDate). I still do not know how the Max function will distinguish between DowChemical’s Call Dates and ExxonMobil’s Call Dates, but I will not let that prevent me from implementing your solution, if only on faith! …and that is OK! Thanks I appreciate your two closing comments. The good news is that I have not really overlooked these issues. They are not within your field of view, which I intentionally limited so we would not trouble ourselves with the rest of the mess I created.
  2. I have 116 customers each with its own sales rep and 11 sales reps each with 10-12 customers and are responsible to "call" (i.e., visit, call, or email) each customer 4-5 times per month. How does Max ( CallReport::CallDate ) know to calculate the maximum value of each Customers' CallDates individually and then populate the LAST CALL DATE field with the maximum value by customer? Sorry if I did not make this intent clear originally.
  3. CUSTOMERS - A table of customers where each CustomerIdNumber is an auto serial number SALESREPS - A table of sales reps such that: Each SalesRep-to-Customer relationship is one-to-oneEach ContactIdNumber is the concatenation of the CustomerIdNumber, a hyphen, and the auto serial number generated when the sales rep was entered into the SALESREPS tableCALLREPORTS - A table of call reports such that: Each CallReport-to-SalesRep relationship is one-to-oneEach CallReportIdNumber is the concatenation of the ContactIdNumber, a hyphen, and the auto serial number generated when the call report was entered into the CALLREPORTS tablePlease let me know if any other additional information might be helpful. Thanks for your assistance. Joe
  4. I feel like I should know how to do this, but I keep going around in circles. (I have tried to demonstrate what I am trying to do below.) Simply put, I want to populate the field Last Call Date with the date of the last sales call, i.e., Call Date, for each company. (I think I am OK on the sorting afterwards.) Two more things... I need the values in the Last Call Date field to remain unchanged when the data is not sorted, andI can update the Last Call Date when needed. However, it would be nice if it updated itself anytime a more recent Call Date was entered. I would appreciate any assistance! Thanks. Joe
  5. Lee, Thanks. Comment, OMG! I am speechless. Great! Terrific! Thank you! Well, almost speechless.
  6. Comment, I am not familiar with the three icons circled below. Could you please tell me what they signify and how you caused them to be visible? Thanks!
  7. WOW! I can't wait to dissect it and learn your secrets! Thanks! I will let you know how it goes. Joe
  8. I have a portal that I will call LIST OF CUSTOMERS. (Photos #1 & 2) My desire is to type the first few letters of a company's name in the global field CallReport::ChooseCustomer and click on a red square button (Photo #4) to populate the portal LIST OF CUSTOMERS with an alpha-sort of my customers' names starting with Customer2::CustomerName >= CallReport::ChooseCustomer at the top and ending with Zywux on the bottom. Everything works PERFECT except the portal does not refresh such that Customer2::CustomerName >= CallReport::ChooseCustomer is listed in the first row of the portal no matter how many times I click on the red square button! (The top-left red arrows on Photo #3 signify repeated attempts to refresh the portal.) However, if I first click on any field, for example, in the field Additional Information shown on the right half of Photo #3, then I need only click on the red square button once for the portal to refresh and list the customer name satisfying Customer2::CustomerName >= CallReport::ChooseCustomer in the first row as desired. I would be grateful if someone can tell me how to changing my programming such that after typing the first 3 or 4 letters of the company's name in the global field CallReport::ChooseCustomer I could then click on the red square button causing the portal to refresh and produce the desired outcome. That said, it would be really cool if I could type "K" and K-Line, the first "K" company would be in the first row; type "L" and Kline would now occupy the first row; type "O" and Kloke would grace the first row. However, if the it too complicated for me to understand, using the little red square button is just fine. Thank you for any assistance you could provide me. Sincerely, Joe
  9. When I Searched for 'refresh' in Topics, I Found 2,448 results. When I Searched for 'portals' in Topics, I Found 7,185 results. When I Searched for 'portals refresh' in Topics, I Found 9,505 results. Clearly the third search is "portals" U "refresh" in Topics. How do I perform the search "portals" ∩ "refresh" in Topics? More specifically, how do I perform the search "portals" ∩ "refresh" in the sub-forum FileMaker 13 General Discussion only? Thanks!
  10. ​I had wondered if I should mention why I was asking the question and before making a thoughtful decision, I was off thinking about something else. Why... Before my relationship graph looked as neat and orderly as it does, it was a web of duplicate table occurrences. One had 4 the other two had five plus there were some related and unrelated table occurrences present as well. Knowing that most of the table occurrences were not serving any useful purpose, I went layout-by-layout and view-by-view to determine which table occurrences had field in each layout and view. After identifying those that did not have any fields in any layouts or views, I deleted them. I then consolidated those I could and deleted those serving no purpose. After I completed the project, I came up with the idea of asking my question; in other words, was there a better way to do what I did "manually"? Thanks for asking! Joe
  11. LaRetta, comment, and Fitch, A big thank you very much to each of you for sharing your knowledge and insight! My plan forward is to try each of your suggestions regardless of any duplication of effort hoping to be the benefactor of any serendipitous knowledge I might stumble across. Sincerely, Joe
  12. ​Fitch, Thanks for the concern! I am glad to say the relationship graph is constructed from three tables: CUSTOMERS, CONTACTS and CALLREPORTS. However, I do not think I have anything close to an optimal database design. I also know I tried to implement some functionality that is not functioning as I want it to and I am sure it is directly related to my lack of experience and know-how. That said, I do not want to impose on or burden others. Thanks, again! Joe
  13. ​Thank you for raising that point! If I understood you correctly and considering I know the specific table occurrence whose records are shown on each of the 24 layouts, I think my question should have been: Without having to go layout-to-layout, is it possible to easily identify which layouts each table occurrence had fields in? Thanks, again!
×

Important Information

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