Jump to content

Guy_Smith

Members
  • Content count

    35
  • Joined

  • Last visited

Community Reputation

0 Neutral

About Guy_Smith

  • Rank
    member

Profile Information

  • Gender
    Male
  • Location
    SoCal

Recent Profile Visitors

1,287 profile views
  1. Engine Exhaust Emissions Database ERD is Circular!

    Yeah, I sorta missed the "generate a record" part of your first response I got the script to work and my database is up and running thanks to your guidance - thanks so much and have a great afternoon!
  2. Engine Exhaust Emissions Database ERD is Circular!

    Rats! Phooey! I'm still stuck - I can't get the emissions join table to populate. I split the emission factor data into individual records, I've verified that I have the box checked to allow creation of records in the Emissions table and I've tried using a portal from the Engine table to display the emissions, but still nothing. I maybe shouldn't be pulling the data for the Engine bhp and Tier from the Engine table or the CAS and Pollutant Names from the Emissions Factor table (for the Emissions table), but I don't know how else to do that (I also tried to do automatic lookups for those fields, but it didn't work, either). Any chance of looking at my file and seeing where I went wrong? And, by the way, you will see the word "Tier" used in place of Year of Manufacture: Tiers are basically groups of years used by the EPA. Using them in this instance saves me some time as I only have to enter emission factor records for one Tier instead of three or four records, one for each year in the Tier. Thanks again for all of your assistance, Guy HARP DICE EmsInv Calc Sheet.fmp12
  3. Engine Exhaust Emissions Database ERD is Circular!

    That actually makes sense to me - who'd have thunk it?! Thanks again, Comment - your willingness to help us neophytes is a true blessing!
  4. Engine Exhaust Emissions Database ERD is Circular!

    Comment: Thank you so much for the help on this! And, of course, you're a step ahead of me already - I am currently only collecting data for 2016, but I anticipate that it will turn into an annual event and I will need to modify my database to include multiple reporting years. Any helpful hints on how to tweak the solution to handle that? Thanks again, Guy
  5. I am trying to set up a database to calculate and report exhaust emissions from diesel engines and am stumped at Step #1: The infamous Entity Relationship Diagram! I am looking at a few thousand engines and need to calculate how much of what kind of pollutants they kick out into the air. I have spreadsheets that list the Year of Manufacture, the horsepower, the serial number, how long the engine ran during a given year and how much fuel it consumed during that year. I also have some spreadsheets that list what the Emission Factors, usually expressed in pounds per hour operated or pounds per gallon of fuel consumed, for each of the two dozen chemical compounds I’m interested in tracking. Those emissions are relatively simple to calculate: Multiply the Emission Factor times the number of hours operated (or times the gallons of fuel consumed) and we’re done. Except for the fact that the Emission Factors are based on the Year of Manufacture and, in some cases, the horsepower rating of the engine, so I have to circle back around to the Engine table: I don’t know how to connect the emission factor for, say, Arsenic to a specific engine, say a 154 hp Chevy made in 2014, based on that engine’s year of manufacture and hp rating. So my ERD keeps looking something like this: Engines --->Emission Factors--->Engines or Engines ---< Emissions >---Emission Factors--->Engines My computer keeps puking ones and zeroes all over my keyboard when I try either setup in my Relationship Graph! The only other way I can think of accomplishing these seemingly simple calculations is to write a boatload of scripts with variables, but I’m not even sure I could come up with all of the combinations/permutations involved. And, unfortunately, I can’ even spell SQL, let alone know how to execute one of ‘em! I have attached a (simplified) copy of the spreadsheets I currently use to better explain my problem. I hope one of you will find this to be mind-numbingly simple and explain how it should be done. Thanks very much for your time and consideration. Sincerely, Guy Engine Emissions Calc Sheet MOD for FMF.xlsx
  6. Thanks for your time and patience on this, webko, but I think I'm even more confused now: I thought the whole purpose of sliding left was to strip away the extra blank space in the leftmost block to allow for differing lengths of text, such as names. Is there a better way to merge the fields together to avoid this 'gap-osis'? Thanks again!
  7. Lee and webko: Thanks so much for your feedback. The revised calc makes my solution a LOT more robust and will prove useful in making some of my earlier attempts work much better! webko: I'm still a bit confused about "...The problem was that the second text black had a fixed left point, leading to the extra space..." Where do I find the fixed left point setting? I've gone through every panel in the inspector, but can't find anything different between the two strings: The text attributes are the same, there is no padding in either, and all indents are set to zero. Can I please bug you one more time and have you explain this to me in noob-speak? Thanks again - you guys rock!
  8. I've read through the previous posts on things not sliding left properly and I've tried all of the known fixes, and I'm still stumped. Here's my problem: I'm trying to get a mailing label layout to display a comma and then any suffix that may follow a person's name (such as Ph.D, PE, MSCE, etc.), but if there is no suffix, then I do not want the comma to display. Should be a piece of cake, right?! Ummm...Nope! I have fields for prefix (Dr., Ms., Mr., etc.), first name, last name, and suffix. I first added a calculation field to combine the prefix, first name, and last name: = Prefix & " " & First_Name & " " & Last_Name and a second calculation field to combine a comma and the suffix: = ", " & Suffix. The comma and suffix field is conditionally formatted to be white if there is no suffix. When viewed in Browse Mode, it's looks wonky, but, OK, it's sorta supposed to look goofy, so I can handle that - let's switch to Preview mode and see what happens: There is a gap between the last letter of the last name and the comma - about two letter-width's. And printing it shows the same problem - way too much room between the last name and the comma. I have quadruple-checked the following: The fields are touching - I've even tried overlapping by a pixel or two just to make sure, to no avail. All fields are set to left and top, all padding is set to zero, and, yes, I did check the 'Remove blank space by: Sliding Left' checkbox. And I've tried the above using the original text fields (plus a new text field for the comma), my added calc fields, and merge fields. I'm also not sure why I have a blank label/page between each entry - may be a field is too close to the edge, but I'll worry about that later. I have attached a copy of the offending file for reference. I'm sure it's something simple, but I just can't find it - any help would be greatly appreciated! Mailing_Label_test_1.fmp12
  9. Thanks to the both of you - That answered my concerns about the DDR not showing all of the script calls possible and I also now know how to test for OMG's. As always, your time and assistance are greatly appreciated. Best Regards, Guy
  10. Is it always safe to delete a script when the DDR lists no Layouts that use the script and no other Scripts that call the script? I'm trying to clean up my file without shooting myself in the foot: I can't think of why I would ever need such a script, but don't want to find out the hard way that I could still need them. Thanks in advance, Guy
  11. Thanks, Gentlemen: Turns out the problem was a layout that "lost" its association to a Table - once I reassigned the table, everything worked as expected. Your knowledge and assistance are greatly appreciated! Best Regards, Guy
  12. YIKES! I tried to generate a DDR for my solution and got the following error: SAXParseException: Invalid character 0x12 in attribute value 'PlatformType' (Occurred in entity C:/Users\guys\AppData\Local\Temp\FMTEMPFM5128_4.tmp', at lime 24503, column 981.) I have attached a screenshot for clarity. The PlatformType bit is interesting as I work on the file at my office on a PC (Windows 10) and at home on a Mac (OS X Sierra). I clicked the OK Button three times and a DDR popped up, but only contained the Report Overview Page: The correct amounts of Tables, Relationships, etc. showed up, but none of the links work: It's an empty DDR. After shutting down FMP, reopening the file and trying again, I received the same error except the "FMTEMPFM5128_4.tmp" changed slightly to "FMTEMPFM5128_6.tmp". (the 6 replaced the 4) I am, as usual, clueless - any ideas out there? Thanks, Guy SAX Parse Exception 092916.pdf
  13. All layouts randomly change to weird "Z@R701E.tmp" font

    Hmmm... Could be. I already reset the font cache and the problem went away - if it comes up again, I'll try the restart trick and see what happens. Thanks for the added insight.
  14. All layouts randomly change to weird "Z@R701E.tmp" font

    Thanks, Josh - I sure appreciate the quick response! I'll have to get my IT gurus to get that done - they have our computers locked down pretty tight, but I'm glad to hear that it's not terminal!
  15. This is getting frustrating: About ten percent of the time I open a file, all of the layouts are displaying in a font named Z@R701E.tmp or, less commonly, Z@R6FAB.tmp. If I close and reopen the file a number of times, the problem will sometimes self-correct and show the normal fonts (I only use Arial, Calibri, and Times New Roman), but sometimes I have to go through every layout and reset the fonts. This only happens to my FMP 15 files - no other programs have been affected. I have attached a screen shot for clarification. Any ideas? Thanks, Guy Weird font example.pdf
×

Important Information

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