Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About vwgtiturbo

  • Rank

Profile Information

  • Location
    Lincoln, CA

FileMaker Experience

  • Skill Level
  • FM Application
    14 Advanced

Platform Environment

  • OS Platform
  • OS Version
    Win7, Win10, and Mac El Capitan

Recent Profile Visitors

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

  1. Thank you very much for that example. It perfectly explains what I was looking for (and the idea really simplifies my relationship graph). I did have to create some relationships to allow conditional formatting (that is based on field value) but otherwise, things are much more tidy. Thanks again for the confirmation!
  2. Hello! Thank you for the response (and my apologies for my lack of it!). I spent a couple of days going over what you stated, initially thinking "Hmm... that doesn't address the relationship angle of my question??". However, after a few days, I am starting to understand the point (and realizing that I need to find some good resources for designing with FileMaker, versus the multitude of resources that simply explain how to use the software). When designing how things were going to go, I was only thinking about designing it in a way that would translate to a "normal" SQL database (I should
  3. Hello all, While I'm not exactly new to using FileMaker (17, in this case), I am quite wet behind the ears with a lot of its functionality, and the proper way to do things. I've put together a few solutions that seem to work, but they aren't pretty, and I'm sure they are quite inefficient. I'm not really sure how to ask this question, so I'll lead with a simplified example: Let's say I have one table that is the focal point of a relationship (Table X). In that table, I store foreign keys to smaller tables (1-5) that just provide options for the main table foreign key fields (via
  4. Thank you for the resources, Lee! I will keep those references handy. Not being able to put together a properly sanitized variant of the DB I am using (for peer review), I ended up simply creating a different layout to use for searches. For whatever reason, going into Find mode (on my usual layout) and selecting a drop down menu field was resulting in "<no values defined>". This kind of made sense; in Browse mode, these menus are based on value lists based on related records, and in Find, the context of relation seems to be removed. On the new layout, I opted for text input fields (
  5. I'll attempt to put something together this weekend. The database will require quite a bit of sanitizing and loading with bogus data. Thanks!
  6. Hello all! I'm sure this will be a very basic inquiry for the gurus, but I can't seem to wrap my head around it... My old FM database was a simple flat file affair, and searching was pretty much a no brainer. After rebuilding it as a relational database, I'm noticing that my searches are... impossible. Many of my fields are based on value lists, that are in turn based on related records. When I enter Find mode, and I select a dropdown that is set up in this way, I am met with "No Values Defined". Now, it makes sense that no values are defined, as I am in Find mode and not IN a record
  7. Thanks for the 360Works link! Over the course of time and subsequent revisions/fixes/additions, the cost of this software could pay for itself easily if it works out well! Thanks for that tip! I honestly had never heard of data separation (this is my first complex database; all others have been single-user flat-file type). I wish I would've thought of this before fielding the database to begin with, hahaha.
  8. Hello, The forum search is failing me, and Google is yielding old results, so I figured that I'd take a shot in the dark here... I built a fairly complex database a few months ago, and sent it to my counterparts at overseas locations to use until I can implement one last (time-consuming) section. I am working on applying fixes to existing formulas/layouts, and adding new scripts/layouts/tables to a "Master" DB file. But it occurred to me that applying all of these changes would be nearly impossible for the other DB files (as far as ensuring that ALL changes are implemented acros
  9. Nevermind... Solved it. Strange implementation (to my novice brain), but it works. Assigning the chosen graduation to a global variable, then using the value of the variable in the child table calculation was the way to go. EDIT: After further examination, the global variable wasn't needed. The original code works... if the record is committed. I guess when I moved on to the next record, the previous record wasn't committed, so the calculation choked. Adding a script step to commit the record after inserting the chosen increment, then pressing on with data entry, allowed the next record t
  10. Hi there! I've been beating my head on the desk for about a week trying to figure out an issue with auto-incrementing values in a child table, dependent on a value in the parent table, and it is driving me absolutely insane. In a previous iteration of the DB, auto-increment was working fine, as the value to increment the field was hard coded (i.e. incrementing the value by 1 for each successive child table record created). However, through real-world use, it became apparent that this was not ideal, and that I needed to have the option of incrementing the value by 1 or by 2. So, I devised
  11. Well, I wiped the entire section and just started over. With all of the other stuff in the live DB, I didn't want to risk breaking it just to accommodate this function. In the end, it is now MUCH simpler, and using a portal into the measurements table (from flight data layout), and implementing filtering of the portal based on the session and increment, am now able to display the 5 related measurements based on the session and increments selected in the flight data table. Thanks for the assistance! I likely never would have been able to fix it in its old state; starting that section over reall
  12. Ah, well I do have a diagram I put together in Dia, but am not sure if it meets the technical definition of an ERD (it is, after all, only my first large DB).
  13. It is VERY confusing. I guess I should've expected that, trying to combine two 'only vaguely related' areas in the DB. Seeing how it's put together, it certainly makes sense that it was a trial and error approach. What is kills me is how everything works in these simplified examples, yet in the actual DB, doesn't work (well... it works 2/3, with the last third being necessary). I have no idea how I managed to kludge it together and it's extremely frustrating. In the beginning, certain design decisions made sense, (not wanting to repeat certain data hundreds of times, like the date and ser
  14. Well... I spent about two weeks of trial and error getting my DB to provide conditional value lists as I wished, since I couldn't post the DB online. After using the DB for a week (mostly flawlessly), my conditional value lists didn't end up working. Being frustrated after beating my head against the wall for so long, I researched (more) about this ability, and have come to the conclusion that either 1) I have issues translating simple two table examples to my more complex example, 2) I'm missing something fundamental, 3) my structure isn't conducive to my goals, or 4) I have issue with creati
  15. You are amazing, thank you tons for the sample! After reviewing this file thoroughly, I came to the conclusion that I was looking at this all wrong. I was trying to use the 'New Report' aspect of FM, and I think that the grouping options and such just confused me (I could never see the results that I had my mind's eye). It seems that working backwards (trying to use the report to filter the data, versus filtering the data then reporting on the end 'found set') complicated matters (especially with regard to the grouping options I was setting up). Nothing would sort as expected, etc. In any
  • Create New...

Important Information

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