9 posts in this topic
Users can not view or access Calculation fields
By Miss A!
I have a layout based on a particular table with fields from a table in another file through a relationship - I have full access and hence can access and edit fields, other user with custom privileges are unable to access or edit this fields, but can create records, i have tried editing the privileges on this tables for this users but still no change - what could i be missing?
The table name is Rental_Calc, i have attached screenshot for the set privilege.
Thanks for your help!
Prospects v Customers
By Simon UK
I'm developing for a service company that has a telesales and a field sales team. They then have a service team that visits customers and services products on site.
Both prospects and customers are currently in a table called 'companies' and have a simple flag (dropdown list) to indicate the difference. Challenge is that the table has grown to 124 fields with some of the fields only relevant to either Prospects or Customers. Remarkably I have never needed to create 1:1 relationships in such a scenario but I'm thinking of doing so. Would it be advisable? I'm thinking specifically it may lead to performance improvements on list layouts with some 20,000 prospect records being loaded?
Also having not used this technique before is there a way of having the related 1:1 records in the separated tables auto create when I create a record in the main company table? I'm thinking this might be a really stupid question but I'm quite tired and just can't see it?
I look forward to your opinions.
Value List to Create new unique records
I have been requested to produce a report consisting of Employee Names, each with the single task assigned to them.
I have a large DB table ALL_TASKS where each record is a unique TASK_NUMBER, and each record has an employee assigned to it (EMPLOYEE_NM) from a value list (unique values from the field EMPLOYEE_NM). There's also a lot of other summary data assigned to tasks, like time to complete, etc. (Tasks are added sequentially all the time throughout our work day).
So far I created a new empty table for my report, REPORT_SUMMARY, where each record will be an employee name, with TASK_NUMBER and some other summarized time info alongside it. (TASK_DURATION)
I want to create a new record in this REPORT_SUMMARY table for each unique EMPLOYEE_NM from the ALL_TASKS table, and then get a record for each employee using a "Show all records" from the new table.
I've made a script to freeze the interface, call up all the records in the ALL_TASK table, sorted by TASK_NUMBER, and then I've figured out how to make a value list of unique employee names derived from the records displayed, so I have a value list where each value corresponds to a record that I want in the REPORT_SUMMARY table.
But I am stuck - how do I create the records in the new table from my Value list? Is there another method to build the records for this REPORT table without using a value list? Each employee record in the new table will have a TASK_NUMBER and TASK_DURATION beside their name.
Hope someone might have tried this sort of thing before.
seeking tutorials for TO's and TOG's
I'm just returning to FileMaker development after years away. The last time I developed in FileMaker was... version 6!!! Wow, has a lot changed, and thank goodness it has.
I'm trying to understand FileMaker database schema design. I have a decent knowledge of normalized database forms, but the concepts of having multiple Table Occurrences, and Table Occurrence Groups, are quite foreign to me. I understand what they are on the Relationship Graph, but I don't yet understand how to plan and use them while constructing my solutions.
Can you direct me to some good tutorials on these topics? I imagine I'll need to examine more than one tutorial (and sample files) in order to truly grasp the concepts, so the more the better!
General question on tables
I am writing a database to gather information on student's degree pathways. I have 4 years of intake; 2011 - 2014; the discipline - maths, arts etc - 7 choices; then the subjects they have completed or are completing. In total this is 900 fields. This tool is not for official records; it will be used to calculate which subjects certain students still need to complete. So record numbers will not be large. My question is this: should I break up the table into years? This is the way I am planning to design the file: a student will login in via IWP (moving to 14 eventually) then select a year and a discipline - this will take them to the appropriate layout, to enter their data. I do however want a lecturer to be able to find a student by their student ID (this is entered by the student) so all tables need to be relational. What would you do? Is it work breaking up the table into years of about 200 fields? Will this make the design more efficient or am I making work for myself? Thanks for your time - it's much appreciated.