Problem with fields - Rev 3.0

bjb007 · Post by **bjb007** » Sat Sep 20, 2008 3:18 pm

Had a strange experience...

I have a programme which works.
I modified it to do almost the same
thing so renamed some hidden fields
which have data put into them by
the programme - numbers separated
by commas e.g. 4,3,7,11 etc.

The results were rubbish so I checked
everything but still no joy.

As almost a last resort I made the hidden
fields visible and found that even though
the code was running perfectly through the
code "put aNumber & "," after field theField..."
there was nothing in the fields.

After more checking I was left with only one
possibility - something not right with the
fields.

I used the message box to put similar
info into one of the six fields and it worked as expected.
When I ran the script next that one window had
the correct info put into it but the other five
were still empty.

I went through all six windows putting some info
into each field with the message box after which
they all had the right info in them and the
programme ran as expected.

Seems that Rev wasn't performing as it should.

Any ideas?

Janschenkel · Post by **Janschenkel** » Sat Sep 20, 2008 7:45 pm

The only thing I can think of is that the data went into a field in a different stack - what was 'the defautlStack' when you put the data into the fields from your scripts?

Jan Schenkel.

bjb007 · Post by **bjb007** » Sat Sep 20, 2008 11:56 pm

Prog only has one stack.

Recall having same problem with
another script - again with only
one stack.

Janschenkel · Post by **Janschenkel** » Mon Sep 22, 2008 6:04 am

It doesn't necessarily have to be a stack in your program - if you've opened other stacks before, they may stay in memory even if invisible. Of course it's extremely difficult to find the original cause when all you're left with is the end result.

Jan Schenkel.

bjb007 · Post by **bjb007** » Mon Sep 22, 2008 6:56 am

The problem persisted even after closing Rev
and even after a reboot and not opening any
other Rev files before the problem one.

Just have to hope it doesn't happen again
but if it does I'll know how to fix it.