There are some quirks to the way PToolboxLib Fields accept text. Here is a small program that demonstrates what I mean, with a description in the comments.

<pre id=code><font face=courier size=2 id=code>//FieldQuirks.pc
// Demonstrates quirks of PToolboxLib Fields.
/*
Both text fields are set to 12 maximum characters. Graffitti text
entry is limited to 12 characters, alphanumeric in the text field,
and numeric alone in the numeric field. The point of this program is
to demonstrate that:
1) Text added by Fctl(INSERT,&string) is not limited to numeric in
the numeric field, but is limited by the field character maximum.
2) Text added by FsetText(Id, string) is not limited by numeric type,
nor by character maximum. The ability to add more text than was
allocated can be dangerous.

It may actually be useful to retain the ability to put some alphanumeric characters into a numeric field in some circumstances. This allows negative numbers and scientific notation. One could imagine a field where the user can change the sign of a number by tapping a button, but would be allowed only to enter digits into the field.

It's possible, and it's not that much work, but at this point I'm inclined not to implement such a feature. As you pointed out the user really already has this information. If you have a compelling reason for having it, I'll reconsider it though.

I just overhauled the v7.1.7 Sort function. It like rocks! It has natural, caseless, and reverse sort options. It can handle any data type. It can sort data structures (blocks of array elements as opposed to individual elements) and can do up to 3 levels of sorting, and it's bloody fast. I also have a complete Handbase and Pilot-DB database interface implemented (but that will be out in 7.2 due to the documentation complexity). Version 7.1.7 should be out in a few days.