At 07:48 2018-10-12, Alan Bourke wrote:
Easy for the staff to count, or difficult for the opposition to
count. Pick one.
In situations like this, aren't there supposed to be three
things with a choice of two? Especially on a Friday.
Sincerely,
Gene Wirchenko
It doesn't have to be either or. I have put forward the various
suggestions to the client and will let them decide how they want it done.
Thanks to everyone for their contribution.
Frank.
Frank Cazabon
On 12/10/2018 10:48 AM, Alan Bourke wrote:
Easy for the staff to count, or difficult for
Easy for the staff to count, or difficult for the opposition to count. Pick one.
--
Alan Bourke
alanpbourke (at) fastmail (dot) fm
___
Post Messages to: ProFox@leafe.com
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
Thanks for the suggestion
Frank.
Frank Cazabon
On 11/10/2018 02:56 PM, Joe Yoder wrote:
How about converting to base 26 and printing alpha characters (A-Z)? This
would allow easy sequencing and a simple program could convert an alpha
string to a base 10 number when needed.- Joe
On Thu, Oct
How about converting to base 26 and printing alpha characters (A-Z)? This
would allow easy sequencing and a simple program could convert an alpha
string to a base 10 number when needed.- Joe
On Thu, Oct 11, 2018 at 2:39 PM Frank Cazabon
wrote:
> They have that already. This is a physical
They have that already. This is a physical count process to avoid theft. They
deal in lending money for gold and have to be paranoid.
On 11 October 2018 14:10:36 GMT-04:00, Stephen Russell
wrote:
>Why not make a dashboard that has a Count for the Day on it. If you
>have
>really simple people
Why not make a dashboard that has a Count for the Day on it. If you have
really simple people this might work?
On Thu, Oct 11, 2018 at 9:54 AM Frank Cazabon
wrote:
> Thanks, Obscuring the number is not a problem, but I think they want to
> be able to read the number off the ticket at the end of
so to improve this solution : print the time and then add the sequential number
as milliseconds such as :
172543.124 : the ticket has been printed at 17h25m43s and is the 124th ...
The Foxil
Le 11/10/2018 à 17:12, Frank Cazabon a écrit :
That may work!
Frank.
Frank Cazabon
On 11/10/2018
What I would do: at a 3digt random prefix and a 2 digit random suffix to
your seq number of fixed lengte.
So you will end up with something like 45600198
67000261
45800377
Aso
If you print the list like this you will see at one glance the seq number
but your competetiors are not Abel to see that
LOL!
Frank.
Frank Cazabon
On 11/10/2018 11:06 AM, Ted Roche wrote:
On Thu, Oct 11, 2018 at 10:54 AM Frank Cazabon
wrote:
Thanks, Obscuring the number is not a problem, but I think they want to
be able to read the number off the ticket at the end of the day in
sequential order and I don't
That may work!
Frank.
Frank Cazabon
On 11/10/2018 10:59 AM, Vassilis Aggelakos wrote:
Try to put the real number between two 1 single digit other numbers. For
example 3452 --> 3=dummy 45 = real sequence 2--> dummy.
No math needed, just this little trick!
Hope this helps.
On Thu, Oct 11,
Thanks
Frank.
Frank Cazabon
On 10/10/2018 06:45 PM, Charles Hart Enzer, M.D. wrote:
How about table with two columns in an Array:
- Column One is sequential by one
- Column Two is generated by Random Number Generator with IF THEN
- If Random Number Exists, reGenerate
-
If you want it a bit more sophisticated, the last digit it could denote how
many digits are dummy in the begining.
E.g: 45672 --> 45=dummy --> 67 real number and 2 dummy indicator.
On Thu, Oct 11, 2018 at 6:03 PM Ed Leafe wrote:
> On Oct 11, 2018, at 9:59 AM, Vassilis Aggelakos
> wrote:
> >
>
They actually have barcodes on the ticket but never use the scanners to
actually read them, they just read the number (printed below the bar code).
Frank.
Frank Cazabon
On 10/10/2018 06:19 PM, Mike wrote:
Print the sequential number using a barcode font. If a customer has a
barcode scanner,
The people in the know memorize the rebus. But you mentioned nobody wants to
think so...
--
rk
-Original Message-
From: ProfoxTech On Behalf Of Frank Cazabon
Sent: Thursday, October 11, 2018 10:54 AM
To: profoxt...@leafe.com
Subject: Re: Numbering Scheme
Thanks, Obscuring the number
That's along the lines of what I think needs to be done but not sure if
my client will be happy with it. Only way to find out is to ask.
Frank.
Frank Cazabon
On 10/10/2018 06:18 PM, Paul H. Tarver wrote:
How about a simple character substitution routine like this:
Original # String:
On Thu, Oct 11, 2018 at 10:54 AM Frank Cazabon
wrote:
> Thanks, Obscuring the number is not a problem, but I think they want to
> be able to read the number off the ticket at the end of the day in
> sequential order and I don't see how I can come up with a simple way to
> do this.
>
Invisible
I would guess they are more concerned about overestimating, but that's
just a WAG.
Frank.
Frank Cazabon
On 11/10/2018 10:55 AM, Alan Bourke wrote:
Do you care more about competitors overestimating or underestimating the amount
of business being done?
On Oct 11, 2018, at 9:59 AM, Vassilis Aggelakos wrote:
>
> Try to put the real number between two 1 single digit other numbers. For
> example 3452 --> 3=dummy 45 = real sequence 2--> dummy.
>
> No math needed, just this little trick!
This is the best solution so far! You could use multiple
On 10/10/2018 03:41 PM, Eric Selje wrote:
What difference does it make if the competition knows how much business
you're doing?
I really couldn't say. They seem to "spy" on their competitors this way
and think their competitors also do it to them. I really don't
understand their reasoning,
This is for their end of day process and they want to be able to count
the number of tickets and match the number of parcels and then be able
to match them in sequential order. They also store the parcels in a
vault in sequential order so that when the customer comes back for their
parcel it's
Try to put the real number between two 1 single digit other numbers. For
example 3452 --> 3=dummy 45 = real sequence 2--> dummy.
No math needed, just this little trick!
Hope this helps.
On Thu, Oct 11, 2018 at 5:55 PM Alan Bourke wrote:
> Do you care more about competitors overestimating or
Do you care more about competitors overestimating or underestimating the amount
of business being done?
--
Alan Bourke
alanpbourke (at) fastmail (dot) fm
___
Post Messages to: ProFox@leafe.com
Subscription Maintenance:
Thanks, Obscuring the number is not a problem, but I think they want to
be able to read the number off the ticket at the end of the day in
sequential order and I don't see how I can come up with a simple way to
do this.
Frank.
Frank Cazabon
On 10/10/2018 03:48 PM, Richard Kaye wrote:
One
That would still involve some thought on the users part (and they don't
think at all).
Frank.
Frank Cazabon
On 10/10/2018 03:46 PM, Vassilis Aggelakos wrote:
Multiply the number by 3.
Vassilis
On 10 Oct 2018, at 22:42, Ted Roche wrote:
Keep a table with the primary key (a
They have a barcode on the ticket, but we also print the number. They
(for whatever reason) found that using the barcode was too hard.
A QR code won't make it any easier. :(
Frank.
Frank Cazabon
On 10/10/2018 05:35 PM, Stephen Russell wrote:
01 =1 10=2
Why not print a QR Barcode and stick
True, but they would need several invoices to compare...which means
they're "looking" for a sequence and not just "noticing".
Mike
Paul Hill wrote:
On Wed, 10 Oct 2018 at 23:19, Mike wrote:
Print the sequential number using a barcode font. If a customer has a
barcode scanner, they can
On Wed, 10 Oct 2018 at 23:19, Mike wrote:
>
> Print the sequential number using a barcode font. If a customer has a
> barcode scanner, they can "see" the number, but they'd have to be
> looking pretty hard.
Or they could just use their phone.
--
Paul
How about table with two columns in an Array:
- Column One is sequential by one
- Column Two is generated by Random Number Generator with IF THEN
- If Random Number Exists, reGenerate
- Assign numbers to items from Column Two
Instead of an Array, create a Table to be used --
How about a simple character substitution routine like this:
Original # String: '0123456789'
Substitution String : '2546890313'
Create a simple routine to take a number as a string, do a character by
character substitution and return the "encoded" Ticket #
Ticket #: 12345 would be printed on
Print the sequential number using a barcode font. If a customer has a
barcode scanner, they can "see" the number, but they'd have to be
looking pretty hard. Meanwhile, an $80 barcode scanner (USB connection)
on the office computer would let them read the sequential number.
Mike Copeland
01 =1 10=2
Why not print a QR Barcode and stick the number in there instead?
On Wed, Oct 10, 2018 at 4:24 PM Frank Cazabon
wrote:
> But how will the staff be able to read the binary numbers off the ticket
> and know it's in sequence?
>
> On 10 October 2018 15:33:10 GMT-04:00, Stephen Russell
So effectively display one number on the ticket but when it comes to checking,
run a report displaying the sequential numbers and the random/nonsense number?
On 10 October 2018 15:42:30 GMT-04:00, Ted Roche wrote:
>Keep a table with the primary key (a non-data-bearing auto-incremented
>integer)
But how will the staff be able to read the binary numbers off the ticket and
know it's in sequence?
On 10 October 2018 15:33:10 GMT-04:00, Stephen Russell
wrote:
>Go binary! 10010110101 They are kicking ass today!
>
>
>On Wed, Oct 10, 2018 at 2:26 PM Frank Cazabon
>wrote:
>
>> I have a
Do you have
1) a specific report for the customer ticket
2) can you can add a sequential number on to the above for the internal
copy?
3) a parcel label that can have a ticket number and the sequential number
on it?
It would mean the two people would need to come back and get the parcel,
Multiply the number by 3.
Vassilis
> On 10 Oct 2018, at 22:25, Frank Cazabon wrote:
>
> I have a client who issues tickets in numerical sequence (it's a pawnshop).
> The sequence helps them balance things back at the end of the day (read that
> as check for stealing) when checking the
One way is to come up with a 10 letter "word" with each letter representing a
digit. You then convert the numeric sequence to alpha characters. And to avoid
the pattern being too easily spotted, add one or more random characters to the
final string. It's not the most robust encryption scheme
Multiply the number by 3.
Vassilis
> On 10 Oct 2018, at 22:42, Ted Roche wrote:
>
> Keep a table with the primary key (a non-data-bearing auto-incremented
> integer) as the sequential number, to ensure things don't go missing out of
> sequence.
>
> For each ticket, create a unique number
Keep a table with the primary key (a non-data-bearing auto-incremented
integer) as the sequential number, to ensure things don't go missing out of
sequence.
For each ticket, create a unique number that's not already in the table.
Use the random functions to generate a mix of numbers and letters,
ROFL.
John Weller
01380 723235
07976 393631
Go binary! 10010110101 They are kicking ass today!
___
Post Messages to: ProFox@leafe.com
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list:
Or Hex?
What difference does it make if the competition knows how much business
you're doing?
E
On Wed, Oct 10, 2018 at 2:33 PM Stephen Russell
wrote:
> Go binary! 10010110101 They are kicking ass today!
>
>
> On Wed, Oct 10, 2018 at 2:26 PM Frank Cazabon
> wrote:
>
> > I have a client who
Go binary! 10010110101 They are kicking ass today!
On Wed, Oct 10, 2018 at 2:26 PM Frank Cazabon
wrote:
> I have a client who issues tickets in numerical sequence (it's a
> pawnshop). The sequence helps them balance things back at the end of the
> day (read that as check for stealing) when
42 matches
Mail list logo
