I just figured out how to set the Initiation variable. When the workflow  runs
now I just increment the counter value in that. Now just trying to figure out
how to get that initiation variable back  into the list  column.

Set a variable  to the value in the column  before you do the calculation. Do the
calculation on the variable. Then, set the column to the value in the variable.

This works fine until I try to set the column  to the value in the variable. I
select Workflow Data from the dropdown, and there is nothing in the list!

What type of variable  are you using? The Workflow Data list  will only show
variables with the correct type for the action  you are performing...are you
using a String variable or a Number?

It is a number variable...............................

...and, is the field you are trying to update a Number column? If not, I think
you could create a String variable  and set it to the Number variable.

The problem is that when I try to access any Workflow Data there are none of my
Initiation Variables in that list.

Maybe I should mention that the column  was created by publishing an InfoPath
form to a doc lib. When I go to the doc lib settings I can't see the column,
but when I look at it in the standard view I can see the column.

Okay, I don't know much about InfoPath...promote the columns? Make sure that
the content types are available on the list?

update a list  item or set a value............

Simply assign it back  to the column  from the variable.

When I try that, the initiation variables are not available in the workflow  data
dropdown.

This one got tagged as spam so I don't know if this will make in...

Are you trying to reference variables from a different workflow? The variable
only exists for the duration of the current workflow. When you update the
variable, try storing it in a column  and then reference the column data.

How do I store the variable  in a column? And yes I am asking for step by step
please. I've been working  on this all day and I must either be missing something
or it's seriously screwed up! Maybe I need to go home and just look at it in the
morning.

If you need to store the thing, just create an extra field/column in the
list and when the variable  is set, stick it in the extra field. Then, when
your workflow  runs and needs that variable, you can pick it up from the
field.

Evidently fields generated by IP don't really exist. So
by creating the extra counter field I was able to use it in the workflow. Thanks
everyone for being so patient! I appreciate all the help. Coffee at the
sharepointdiscussions Starbucks is on me!

Like I said before, I don't know InfoPath, but is that related to promoting
fields?

you should be able to achieve the same result by
promoting (aka publishing) the field in question. That's what you do to get
SharePoint to recognize the data and store it in a list  field.

FYI, one way to avoid this kind of confusion would be to create content type
and then base your InfoPath form on that. Then when you need a new field,
you just create it in the content type and pull it through on the form. The
alternative would be to publish your form *as* a content type, but that
seems to require admin privileges, etc. that may or may not be within your
reach on a particular server.

Of course you can just do the field promotion thing and carry on... it's
been a while since I was the "InfoPath expert" (read: the guy who got stuck
doing IP most often) at my old employer, so I may not have the most
realistic perspective.

I am supposed to be the resident expert on all things SharePoint, and apparently
all things that touch SP.

Yes, when I publish the IP form I promote the fields to the list.

I came across this issue where fields promoted from InfoPath are hidden in
SharePoint by default, which (annoyingly) means you can't use them in workflows.
The way to make them visible is to select the check box "Allow users to edit
data in this field..." in the dialog in InfoPath when promoting the field.

The downside is that the field then becomes visible in SharePoint views for
users to possibly directly edit at will. I never got to the bottom of whether
the field could be properly hidden in SharePoint without breaking the workflow.

well, maybe now they'll finally believe I'm not the InfoPath expert.