Jump to content

KToomey

Registered Users - Approved
  • Posts

    12
  • Joined

Converted

  • FusionPro Products
    No

KToomey's Achievements

Apprentice

Apprentice (3/14)

  • First Post Rare
  • Collaborator Rare
  • Conversation Starter Rare
  • Week One Done
  • One Month Later

Recent Badges

10

Reputation

  1. OK... I figured this one out, though I'm unsure as to why I got the error message that I did. It turns out that the problem was that my input and output file names were too long. While I am working on a Mac, all of the files reside on our network, which is hosted on Windows servers. While both Windows and Macs allow long file names now, for some reason, when saving a file from the Mac to the network, the filename can't be longer than 32 bytes (actually 31, because Windows saves the data and resource forks as separate files).
  2. I'm getting an error when trying to compose a known working FusionPro document: Could not load job options from file Composition stopped with errors. Error no 1127. We are running FusionPro Desktop 7.1P1c on Mac OS X 10.5.8 As I understand it, this error only appears when working with FusionPro Direct or Server, so I'm not sure why I'm getting it, since we don't have those installed. I have already made sure that the "Use FusionPro Direct on Scheduler" box is NOT checked. I've already tried closing and restarting FusionPro and Acrobat, without success. I'm going to try to reboot the Mac, but then I'm pretty much out of ideas to try.
  3. I think the problem must be that I'm coming in to the Mac via VNC from a Windows PC. Everything else seems to work just fine, so I don't understand why this keystroke wouldn't work here when it works everywhere else.
  4. I'm using v7.1P1c in Acrobat Pro 9.5.4 on a Mac with OS X 10.5.8 I have a data file that's about 8,000 records long, and I want to jump to the middle to preview some records. Is there a quick way to get there without pressing the forward button 4,000 times? I've tried typing in 4,000 in where it displays the record number on the Preview Record Selector, but that's a no-go.
  5. You said "Topic E = Variable lines A & G" so I presume that means you know each variable line possible. First, I would create a global variable called "DisclaimerText". Secondly, create a resource for each variable disclaimer line that could appear, and name it using a single character to identify it (i.e. "DisclaimerLine_A", "DisclaimerLine_B", etc.) Then, thirdly, put code similar to the following in your OnRecordStart rule: a = "" for (x=1; x<4; x++) { switch(x) { case 1: TopicField = "TopicOne"; case 2: TopicField = "TopicTwo"; case 3: TopicField = "TopicThree"; } switch (Field(TopicField)) { case "Global & Financial Market Outlook": a += "AE"; case "Investing in an Uncertain World": a += "AF"; case "Beyond Bonds - Income Alternatives with Growth Potential": a += "ABFS"; // ... add as many case statements as needed (one for each topic possible) to show // which variable disclaimer lines that each topic gets, each time appending // it to the variable "a" case "High Conviction Investing: The Benefits of Active Management": a += "DHR"; } } // Loop through a, if current character of a isn't found in b, add it to b b = "" for (x = 0; x < Len(a); x++) { if(StringToNumber(b.indexOf(a.substr(x,1))) = -1) { b += a.substr(x,1); } } // Now combine all the disclaimer lines from their respective Resources for (x = 0; x < Len(b); x++) { DisclaimerText += Resource.content("DislaimerLine_" + b.substr(x,1)) } Lastly, create a rule that returns the global DisclaimerText variable and place that rule into your text frame: return DisclaimerText;That should work, I think!
  6. um.. OK, except that adding the "break;" statement didn't work. I got the same results as without it!?
  7. sschardan: Your solution works (for this instance), but we can't guarantee that the client won't be putting characters in that field that wouldn't be valid in a page name. Nor do we dictate how many characters long that field is.
  8. Also, I just tried this code using the "break;" syntax and got the same results as with my original code: FusionPro.Composition.SetBodyPageUsage("INVY_SHOPPERS_SRP", false); FusionPro.Composition.SetBodyPageUsage("INVENTORY SRP", false); FusionPro.Composition.SetBodyPageUsage("INVENTORY ONLY", false); FusionPro.Composition.SetBodyPageUsage("SHOPPERS SRP", false); FusionPro.Composition.SetBodyPageUsage("SHOPPERS ONLY", false); switch (Field("VERSION")) { case "Invy, Shoppers, SRP": FusionPro.Composition.SetBodyPageUsage("INVY_SHOPPERS_SRP", true); break; case "Inventory, SRP": FusionPro.Composition.SetBodyPageUsage("INVENTORY SRP", true); break; case "Inventory": FusionPro.Composition.SetBodyPageUsage("INVENTORY ONLY", true); break; case "Shoppers, SRP": FusionPro.Composition.SetBodyPageUsage("SHOPPERS SRP", true); break; case "Shoppers": FusionPro.Composition.SetBodyPageUsage("SHOPPERS ONLY", true); break; }
  9. OK, I understand the break now, but how is it that something like this would work without the break? switch (Field("VERSION")) { case "Invy, Shoppers, SRP": return "1"; case "Inventory, SRP": return "2"; case "Inventory": return "3"; case "Shoppers, SRP": return "4"; case "Shoppers": return "5"; }
  10. I'm not sure I know what you mean by a break. I thought I just needed a semicolon after each statement (which I have in there).
  11. I have an OnRecordStart rule that is not acting the way I think it should. I have a work-around by using IF statements versus the SWITCH rule I tried to use. However, I thought I'd ask here to see why this doesn't work the way I think it should: FusionPro.Composition.SetBodyPageUsage("INVY_SHOPPERS_SRP", false); FusionPro.Composition.SetBodyPageUsage("INVENTORY SRP", false); FusionPro.Composition.SetBodyPageUsage("INVENTORY ONLY", false); FusionPro.Composition.SetBodyPageUsage("SHOPPERS SRP", false); FusionPro.Composition.SetBodyPageUsage("SHOPPERS ONLY", false); switch (Field("VERSION")) { case "Invy, Shoppers, SRP": FusionPro.Composition.SetBodyPageUsage("INVY_SHOPPERS_SRP", true); case "Inventory, SRP": FusionPro.Composition.SetBodyPageUsage("INVENTORY SRP", true); case "Inventory": FusionPro.Composition.SetBodyPageUsage("INVENTORY ONLY", true); case "Shoppers, SRP": FusionPro.Composition.SetBodyPageUsage("SHOPPERS SRP", true); case "Shoppers": FusionPro.Composition.SetBodyPageUsage("SHOPPERS ONLY", true); } What is actually happening is that the case statement that matches is working and turning on the page that is should, but every case statement listed after that one is also turning on its respective page. Anyone have any idea why?
×
×
  • Create New...