Stefan Cameron on Forms
Building intelligent forms using Adobe LiveCycle Designer

Return to the Blog

It has been almost 4 months now since I put my blog on hold. Things were getting increasingly busy with my wife’s new clothing business, The Beautiful Pear, but now that we’ve been through our first year, the learning curve (for me) has leveled-off and I’m now able to refocus some energy into my blog.

I’ve been keeping track of the traffic since Oct 29, 2007, and despite my hiatus, many of you have kept finding useful stuff here with an average of 100 visits per day:

100 visits/day from Oct 29, 2007 to Feb 18, 2008

Thanks for sticking around and I hope I’ll be able to keep posting things that are of interest to all of you.

Posted by Stefan Cameron on February 19th, 2008
Filed under General
Both comments and pings are currently closed.

3 Responses to “Return to the Blog”

  1. Bryan on March 4th, 2008

    Glad to see you’re back. Your blog has been very helpful to me in learning LiveCycle for use in our SAP NetWeaver Environment.

    I was hoping you could take a look at something for me. I’ve found what looks to me like a bug, but perhaps this is how FormCalc was designed. I’ve since solved the issue by re-writing the script in question in JavaScript, but I’m curious about it.


    P.S. I’d have put this in a more appropriate blog post, but the one that seemed the most appropriate had a disclaimer about you not following comments on older posts. So I stuck it here. Sorry about that.

  2. Stefan Cameron on March 10th, 2008


    That’s a really long and complex post to follow but I think it comes down to the fact that you can’t access row[0] during the first iteration of the loop when using FormCalc. If you could create a new form that isolates this problem in a really simple way, then I could have a look at it if you sent it to this address, along with the some XML data to merge into the form to test with: formcollateral1 at stefcameron dot com

    Also, I’m wondering why you access field values in FormCalc by using “.value.#type”? In FormCalc, the field raw value is the default property so “$” will return the raw value of the field in context and “MyNumericField” will return the raw value of the field named “MyNumericField” — no need to know whether it’s “value.#integer” or “value.#float”, etc.

    PS: The disclaimer is there in the event my comment levels return to what they were when I went on hiatus. If that happens, there’s no way I’ll be able to keep-up with all of them at which point I’ll only be able to stick to comments related to the most recent posts… But you’re lucky this time since it’s still relatively quiet.

  3. Bryan on March 10th, 2008


    Thanks for taking a look. Since I’ve effectively solved the problem by rewriting in javascript, I’m going to have to develop the example form on my own time, which means I probably won’t get to it until the weekend. But I will get to it.

    “Also, I’m wondering why you access field values in FormCalc by using “.value.#type”?”

    Because I’m entirely self taught on creating Adobe Forms. It’s been a long time since I’ve written any javascript or VB (which FormCalc reminds me of a little bit). I hit the period button and used the autocomplete after typing a variable name; I saw those available and assumed they were necessary. It’s nice to know they’re not.