Paradox Community

Items in pnews.paradox-programming

Subject:Re: Number Format
Date:23 Sep 2020 18:23:52 -0400
From:"Kevin Zawicki" <numberjack@wi.rr.com>
Newsgroups:pnews.paradox-programming


see my other post below

but in addition to my other post

why not use a timestamp and back fill? I would even log a timestamp of shift
start and timestamp the entry was entered.
etc




Peter <peterspammenot@whiteknight.email> wrote:
>It is a timecard system. Employees enter the work order number and job 
>hit enter and they are on the clock. There are other features.
>
>The problem is that sometimes they forget to punch on/off a job so they

>have to be able to enter corrections, hence the need for decimals to 
>insert corrections in between existing records.
>
>
>On 9/23/2020 1:30 AM, Tom Krieg wrote:
>> What's the business logic behind this?
>> 
>> 
>> On 23/09/2020 2:06 pm, Peter wrote:
>>> I cannot use rounded figures.
>>>
>>> I use these numbers for unique ID ("EntryID") in the first field of my

>>> table. I need to be able to insert new records in between sequentially

>>> numbered records:
>>> e.g.
>>> 1
>>> 2
>>> 3
>>> 4
>>> 5
>>>
>>> May need to become
>>> 1
>>> 1.1
>>> 2
>>> 3
>>> 4
>>> 5
>>>
>>> Further it may need to become
>>> 1
>>> 1.01
>>> 1.02
>>> 1.03
>>> 1.1
>>> 2
>>> 3
>>> 4
>>> 5
>>>
>>> Getting crazy
>>> 1
>>> 1.01
>>> 1.001
>>> 1.002
>>> 1.02
>>> 1.03
>>> 1.1
>>> 2
>>> 3
>>> 4
>>> 5
>>>
>>>


Copyright © 2004 thedbcommunity.com