Jump to content

Search the Community

Showing results for tags 'tables'.

More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type

Community Forums

  • The New FileMaker Platform
  • Community Resources
    • Community Articles, Tips, & Techniques
    • FileMaker Marketplace Discussions
  • FileMaker Platform
    • FileMaker Interface Features
    • FileMaker Schema & Logical Functions
    • FileMaker Go for iPad and iPhone
    • FileMaker and the Internet
    • FileMaker Pro Advanced 18
    • FileMaker Pro Advanced 17
    • Legacy FileMaker Platform Discussions
  • FileMaker Server Administration
    • FileMaker Server 18
    • Zabbix Server Monitoring
    • FileMaker Server 17
    • FileMaker Cloud
    • FileMaker Custom SSL Certificates
    • oAuth and External Server Authentication
  • Brain Food
    • Security Concepts
    • The Left Brain
    • Upgrading & Migration
    • Data Analysis
    • Development Standards
    • The Separation Model
    • Relational Database Theory
    • Damaged / Corrupt File Problems
    • Bar Codes (Printer, Scanners, Software)
    • Hardware & Networking
    • OS Level Database Automation
    • Product Ideas
  • JavaScript Integration
  • FMForums Affiliates & Sponsors
  • FileMaker Classifieds
  • FM Forums Operations
  • FileMaker Friday Night Chat's Topics


There are no results to display.

There are no results to display.


  • White Papers
  • Infographics
  • Samples
  • Solutions
  • FMGo
  • Plug-Ins
  • Tutorials

Product Groups

  • Workplace Innovation Platform
  • Site Advertising
  • Development & Hosting

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start







Website URL




OS Version

Found 26 results

  1. I have a TODO list. Some tasks I want to put off until tomorrow, but have them re-appear on my TODO List the following day. I have two tables; TODAY, and TOMORROW. I can get the individual records to go to the TOMORROW table ok by just using a button and script. This operates on only one task at a time. I am having problems getting the records in the TOMORROW table to automatically come back to the TODAY table the following day. I date the records going to the TOMORROW table and have tried to use this as a criteria to send them back to the TODAY table. One problem is that there are often numerous records and not just the one that need to be sent back. I have tried a script trigger on the file so that when the file is opened, the records in TOMORROW are sent to TODAY. The problem is that there are numerous records. Any assistance is appreciated. Thanks.
  2. Hi, I believe I'm having a problem with an unidentified key concept. I hope to get pointed in the right direction. I am attempting to build an English horse racing form here in Tokyo. I import all the data from Excel and am working from a single table (I believe this might be the root of my problem). I did a few tutorials and I felt pretty comfortable with the basics. At my first attempt (and I thought it was strange at the beginning), I gave every piece of info that would appear on the form its own field. With a possible 18 horses running in a race, and 5 lines of past performances per horse, I ended up with almost 2,000 fields. I filled in each past performance line through look-ups from the race id. It was pretty cool and at the same time obviously wrong. So I bought FMP12 The Missing Manuel, and while I feel as if I am getting through the text well enough (I can build an invoice!), when I come back to my project I have been lost -- to a point of great frustration. I moved to trial and error for a few days and decided to come here. I have attached a sample form I borrowed from the Daily Race Form (and simplified it) to show what the end product would look like. I see it as a Mast Head, 18 Sub-headers (1 for each horse), and then 5 lines of past performances for each horse. To get away from 2000 fields I figured I must have multiple TOs (18?) of the single table I have, then I figured I need portals for each horse to display the 5 past performances. I've been working this angle to no avail and figured I must not have grasped a key concept. From what I've written -- is the missing concept apparent? Thanks, Paul race_form_model.pdf
  3. 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.
  4. I have 24 layouts that are populated with fields from multiple tables present in the relationship graph shown in the image below. (I realize this is not uncommon.) Is it possible to determine which layouts use each table? In other words, is it possible to identify which of the 24 layouts have fields from the table "Contacts", which of the 24 layouts have fields from the table "Contacts 3", which of the 24 layouts have fields from the table "Customers", etc.? Thanks! Joe
  5. Hi - I'm new to FMforums, but have been reading in here for some time. My challenge is a database, where I need to display some points earned by members in different categories and display their individual points so far - and finally have a tab/layout/button, where new records of points can be entered Plz find file attached. Any help will be appreciated Martin TølbøllClubPoint-vers.-2013.11.05.01.zip
  6. Is there a limit to how many fields a table should have? My solution requires the management of 6 categories. Each category has up to 34 sub-categories, although most have 9-12, and each sub-category has several items requiring data entry. This leads to 91 sub-categories and hundreds of fields requiring data entry. The records per sub-category require relationships to corresponding sub-categories that respond to the data recorded. It is like a question/answer system, so the initial question field has data entered that requires answers entered and/or available (from previous experience) in the corresponding answer table. I have been thinking that I need to have the 91sub-categories in their own tables to limit the number of fields per layout. Is this a limitation? Is there anything wrong with having loads of fields in one table? Each of the 91 sub-categories will need to be related to the entity asking the question and receiving the answer. The questions and answers will eventually be presented in a report. In the future, when the answers have been acted on, the process is redone using the same sub-categories and the latest report is used to show progress, or otherwise. I could create tables for each main category and split the one with 34 sub-categories into 3, making 8 tables populated with the fields from the sub-categories which would result in approximately 50 to 100 fields in each table.
  7. Hi, 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. Question: 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. Thank you, Simon
  8. I have a table which is related to another one. Trying to keep it simple lets say one is a table of cats (first table) which has fields for cat species, colour, weight etc. I can also record the details of when I bought the cat, price paid etc. It is linked to another table where I record all the prices of cats I can find (second table) and they're matched according to species and colour. I create a report based upon a time period using the first table and by doing a find of records which match certain criteria I wish to includewhich shows certain data for example: min price, max price, av. opening price, av. opening price. The report doesn't need a script it is simply another layout which pulls the data from certain calculations fields some of which are based upon the other table (eg a summary field). The problem is the table (first table) picks up references to any cats given away (eg $0) as part of its minimum search and I only want to include cats whose price is at least $50. Also, I wish to exclude the $0 values in the summaries of average prices in the second table. I suppose what it comes down to is how can I ensure 'summaries' never include 0 values without just excluding them from the DB altogether (I could do a find on the price field for $0 and then delete all these records).
  9. 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. thanks, jamie
  10. I have created a basic Contact-> Order-> Line Item <-Inventory database but am at a loss how to go about creating the next stage. Our company signs out equipment to its employees. Each Order can be made of multiple individual items from our inventory. This is basically your typical Invoice solution except we are not selling items, but rather signing them out. The trick is how to assign individual Inventory items to a “Kit number & category which then can be pulled up in an Order portal. Once that Kit number is pulled up in the portal, the line items automatically become populated with all the items associated with that specific Kit/category. Additionally the Order portal would also be able to pull up individual items from the Inventory which have no kit association. Items from the established kits could not be rented out individually until that particular item in the Inventory has it’s kit number association turned off / deleted. This is to allow for upgrading, fixing, or moving equipment around to other employees which may have been assigned.
  11. Hi, I would like to know if it´s possible to create memory tables within Filemaker and how. I saw in a different RAD tool the option to create memory tables. The table is kept meanwhile the program is open and dismissed after is closed. I see this as a powerful tool for complex reports and to speed processes. Maybe there is an ODBC or JDBC driver for memory tables, Server side or client side.
  12. Hi All, I would like to create a button that copies data from specific table and fields to other ones on display in my form. The context for this is that I am creating a button that copies data that has already been entered and displayed in some text merge fields. i.e., Account address (first table), and I would love to have that data copied to the location address fields (second table). See attached file. Any help would be gratefully received (Complete beginner). Cheers, Simon DB_SC_Grab- button question.tiff
  13. Hope someone can help. I have a number of related tables. Companies Company_addresses Personnel Personnel_addresses Companies relates to Personnel and Company_addresses Personnel relates to Companies and Personnel_addresses Company_addresses relates to Personnel_addresses (sort of) The intention is to have unlimited addresses for both companies and the personnel related to those companies In the companies' form layout I have a portal that shows the related personnel. This relationship is based on a company_ID key. In the companies' form layout I have a portal that shows address fields. This relationship is based on a multikey drop-down global field. In this way I can select from a value list that includes Address 1 - Street, Address 2 - Postal, Address 3 - Billing, Address 4 - Shipping, Address 5 - Other. This displays each address without requiring any more real-estate on the layout. In the personnel's form layout I also have a portal that shows address fields. It's the same concept as above but with a separate value list that includes Address 1 - Work, Address 2 - Home, Address 3 - Postal, Address 5 - Other. What I would like to achieve is an auto-enter calculation or lookup in the personnel_addresses table so that when a personnel record is added in the companies' personnel portal the address info for the company's Address 1 - Street is added to the personnel_address table as Address 1 - Work. Just thinking about this makes my head spin so I thought I may be able to lean on smarter people than me via the forum. I could put together a simple db with just this functionality if it would help. Possibly needs a script trigger on the personnel portal's fields? Any thoughts?
  14. Are there any drawbacks to creating a second occurrence of a table? I have hunted around through documentation and help and I can't find a concise discussion of what the negative impacts of it might be.
  15. I everyone, I'm brand new to the FileMaker database but have some FB experience and a newbie here. I'm well into a heavily modified starter solution for asset management and have been asked if FM will do something! What I need to do is every time a assets mileage or hours is changed in a shared field of "current hours" have it recorded in a table that can then be reported from with a time stamp for each change to the field and it's value. Could someone give me a bit of advice? Thanks always in advance, Jay
  16. Environment: Windows 7 with FileMaker Pro 14. I have a test database that I am currently making changes to. I saved the test database as a clone, so that I could test importing data back into it. the Import functions allows me to import the first table of information just fine, but it will not let me import any other tables. On any subsequent import, I can select the source table from my source file, but all of the target files are grayed out, except for the first file to which I was able to import into. What am I doing wrong? I will need to do this on a regular basis, as I will use this technique to move my changes into the live environment. Thanks, Linda
  17. 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! Miss A!
  18. I thought I understood that different table views are simply that - VIEWS into the same table, like when you establish a self-join on a key and FM creates a new view for that table. I also thought that data in a field in a table is the same data, no matter which view I am using to display it. Extending that, if I enter or change data in a field using one view, that field will reflect the change to that field in any other view. Now, I understand the concepts of filtering and lookups that might change WHAT you're viewing or HOW you're viewing - but not the DATA itself. But I have a very strange situation that sure looks like my understanding has been wrong all along. Once I saw strange behavior, I set up a test situation where the same field, viewed twice in a single layout, with one instance of the field pointing to the initial table and the other instance of the same field pointing to a different view of the same table is displaying different data! How can that be? I know I've provided no specifics here and can certainly do so, but is my basic understanding wrong? What could account for what I'm seeing? Thanks for any thoughts. - KJ (now stumped and stuck)
  19. I have a table that contains dimensional data for parts. Each record has a unique ID, but also has another field with the ID associated with the part. I have another table that I'll be storing individual inspection data on. I was wondering if it's at all possible to parse the first table, and copy over all records that have a specific part ID to the second table whenever someone starts a new inspection record. Please let me know if I need to provide any more information and/or pictures. Thank you in advance for any assistance you can offer!
  20. Hey, I have a Tab-Separated Text File which I want to import to a database that I just created in FileMaker Pro 15. The text file essentially is a log of events, for instance, one line describes an order, another line describes a payment that has been made. The problem is that I somehow need to import all these lines into different tables. I want all lines in the log file that describe a payment in a table called Payments, and all lines that describe an order in a table called Orders for example. I'm just starting out with FileMaker so forgive me if there is an obvious solution that I'm not aware of. I have a background in software development, so the only solution that I can think of is writing a small program myself that does all the parsing for me and creates separate text files that contain all the orders and payments and other events that have been logged in the file. Then I could simply import each file into the table I need all the data in. So to sum everything up, my main question is if there is a way to somehow parse the text file before importing it. I know that you can create custom scripts in FileMaker but I'm not sure if what I need to do can be done just with that. Thanks in advance, Mike
  21. I am working with a Woocommerce installation and trying to create a product form interface. Woocommerce stores product attributes as meta_key's and values. I was wondering if there was a way of linking the table to a different table which would be more manageable and easier to use. Below I have tried to illustrate the two different tables and was wondering if there was a way of linking them together allowing them both to update when information is entered. I have a feeling I might need to use global fields and calculations. However, not completely sure if it is possible. Woocommerce Table ID post_id meta_key meta_value 1 1 Field 1 Value 2 1 Field 2 Value 3 1 Field 3 Value 4 2 Field 1 Value 5 2 Field 2 Value 6 2 Field 3 Value New Table, which should populate existing Woocommerce Table ID post_id Field 1 Field 2 Field 3 1 1 Value Value Value 2 2 Value Value Value I hope this makes sense and any advice will be greatly appreciated
  22. Hi all I'm sorry if this is really obvious or the wrong place to post this, but I have been having a real frustration with FM Pro databases recently. I am editing my website databases using ODBC. As I tend to edit fields en masse, I use the "view as table" browse mode. In a lot of my columns, the fields I have contain more data than the column width will show. So I've tried adjusting the column width, but it won't let me. I've used the drag to resize function, and the right click and set column width one, but in both cases my column width remains the same. Does anyone have any ideas of what I can do to set them? I've looked through all the help info, forums and googled the problem but have got nowhere. I took a screengrab, but the arrow one didn't show up. I'm attaching the right click one. Thanks for any help.
  23. I have a database that keeps growing larger and larger (the number of fields, not the number of records). I want to reorganize before things get out of hand, but I don't know if I should create related tables for different categories of information or if there is a better solution. The main content of my records comes from an outside source, which sends me an excel sheet with applicants for the program where I work. This is all demographic information and contact information. Next, I begin analyzing applicants, and marking the applicants in various ways, creating new fields based on their qualities, status, etc. The issue is that it is becoming increasingly difficult to import the excel sheet when I receive it (on a weekly basis), because of all the fields I've added. I also have to admit that I haven't quite mastered the recurring import function, yet, but mainly because the person who sends me this file never uses the same headers, so I've been afraid to try this. Basically, it takes way too long for me to match up these records every time I want to import new records, and update the existing records, and I was thinking that I could have only the items on the excel sheet in the main table, and then have all my added fields in related tables matched by an auto-created serial number. Additionally, this would make it easier to locate fields if they are categorized in separate tables based on their specific use. I suppose the question is: Is it stupid to make related tables for the sake of field organization? If so, how can I better organize these fields to prepare for import?
  24. My first post here from a relative novice, so I apologize is this is a dumb question or one that has been covered many times. I'm starting to build a database for an academic department, to keep track of contact information, as well as publications, grants, applications, and other items associated with the different department members. Department members can be one of several different positions or "ranks," such as faculty (professors, associate professors, etc.), post-docs, grad students, staff etc. I also want to keep track of the relationships between these various department members, for example, which grad students "belong to" which faculty member. Ok, now my question: Should I keep everyone in one "Department Member" table that has a field denoting each member's position, or should I use a separate table for faculty, grad student's, post-doc's etc. My intuition tells me I should use one table for everybody, to avoid duplicating lots of contact fields. But if I do that, how would I relate grad students, for example, to professors? Would I create separate table occurrences of the Department Member table to use for each position (faculty, grad student, etc.), and relate those different table occurrences? Many thanks for advice.
  25. Not sure if this the right place but was curious about people's thoughts on specialized tables versus multi-purpose tables. For example, let's say you have a database with a number of different tables (Table_A, Table_B, Table_C, Table_D) Table_A needs to have a many-to-many relationship with Table_B, as well as with Table_C, and with Table_D so it needs a join table between each of them. In the past, I would create three different join tables, each for the specific join relationship (Join_AB, Join_AC, Join_AD). The only fields in the Join tables would be its own primary ID, Table_A's foreign ID and the foreign ID of the table being joined. What if instead of multiple join tables, you just create one join table and add a field to it that explains what relationship that particular record serves. Then in Table_A you create a global field for each kind of relationship and create table occurrences for each relationship connecting them as follows. Table A has the following records: The Join table has the following records: Therefore.... Record 1 of the Join table joins Record 1 of Table_A with Record 5 of Table_B (since <<Table_A::relationship_Table_B>> == <<Join::relationship>> ). Record 3 of the Join Table joins Record 2 of Table_A with Record 4 of Table B (since <<Table_A::relationship_Table_C>> == <<Join::relationship>> ). Is there any downside to doing this beyond losing flexibility in terms of having data in the join tables that explains each relationship? And if that becomes an issue, what if you do the following: Within the "Join" table, add some new fields: text1_Description, text1_Value, num1_Description, num1_Value, text2_Description, text2_Value, num2_Description, num2_Value So for example, in relationships between Table_A and Table_B the Join record uses text1_Value to store the "name" of the relationship. For relationships been Table_A and Table_C, tex1_Value is used to store the "team" of the relationship. ---- Any downsides to this technique? Obviously, you could get stuck having to create endless new fields in the Join table if you start needing more field values describing various relationships. So this would only make sense if you knew the Join table only needed the primary and foreign keys or if you knew that the Join table would only need a few extra fields to describe the nature of the relationships. The major upside to me (and why I'm considering this) is needing a lot fewer join tables (and therefore fewer layouts as well). In the solution I'm working on that has 30+ tables with a ton of many-to-many relationships this design seems very attractive. Or perhaps I am just shuffling complexity around? Hope my explanation made sense. Any thoughts would be appreciated. Thanks!
  • Create New...

Important Information

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