Jump to content

Anuviel

Members
  • Content Count

    406
  • Joined

  • Last visited

Community Reputation

0 Neutral

About Anuviel

  • Rank
    member

Profile Information

  • Gender
    Not Telling

FileMaker Experience

  • Skill Level
    Intermediate
  • FM Application
    15 Advanced

Platform Environment

  • OS Platform
    Windows
  • OS Version
    Windows 7 Ultimate & Windows 10 Pro

Recent Profile Visitors

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

  1. Thank you for the reply. Yes, it seems I'll have to separate the import of records into a few tables and create some new relationships. Will look into the scripting as well. Thank you.
  2. Hello. It's been awhile since I was here last. Good to be back. I have some trouble in deciding what relationship setup to use, I am also not quite sure if I am trying to solve the issue I am having in the correct way so any input and advice is more than welcome, thank you. Setup: Standard invoicing solution for the invoicing of lessons with the following tables: Invoices, Customers, Line Items, Items and some others... Line Items table contains the following fields; Instructor_Name, Lesson_Time, Lesson_Date and some others Usage: Due to the nature of business, data is directly imported into the Line items table and a unique Line Items key is created to make connection to the Invoices table. Everything works without any issues in that respect. Question: My question is as follows: 1. Each day there are up to 9 lessons in a day, for example, lesson start times - 11, 12, 13, 14, 15, 16, 17, 18 ,19. 2. Instructors can choose how many lessons they can give 3. We have a bonus system setup: If the first three lessons are given or the last three or both, the Instructors will get a bonus, Example: Instructor works 11, 12, 13 = bonus 12, 13, 14 = no bonus All three starting times have to be worked or all three ending times have to be worked in order to get the bonus. - I have set up a self-join between Line_Items table based on the Lesson_Date and have the following calculation setup: If ( _i.LessonTime = Time ( 11 ; 0 ; 0 ) ; 1 ; 0 ) This lets me know if the time qualifies as the bonus time, I have one calculation setup for each time ( might need to do a Case calc here instead of If ) My second calculation basically sums up the first, thus resulting in a 3 if all 3 first times are worked ( last times calculation is done separately ) Sum (vLineItems_Bonus_Days_Check::_f.Bonus_Slot_11:00) + Sum (vLineItems_Bonus_Days_Check::_f.Bonus_Slot_12:00) + Sum (vLineItems_Bonus_Days_Check::_f.Bonus_Slot_13:00) So if there is a 3 in the record it means that the Instructor will receive the bonus for that day. The issue is that I do not know how to get the number of days that the instructor will get the bonus for. I would like to show/do the following: If Instructor worked 11, 12 and 13 do 1, then from Invoices table sum up the ones and get the number of times that the instructor qualified for the bonus. My described setup puts "3" into every record in the Line_Items table, even the ones where time does not qualify for the bonus. Hope the above is clear enough, please let me know if not and I'll elaborate more as best I can. Thank you kindly.
  3. Hi. Thanks for the reply. Don't have the $$$ for v.11 so will give up on it for now. Will post here if I can figure it out in a different way. Got a few ideas I am trying now. Thanks.,
  4. Hello.  I have a regular setup Items | Line Items | Invoices | Customers  Line Items and Invoices are related through an Invoice_ID field.  The database is a record of all school lessons for a particular teacher in any given month.  My Items table is actually a table of different Lesson Types. When I am entering lessons, each lesson has a start time and date.  I can see all lessons for any given teacher for the whole month on the invoice table in a portal [ portal is showing Line Items entries ].  The thing is that lessons are all in the portal [ as they should be, no issues ] one below the other, for example :  Lesson1 Date1 Lesson2 Date1 Lesson3 Date2  I would like to add a monthly view sorted by date:  Date1      Date2      Date3 Lesson1    Lesson1    Lesson1 Lesson2    Lesson2 Lesson3  I am getting stuck here, not sure how to relate the table to get what I want.  Any help is appreciated  * Please see the screenshot of my relationship graph [ attached ]  Thank you kindly., Attachment added.
  5. Hi, I just went ahead and have added the Students table on the side of Items - seems to be working ok. If I am wrong please let me know. I however ran into a new issue; One lesson can have multiple students or a single student, not sure how to set that up. Should I set a separate table where I assign students to a lesson so have something like: Month: January Teacher: X 1. LessonA 1hr StudentX 2000 2. LessonB 2hr StudentY 4000 StudentX StudentM Thanks
  6. Hello. It has been a while since I was here - good to be back. I have a following question about an invoice solution. Background: Creating an invoicing solution for myself to keep track and run statistics for English lessons, students and teachers. Before I start the following is not clear to me, I have the following items: Lessons | Students | Teachers | Schools The invoice will be monthly generated, what I am having trouble deciding on is how to relate the above... The Teacher teaches any number of lessons in a month. Each lesson is set in duration and cost so I am thinking that Lessons should be an Item table and the Teacher should be a Customer table. Easy enough to relate the two but I get confused by Students. Should a Student table be another Item table or a Customer table? For example: Month: January Teacher: X 1. LessonA 1hr StudentX 2000 2. LessonB 2hr StudentY 4000 Basically the above is what I want to have in my invoice, hope it is clear from the example. I am thinking of doing the following tables and relationships: Lessons_Item | Join_Table | Invoices | Customers | Students Lessons_Item::Item.ID = Join_Table::Item.ID Join_Table::Invoice.ID = Invoices::Invoice.ID Invoices::Customer.ID = Customers::Customer.ID I am getting lost as how to or where to insert the Students table into the above relationship, should it be on the invoice side or the customer side... Any help is greatly appreciated. Thanks & Happy New year...
  7. Thanks for the replies. I found both very helpful. I will give it some more thought before deciding if I am going to build my own or will try to hook up into an existing solution. Many thanks.,
  8. Hi all, been awhile since I've been here but it is good to be back... I am trying to figure out a simple calendar solution with your basic month, week & day views as well as with appointment functionality. As you might have guessed by now I am hitting a wall with the last part, appointments, what i am trying to do is to have multiple appointments per single day and also to display first 3 appointments on month view via portal or any other way. I got as far as displaying of the appointments but it displays all of them instead of displaying only the ones for that particular day in question... I checked around and have looked at some of the available calendar & appointment solutions but cannot figure it out, if anyone could look at my small test file and give me some pointers I would greatly appreciate it. Thank you Kindly., A-System.zip
  9. NVM, solved it. Added the following to it ">]>
  10. Yes, that would be correct. That is how I would go about it / have it work. Do note that I am new as well when it comes to FM and some people who replied to this post are experts.
  11. I have been trying to achieve this but am hitting a wall. Where exactly and how could I declare the following entity With this code <?xml version='1.0' encoding='utf-8'?> exclude-result-prefixes="fmp" version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform"> seller-id gtin isbn mfg-name mfg-part-number asin seller-sku title description main-image additional-images weight features listing-price msrp keywords product-set-id store-code category-id Thank you
  12. I would try something like this A contact table - contains all fields that are common across all contacts such as address and phone for example. A category field in the contact table which would let you select to which category the contact belongs to. A Category table/s related to contact table. The category table/s could then contain fields specific to each category. Maybe something along those lines...
  13. I am not sure but from what I learned here, it seems that you might have a data structure issue if you need that many fields in one table. There might also be some issues with speed, getting all those fields out on a layout while keeping it effective for the end-user... * Just my thoughts.
  14. Thanks., I will check. I selected to do them in FM as I do not know enough of XSLT to do it in there. Now that data is coming I will hopefully finish this project soon. Thanks for the advice. :D
  15. HM, I added that line to the xsl and now the data is coming. Was this all that had to be added? (not really getting it but am trying to...)
×
×
  • Create New...

Important Information

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