Cannot post record out of range

> Your problem is that the record at the top half of the screen hasn't
> been
> posted when you jump to the record at the bottom half. The 'range'
> is built
> into your form's data model - the bottom record is dependant on the
> top record.

This could also happen if there is a programmatic setrange() for a new
value for the index being used, I think, where a value has been
entered for the key of the index and that value is 'out of range' of
the setrange() (setgenfilter() as well?).


Or am I misunderstanding?

--
------------------------------
Tony McGuire
 >> Stay informed about: Cannot post record out of range 

It could also happen if they are using a AI field as a key and have
exceeded the max value allowed, or a small integer as key and have
exceeded the 32k limit or if they are violating a lookup value in some
instances.

Gonna take some testing and checking but you have several things to
start with.

Denn Santoro
President
Resource Development Associates
http://www.RDAWorldWide.Com
Offices in the United States and Germany
Providing solutions to health care, business, governments and
non-profits since 1982

Tony McGuire wrote:
>> Your problem is that the record at the top half of the screen hasn't
>> been
>> posted when you jump to the record at the bottom half. The 'range'
>> is built
>> into your form's data model - the bottom record is dependant on the
>> top record.
>
> This could also happen if there is a programmatic setrange() for a new
> value for the index being used, I think, where a value has been
> entered for the key of the index and that value is 'out of range' of
> the setrange() (setgenfilter() as well?).
>
>
> Or am I misunderstanding?
>
 >> Stay informed about: Cannot post record out of range 

Jim,

Thank You. Your response got me off dead center, but I'm still grumbling. I
added a postrecord() to one of the fields in the header file, which at first
got the same error message. Then I tried a few other combinations (going
into and out of edit mode, adding a button to post the header record that
didn't work, etc.), and suddenly, I had a form that worked. Unfortunately,
in my irritation, I lost track of the exact changes, and I don't know why the
form works. I cannot reproduce the success if I start with a new copy of the
form that produces the error message. The only change in the form that I can
see is a postrecord command on change in value of one of the header fields.

I've been programming on a variety of systems for longer than I care to admit,
and this is as strange a problem as I've come across in a long time,
especially when I remember that the system has been in use for several years,
and there never has been a postrecord in the form until now. At this point,
I don't trust that the working copy of the form will continue to work.

With all that said, each form when it is opened starts out displaying a
different record. I do not see where in the form definition that record Id
is stored or how to change it. Could you explain where I can see or change
that information?

Jim Moseley wrote:
>bheavilin,
>
>Your problem is that the record at the top half of the screen hasn't been
>posted when you jump to the record at the bottom half. The 'range' is built
>into your form's data model - the bottom record is dependant on the top record.
>
>You've got 2 options:
>1. When you create the top record, also create a bottom record by default
>with matching master keys.
>2. When you arrive on the bottom record, first issue a postRecord() on the
>top record. This should pre-format the bottom record's keys.
>
>HTH,
>Jim Moseley

--
Message posted via http://www.dbmonster.com
 >> Stay informed about: Cannot post record out of range 

Tony,

I have not found any set range value, and in the table mode, I can add
records with any key value, so this is probably not the cause.

Thanks,
Bob

Tony McGuire wrote:
>> Your problem is that the record at the top half of the screen hasn't
>> been
>> posted when you jump to the record at the bottom half. The 'range'
>> is built
>> into your form's data model - the bottom record is dependant on the
>> top record.
>
>This could also happen if there is a programmatic setrange() for a new
>value for the index being used, I think, where a value has been
>entered for the key of the index and that value is 'out of range' of
>the setrange() (setgenfilter() as well?).
>
>Or am I misunderstanding?
>

--
Message posted via http://www.dbmonster.com
 >> Stay informed about: Cannot post record out of range 

Good suggestions, but none appear to be the case. The key is a character
field, and I can add any value in table mode. I have been careful to check
the lookup values, and do not believe they are causing the problem.

Dennis Santoro wrote:
>It could also happen if they are using a AI field as a key and have
>exceeded the max value allowed, or a small integer as key and have
>exceeded the 32k limit or if they are violating a lookup value in some
>instances.
>
>Gonna take some testing and checking but you have several things to
>start with.
>
>Denn Santoro
>President
>Resource Development Associates
>http://www.RDAWorldWide.Com
>Offices in the United States and Germany
>Providing solutions to health care, business, governments and
>non-profits since 1982
>
>>> Your problem is that the record at the top half of the screen hasn't
>>> been
>[quoted text clipped - 9 lines]
>>
>> Or am I misunderstanding?

--
Message posted via http://www.dbmonster.com
 >> Stay informed about: Cannot post record out of range 

> Good suggestions, but none appear to be the case. The key is a
> character


With the form in DESIGN,

Format | Filter

Check to see if a secondary index is defined, but more importantly if
there is any criteria set for any of the fields; be sure to scroll to
the last field.

That would be how you create a 'sticky' filter. In run mode, you
should also be able to interactively set a filter.

--
------------------------------
Tony McGuire
 >> Stay informed about: Cannot post record out of range 

bheavilin,

>I cannot reproduce the success if I start with a new copy of the
>form that produces the error message. The only change in the form that
I can
>see is a postrecord command on change in value of one of the header fields.

Are you manually comparing the code, or programatically? I run the CSDiff
utility on my code (broken out by individual method) to see exactly what
changed.

My bet is that you're forgetting the 'doDefault' in the ChangeValue() method.
You want to PostRecord() after changing the value (hence after doDefault).


Note that there might be other (or better) ways of doing this. You could
use the Arrive() method of the child tableframe to trigger the PostRecord(),
for example. Also, make sure you check the result of the PostRecord() &
don't just assume it happens correctly.


>With all that said, each form when it is opened starts out displaying a
>different record. I do not see where in the form definition that record
Id
>is stored or how to change it. Could you explain where I can see or change
>that information?

You might have saved each form with a different filter. Click on the funnel
icon & see if any unexpected values are set. Also, make sure all forms use
the same index on the 'master' table. Otherwise, the default record that
a form should open with is the first row of the master table's current index.
Note that I've spent lots of time trying to disable this default behavior,
since I want the form to open on the row the user has requested (through
some other function).

HTH,
Jim Moseley
 >> Stay informed about: Cannot post record out of range 

bheavilin,

>You might have saved each form with a different filter. Click on the funnel
>icon & see if any unexpected values are set. Also, make sure all forms
use
>the same index on the 'master' table. Otherwise, the default record that
>a form should open with is the first row of the master table's current index.
> Note that I've spent lots of time trying to disable this default behavior,
>since I want the form to open on the row the user has requested (through
>some other function).

I forgot to mention that you could have saved the forms with different Ranges
set. They can be checked on the Filter screen also.

HTH,
Jim Moseley
 >> Stay informed about: Cannot post record out of range 

We might be able to tell you what is gong on if you actually post the
code...

Denn Santoro
President
Resource Development Associates
http://www.RDAWorldWide.Com
Offices in the United States and Germany
Providing solutions to health care, business, governments and
non-profits since 1982

bheavilin via DBMonster.com wrote:
> Jim,
>
> Thank You. Your response got me off dead center, but I'm still grumbling. I
> added a postrecord() to one of the fields in the header file, which at first
> got the same error message. Then I tried a few other combinations (going
> into and out of edit mode, adding a button to post the header record that
> didn't work, etc.), and suddenly, I had a form that worked. Unfortunately,
> in my irritation, I lost track of the exact changes, and I don't know why the
> form works. I cannot reproduce the success if I start with a new copy of the
> form that produces the error message. The only change in the form that I can
> see is a postrecord command on change in value of one of the header fields.
>
> I've been programming on a variety of systems for longer than I care to admit,
> and this is as strange a problem as I've come across in a long time,
> especially when I remember that the system has been in use for several years,
> and there never has been a postrecord in the form until now. At this point,
> I don't trust that the working copy of the form will continue to work.
>
> With all that said, each form when it is opened starts out displaying a
> different record. I do not see where in the form definition that record Id
> is stored or how to change it. Could you explain where I can see or change
> that information?
>
> Jim Moseley wrote:
>> bheavilin,
>>
>> Your problem is that the record at the top half of the screen hasn't been
>> posted when you jump to the record at the bottom half. The 'range' is built
>> into your form's data model - the bottom record is dependant on the top record.
>>
>> You've got 2 options:
>> 1. When you create the top record, also create a bottom record by default
>> with matching master keys.
>> 2. When you arrive on the bottom record, first issue a postRecord() on the
>> top record. This should pre-format the bottom record's keys.
>>
>> HTH,
>> Jim Moseley
>
 >> Stay informed about: Cannot post record out of range 

Jim,

It turned out to be a filter that was accidentally saved with the form.
After I cleared that, the form started to work correctly. Thanks for your
assistance.

Bob

Jim Moseley wrote:
>bheavilin,
>
>>I cannot reproduce the success if I start with a new copy of the
>>form that produces the error message. The only change in the form that I can
>>see is a postrecord command on change in value of one of the header fields.
>
>Are you manually comparing the code, or programatically? I run the CSDiff
>utility on my code (broken out by individual method) to see exactly what
>changed.
>
>My bet is that you're forgetting the 'doDefault' in the ChangeValue() method.
> You want to PostRecord() after changing the value (hence after doDefault).
>
>
>Note that there might be other (or better) ways of doing this. You could
>use the Arrive() method of the child tableframe to trigger the PostRecord(),
>for example. Also, make sure you check the result of the PostRecord() &
>don't just assume it happens correctly.
>
>>With all that said, each form when it is opened starts out displaying a
>>different record. I do not see where in the form definition that record Id
>>is stored or how to change it. Could you explain where I can see or change
>>that information?
>
>You might have saved each form with a different filter. Click on the funnel
>icon & see if any unexpected values are set. Also, make sure all forms use
>the same index on the 'master' table. Otherwise, the default record that
>a form should open with is the first row of the master table's current index.
> Note that I've spent lots of time trying to disable this default behavior,
>since I want the form to open on the row the user has requested (through
>some other function).
>
>HTH,
>Jim Moseley

--
Message posted via http://www.dbmonster.com
 >> Stay informed about: Cannot post record out of range