We are using Paradox 11 on a purchase order system. We use a form to create
the POs. The top of the form updates a PO master file, and the bottom
updates PO details, with the items to be purchased.

Recently, we have been receiving the message "Cannot post record out of
range" whenever we move from the top of the form (PO master file) to the
bottom (PO details). This happens when we try to add a new PO. I have
searched the tables and the form and cannot find a range definition anywhere.

When I check the PO master table, the PO record is not posted. I can force
the post to happen by trying to insert a new record. After that, we can call
the PO up and fill in the detail records.

This message even happens when I delete POs that were created before the
problem started and add them again (testing to see what range limits there
may be). It also happened after I deleted all records in a test copy of the
files, so it does not appear to be a problem with files too full. I have
also rebuilt both files to ensure that the indexes were OK.

Any help would be appreciated.

BHeavilin

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

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

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

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

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

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

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

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

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