|Subject:||Re: Locate Issue
|Date:||Tue, 1 Dec 2020 15:42:27 -0600
|From:||Mark Bannister <markRemove@THISinjection-moldings.com>
This is correct. You should store this as alpha if you want this
functionality or break it into two fields.
Changing to alpha would be the easiest I would think.
On 12/1/2020 2:53 PM, Peter wrote:
> I'll bet it is a rounding problem. Try viewing the number that Pdox is
> I had a huge problem working with decimals, I ended having to create an
> undefined field that awas formatted to 15 decimal places. I copy the
> number to that field and then read it, then everything behaves as expected.
> On 12/1/2020 10:50 AM, Steve Levet wrote:
>> I have a table with numeric tracking for orders. The Ordernum field is
>> N and
>> is the primary key. When orders are released which are not complete
>> any backordered
>> items are copied to a new record and the Ordernum is incremented by 0.1.
>> As an example I have an Ordernum of 194314.0, 194314.1, 194314.2,
>> and 194314.4. When I click locate and enter the .0, .1 or .2 number
>> the record
>> is found. However, any number above .2, eg 194314.3 or 194314.4 cannot be
>> found unless I select advanced pattern match. Any idea on why and how
>> can be corrected so that I can find the Ordernums above .2?