Jump to content

vwgtiturbo

Members
  • Content count

    18
  • Joined

  • Last visited

Community Reputation

0 Neutral

About vwgtiturbo

  • Rank
    member

Profile Information

  • Gender
  • Location
    Lincoln, CA

FileMaker Experience

  • Skill Level
    Novice
  • FM Application
    14 Advanced

Platform Environment

  • OS Platform
    Windows
  • OS Version
    Win7, Win10, and Mac El Capitan
  1. Conditional Value List Issues (I know...)

    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 really helped out.
  2. Conditional Value List Issues (I know...)

    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).
  3. Conditional Value List Issues (I know...)

    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 serial number, so those were split into the Sessions table), but now... yuck. Maybe it's just my desire to select the equipment (then have the available sessions displayed), the select the desired session (then have the available increments displayed), then select the desired increment (which would display the actual measurements) that makes things so complicated. I wanted to be able to drill down, but... it's hell, hahaha. Thanks for the insight. I'll likely try and integrate your suggestion and see if it simplified matters, tomorrow. I'm so burned out from looking at this. As an aside, when you reference the ERD... are we talking about just a screenshot of the relationships, or an actual ERD (that opens in software and can be manipulated)? I've not used a piece of software to create an actual ERD, and am eager to learn...
  4. 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 creating the value lists from the proper sources (which is easy to do, considering the multiple table complexity). As a result, I created a greatly simplified and sanitized version of the DB (only containing the sections in question) and would GREATLY appreciate a Filemaker veteran's insight into how I could do this. The relationship graph of the DB file has notes that explain the desired outcome. I am just at a loss for words really; I've cursed FM relentlessly lately, hahaha. Thanks in advance for any push in the right direction. I'm not looking for someone to outright solve my issue, but would really appreciate something that puts my mind on the right track, as my logic obviously doesn't jibe with FM. Thanks again! Flight Equipment Measurements (Simplified).fmp12 EDIT: I will make a copy of the above example file to show how the parts are related as of now (not that the relationships are correct, but I was able to ALMOST get it to work...). In addition, I will add notes to the updated file to show how the value lists are put together. Maybe it is just a simple thing to correct (although I AM more interested in starting fresh, the CORRECT way, versus my trial and error...). EDIT 2: Well... After creating the extended (as constructed in my DB) example file, I've found that everything works as it did during my testing. So... It appears that subsequent relationships that I created after this section (in order to view reports/other related data) have mucked with the relationships in this section. Now I have to try and figure out which relationship is causing the problem, and attempt to design it out, while keeping the functionality in the rest of the DB. Ugh... Flight Equipment Measurements (Extended).fmp12
  5. Scripting a Constrained Search?

    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 case, beyond straightening my thinking, I now know how to utilize global fields :-) I don't know why I've never gotten that to work correctly... All I need to do is figure out how to get the Increment worked into this (and sorting them), and figuring out print presentation, then all will be well. Your file gives me a great start! Thanks again for the help! I am SO ready to get this section of the DB done; I'm tired of looking at the same area and am ready for a change. Light at the end of the tunnel, so to speak... As a side note, the script step for going to the Sessions layout never would have crossed my mind; I couldn't wrap my brain around it ("I don't want to go to that layout! Oooohhh..."). Light bulb eventually went off, but I never would have thought of it. Thanks again!
  6. Scripting a Constrained Search?

    Using the same layout that I use for data entry to practice this (based on sessions, with the portal), the process works well (select equipment s/n from the pop-up normally used during equipment selection upon input, view the number of returned records, omit (total - 1) since all are entered chronologically). I never could get this to work with a report based on the Measurements table (from my reading, it seemed to me that reports should be based on the most child table, which, with my understanding, would be the Measurements table). So... I suppose I can duplicate this layout including the use of a portal (but cut out the superfluous elements not necessary when viewing/printing the information), then use a Summary field in the Sessions table to count the number of dates returned, and after the user selects the equipment to search for, omit (count - 1), or am I thinking of this entirely the wrong way?
  7. Scripting a Constrained Search?

    My apologies for such a late response. After reading the last reply, I decided to do a bit of reading so I wasn't a burden asking basic questions. Needless to say, I'm not sure if the design of my relationships/tables isn't conducive to what I'm trying to do, or if there is some basic principle that I am looking past (likely the latter). By reading this statement "You can find the latest measurement session, then do Go to Related Record[] to produce the report from the measurements table.", that would work in some cases, but I was hoping to go the other way. The method mentioned would show a list of dates to select from and Go to Related would show the resulting Equipment IDs and Measurements. What I'd like to do though is select the equipment first (as that is the most important aspect that we need to narrow the data by), then return all measurements under the LAST session date for that particular equipment. Going through the Report creation tool (an untold number of times), I'm not sure where I'm going wrong; maybe the terminology in creation doesn't suit my use case or I'm including too many grouping fields, (or not structuring the resulting layout properly), but I usually end up being able to successfully search a particular piece of equipment, but then ALL dates (and therefore, ALL measurements, even those out of date and no longer relevant). I experimented with setting a global field (the user selects the equipment serial number) for the Find operation, and never was able to make it work (not sure if that was even necessary, but I was trying anything). In all fairness, however, I've never had a global field/variable work, so that it obviously something I need to study and learn...
  8. Scripting a Constrained Search?

    Hmm... I think the part that is tripping me up is that a user would ideally search for the serial number first, but from what I've read on related searches, the report has to be based on the most 'child' table (which I assume, in my case, to be the table with all of the actual measurements listed). I think that the design of the tables themselves might not be helping me, but it seemed like the most logical (to avoid repeating data, space considerations, etc.), considering that the equipment serial number isn't located in the most child table. The increment is literally an 'increment'. So, when the measurements are done, date and equipment serial number are recorded, and the observer sets an adjustment (ranging from .5 to 2.5, in .05 increments) then there are 10 measurements recorded for each increment (e.g. set adjustment for .50, measurements 1 through 10; set .55, measurements 1 through 10; set adjustment to .60, measurements 1 through 10, etc.). Initially, everything was jammed into one table. So the date and equipment serial number were repeated hundreds of time, for one measurement 'session'. It just didn't seem right. Maybe I'm just not looking at this the right way...
  9. Forgive me if the terminology used in the title is incorrect, I'm still getting familiar with this beast... In a nutshell, I am taking measurements on a piece of equipment. I am recording the equipment serial number, date, the increment being measured (about 50 different values, from a value list based on a table), then 10 measurements for each increment. To avoid having the date and equipment serial number stored 500 times for each 'measurement session', I have those items split apart into separate tables, then all of the measurements stored in a junction table (see attached, items are renamed a bit to prevent interfering with actual database tables): I have a report based on the junction table (blue above) and it simply lists all values in the table. The user can search for a particular equipment serial number, but this returns all values related to that serial number (and all of the dates that measurements were taken). Certainly, the user COULD search for the particular equipment desired, then view the available dates, the modify the find to only return those dates. However, I was hoping to somehow script this action, such that the user could simply select the equipment serial number, and only the last 'session' measurements would be returned (the most recent date) automatically, as those are the only pertinent values. I've experimented with various script steps, and have zero luck. I'm hoping not to have to change the structure, as there is another area of the database that is now working as intended (after days of trial and error). I'm just not sure if I'm missing something really basic (overthinking things, as usual) or...? Thanks in advance for any insight!
  10. Learning Scripting?

    Excellent, thanks for the nudge! It's baffled me for months seeing some of the solutions that folks come up with, and having zero idea how they derived their method. It'll still be frustrating, taking me much longer (work and school), but at least I'll have something to work on in my sparse free time.
  11. Learning Scripting?

    Hello, In looking to make my database perfect, it has become obvious that I am going to learn Filemaker scripting. While I can Google and ask questions all day, I'd really like to learn how to do it myself (not so much the raw basic FM functions, but custom functions like 'case' etc.). As an example, with an old FM database, I had downloaded a script that would insert a decimal after I entered numbers in a field (for recording measurements). As an example, if the field entry was 'a' characters long, the decimal would be applied at position 'b'; if it were 'x' characters long, the decimal would be placed at position 'y'. While I used this downloaded script (along with others), it occurred to me that it would be so much better if I actually understood the script so that I could tailor it to other use cases or built completely new variants on my own. My stupid question for the week... where on earth would I even start with trying to learn this? I'm not even sure of the terminology that I should search for in an attempt to learn this. I'll admit that I also have to learn the logic behind these things (in addition to the actual functions and syntax). I just have, what I think, excellent ideas for my database (especially since I will not be the only one using it, so I'd like to make it easy and powerful for the other users), but am realizing quickly that I need more knowledge to do that. Thanks in advance for any push in the right direction!
  12. I had thought about this, however, during the build of the db, I would end up doing some of the structure, then test it via the design... more structure, more testing... after finally getting everything working the way I am intending, to do this would be a huge step backwards. Thanks though!
  13. That looks interesting as well, thanks! I just may have to explore that for future use.
  14. Hello Lee, that was an excellent link, thanks! On my Win machine, I get the 'DDR file missing' error (and exporting via XML is nearly useless). I'll try on the Mac. Thanks again! EDIT: As expected, the process works as expected on the Mac. The DDR is MUCH more interesting than I thought! Talk about handy... Thanks again for the help ;-)
  15. Hello! Being an FM novice, and just finishing the structure of my excruciatingly complicated database, I have to wonder... Is there way to export a list of tables and the fields within each, so I can be sure to include everything on my layouts? I created the layouts a while ago, but then had to redesign quite a bit, and only some bits were auto-added. I just wanted to have a 'checklist' per se, so that I don't have surprises when I actually sit down to USE the beast. I know I could simply expand all of the tables in the relationship graph and print to PDF, using it as a guide, but just wondered what other options there were. Thanks in advance for any insight or personal tips!
×

Important Information

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