Dan,
When you trace the program, use the F6 option to watch what happens to
the variable invbin1 as each step in your program is executed?
Also check your form to see the field order using Layout, Change Field
Order. Does invbin1 come in the expected field order?
One other thing to check, try SET VAR rather than SET V. Since we are
seeking the unexplainable, that may be a factor. (Your example raised the
issue.)
Randy Peterson
Note that the initial setting of the variable requires that a data
type be specified. So if you cleared the variable invbin1 and then issued
the command: SET VAR invbin1 = NULL or whatever, the variable should not
be created, as it does not know whether is should be text, integer or
whatever.
However, after the data type has been set:
SET VAR invbin1 INTEGER = NULL
The value can be changed without specifying the datatype again:
SET VAR invbin1 = 35
>The skip may be the same, but there is a difference in how you set the
variable. It works when you explicitly say
SET V invbin1 INTEGER =
and not when you say
SET V invbin1 =
================================================
TO SEE MESSAGE POSTING GUIDELINES:
Send a plain text email to [EMAIL PROTECTED]
In the message body, put just two words: INTRO rbase-l
================================================
TO UNSUBSCRIBE: send a plain text email to [EMAIL PROTECTED]
In the message body, put just two words: UNSUBSCRIBE rbase-l
================================================
TO SEARCH ARCHIVES:
http://www.mail-archive.com/rbase-l%40sonetmail.com/
