Jump to content

Bobby Bradley

Newbies
  • Content count

    7
  • Joined

  • Last visited

Community Reputation

0 Neutral

About Bobby Bradley

  • Rank
    member

Profile Information

  • Industry
    Entertainment and Conservation
  • Gender
    Male
  • Location
    USA/Namibia

Contact Methods

  • Website URL
    bobbybradleyphoto.com

FileMaker Experience

  • Skill Level
    Intermediate
  • FM Application
    15 Advanced

Platform Environment

  • OS Platform
    Mac
  • OS Version
    10.11
  1. Background Image adds margin in Preview

    I have a layout for printing on a letterhead and have inserted an image file as the Background Image to serve as the letterhead. Printing and Save to PDF work as expected, but for the life of me I cannot get the background image to display correctly in Preview mode. Not displaying correctly in Preview mode is not terrible except, when the client does a print preview and it doesn't line up, there will be questions...even though it print correctly. Basically, it looks like the background image has a pre-determined padding applied to it at the top, but all parts and objects are set to padding 0. Has anyone else experienced this? Preview mode - letterhead has padding Printed PDF - the letterhead is up where it should be:
  2. Array Building - Key Number Problems

    Well, sleeping on it I found the culprit on my own. Here's the fix if anybody has similar problems. Changed the line pos = Position ( localArray ; key; 1 ; 1 ) ; TO pos = Position ( localArray ; key; 1 ; -1 ) ; so now it searches the array properly.
  3. Hi All, Apologize if an answer exists already...did some research to no avail. I have a script running a 2D array on a single table of records which has worked fine for me in past projects, but this time the "key" is a simple number field as opposed to a text field. The problem is that the numbers range from 1 up over 2000. The Array seems to lump some of the single, double and triple digit numbers into the 4 digit number keys also affecting the totals. Basically, as a result instead of 1744 records being reported the array is lumping everything into only 818 records despite the "key" being unique and records with 4 digits are reporting inflated totals. The reason for this array function is to future proof the table when multiples of keys are added (and serve other queries) Fields in question are as follows: EVENTS::__fk SHOW ID# (I've tried it as a Text and Number Field also validating) Here's the array function (the rest of script works fine): Let ( [ localArray = $$Rainbow ; key = EVENTS::__fk SHOW ID# ; pos = Position ( localArray ; key; 1 ; 1 ) ; rowNum = ValueCount ( Left ( localArray ; pos ) ) ; rowData = Substitute ( GetValue ( localArray ; rowNum ) ; "|" ; "¶" ) ; PrevGrandTotal_Proposal = GetValue ( rowData ; 2 ) + 0 ; PrevGrandTotal_COGS = GetValue ( rowData ; 3 ) + 0 ; PrevSalesTax = GetValue ( rowData ; 4 ) + 0 ; PrevLabor_COGS_Estimated = GetValue ( rowData ; 5 ) + 0 ; PrevSupport_COGS_Estimated = GetValue ( rowData ; 6 ) + 0 ; PrevLabor_Actual = GetValue ( rowData ; 7 ) + 0 ; PrevCOGS_fromQB = GetValue ( rowData ; 8 ) + 0 ; NewGrandTotal_Proposal = Case ( not IsEmpty ( EVENTS::ws_grandtotal_proposal_n ) ; EVENTS::ws_grandtotal_proposal_n ; 0 ) + PrevGrandTotal_Proposal ; NewGrandTotal_COGS = Case ( not IsEmpty ( EVENTS::ws_grandtotal_cogs_n ) ; EVENTS::ws_grandtotal_cogs_n ; 0 ) + PrevGrandTotal_COGS ; NewSalesTax = Case ( not IsEmpty ( EVENTS::ws_nys_salestax_proposal_n ) ; EVENTS::ws_nys_salestax_proposal_n ; 0 ) + PrevSalesTax ; NewLabor_COGS_Estimated = Case ( not IsEmpty ( EVENTS::labor_cogs_total_n ) ; EVENTS::labor_cogs_total_n ; 0 ) + PrevLabor_COGS_Estimated ; NewSupport_COGS_Estimated = Case ( not IsEmpty ( EVENTS::labor_support_total_n ) ; EVENTS::labor_support_total_n ; 0 ) + PrevSupport_COGS_Estimated ; NewLabor_Actual = Case ( not IsEmpty ( EVENTS::actuals_labor_n ) ; EVENTS::actuals_labor_n ; 0 ) ; NewCOGS_fromQB = Case ( not IsEmpty ( EVENTS::actuals_COGSfromQB_n ) ; EVENTS::actuals_COGSfromQB_n ; 0 ) ; newRow = key & "|" & NewGrandTotal_Proposal & "|" & NewGrandTotal_COGS & "|" & NewSalesTax & "|" & NewLabor_COGS_Estimated & "|" & NewSupport_COGS_Estimated & "|" & NewLabor_Actual & "|" & NewCOGS_fromQB & "¶" ] ; Case ( pos = 0 ; localArray & newRow ; LeftValues ( localArray ; rowNum - 1 ) & newRow & RightValues ( localArray ; ValueCount ( localArray ) - rowNum ) ) ) Any advice is greatly appreciated...hope I've explained it well enough.
  4. Security

    Hi, I too am having a similar problem. For any user account other than admin only 2 weeks show up. I tried using Tim's sample file and integrating the file into my own database and the same problem persists. Here's a screenshot when I run Tim's sample file as user account "EmployeeA" in the sample file. Has anyone else come across this issue and found a fix?
  5. Thanks Comment. You nailed it. That is the result we were looking for. I'll have to parse the custom function a little more to understand the method, but it works for our needs as of now. Thanks again!
  6. Thanks for the replies...I'm new to posting on the forum. We want an output that looks like this Cheetah #1 Released into wild Date = Dec 15 2012 Current Date = Today Field1 - Days_Since Release until Current Date in Wet Hot Season = x Field2 - Days_Since Release until Current Date in Dry Cold Season = y Field3 - Days_Since Release until Current Date in Dry Hot Season = z Table defining seasons - Attached. I hope this makes more sense...feel free to let me know any questions.
  7. Hi All, We have a database that is tracking wild animals that have been released into the wild (radio collared) and requires a lot of calculations based on date data. We are stumped on how to do the following as cleanly as possible: Calculate the number of days to date in a season that an animal has been in the wild. For Example: Table 1 Animal Released Date Today's Date Calc_Days released Wet Hot Season Calc_Days released Dry Cold Season Calc_Days release Dry Hot Season Table 2 Month | Season | num days in season January | Wet Hot | 31 February | Wet Hot | 28.25 March | Wet Hot | 31 April | Wet Hot | 30 May | Dry Cold | 31 etc...for all months A work around we found is to just create a date table with every date from our past data set until say 2020 and thien script it out to filter by a date range and return counts based on found sets. That seems like it will work but it would be much cleaner to calcuate it so we don't need to fire a script (which could take up resources) each time to refresh the data. Thanks in advance.
×

Important Information

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