Barcode Question

[system]

Chris,

I did a ton of testing over the last couple of days on our barcode
scanner. I concluded this morning that in fact it is not our scanner,
but MES. There are differing results based on which computer we are
using. On my computer it works flawlessly, but I still get errors on
other computers. I tested it on four other computers around our plant
and found that my computer is the only one that doesn't have a
problem. I tried everything I could think of to try to get it to fail
on my workstation (i.e. scanning in motion, at an angle, and dead on)
and it still worked every time. I have made no changes to my MES
because I haven't figure out how to customize it.

I must add that it doesn't fail every time I try it on other
computers. Yet, it is still very very inconsistent (fails 90% of the
time). I decided to open a call with Epicor Support to see what they
say about it. I will let you know if they give some good information
on why this is happening.

Eric


--- In vantage@yahoogroups.com, Chris Thompson <chriselectrix@...>
wrote:

>
> Hi Eric,
>
> I would go for 2D scanners when it is time to upgrade.
>
> They are much more accurate and faster than 1D scanners.
>
> Cheers,
>
>
> CHRIS
>
>
>
>
> ________________________________
> From: homestyleindustries <homestyleindustries@...>
> To: vantage@yahoogroups.com
> Sent: Thursday, December 4, 2008 3:49:17 PM
> Subject: [Vantage] Re: Barcode Question
>
>
> Chris,
>
> Yes it does work for all operations. I also figure out that part of
> our problem is the scanner device itself. It is really picky about
> having the laser straight across the barcode. Thanks again for your
> help.
>
> Eric
>
> --- In vantage@yahoogroups .com, Chris Thompson <chriselectrix@ ...>
> wrote:
> >
> > Eric,
> >
> > Does that work on all of your Opr Seq?
> >
> > I can't take all of the credit .... but I will!!
> >
> > Cheers,
> >
> >
> > CHRIS
> >
> >
> >
> >
> > ____________ _________ _________ __
> > From: homestyleindustries <homestyleindustrie s@...>
> > To: vantage@yahoogroups .com
> > Sent: Wednesday, December 3, 2008 3:50:13 PM
> > Subject: [Vantage] Re: Barcode Question
> >
> >
> > Chris,
> >
> > You are a genius. Thank you.
> >
> > Eric
> >
> > --- In vantage@yahoogroups ..com, Chris Thompson <chriselectrix@
> ...>
> > wrote:
> > >
> > > Hi Eric & Tony,
> > >
> > > I believe I may have a solution to all of our problems!!
> > >
> > > Ok, the problem appears to be the auto fill function as pointed
> out
> > by Tony.
> > >
> > > When the scanner scans ie 10, it scans 1 then auto fills the 0

to

> > make ten but then when it it reads the zero (from the original

ten)

> > for some reason it adds it on the end so scan 10 = scan 1, auto

fill

> > 10, add 0 = 100.
> > >
> > > What I have done which seems to have fixed the problem

(certainly

> on
> > my traveller) is to use
> > >
> > > "*"&ToText({ JobOper.OprSeq} ,"0")&"$H" &"$I"&"*" ....
> > >
> > > obviously you will have to add you job no. and asm to the
> beginning
> > if you want one code to do everything,
> > >
> > > Basically, I have added a $H before the final $I (TAB) which is
> the
> > full ascii key for 'Delete' not 'Backspace', which will delete the
> > character after the cursor where backspace would delete the
> character
> > to the left of the cursor.
> > >
> > > I have tried opr seq 10 - 100 and this works well.
> > >
> > > I would be interested if this fixes your problems, because at
> > present it looks as if it has fixed our problem.
> > >
> > > I would suggest using ToText as the code is shorter and it works
> the
> > same.
> > >
> > > Cheers,
> > >
> > >
> > >
> > > CHRIS
> > >
> > >
> > >
> > >
> > > ____________ _________ _________ __
> > > From: Chris Thompson <chriselectrix@ ...>
> > > To: vantage@yahoogroups .com
> > > Sent: Wednesday, December 3, 2008 2:32:45 PM
> > > Subject: Re: [Vantage] Re: Barcode Question
> > >
> > >
> > > Hi,
> > >
> > > That sounds great - but how do I do it?
> > >
> > > Thanks,
> > >
> > > CHRIS
> > >
> > > ____________ _________ _________ __
> > > From: bw2868bond <bwalker@adcocircui t s.com>
> > > To: vantage@yahoogroups .com
> > > Sent: Wednesday, December 3, 2008 2:00:26 PM
> > > Subject: [Vantage] Re: Barcode Question
> > >
> > > Try setting the AutoEdit property to false (if not available in
> > > designer propeties, it will have to be done in code)
> > >
> > > here is a description of the property:
> > >
> > > public bool AutoEdit { set; get; }
> > > Member of Infragistics. Win.UltraWinGrid .UltraCombo
> > >
> > > Summary:
> > > Determines if the combo will support automatic value completion.
> > > (Default is true).
> > >
> > > Remarks:
> > > Setting the AutoEdit property to True will enable automatic edit
> > > value completion for the text area of the combo, based on the
> values
> > > in the value list.. When AutoEdit is True and the user types a
> > > character in the combo's text box, the control will search the
> > > contents of the
> > > Infragistics. Win..UltraWinGrid .UltraDropDownBa

se.DisplayMember

> > column
> > > to see if it contains a value that begins with the same

character.

> > If
> > > it does, this value will appear in the text box, with all of its
> > > characters highlighted except the one that the user typed. If

the

> > > user types a second character, the control will check to see if

it

> > is
> > > the next highlighted character is in the value that appeared. If
> it
> > > is, the value stays and the character typed becomes deselected.

If

> > > the second character does not appear in the value, the control
> > > searches the list again for a value that begins with the first

two

> > > characters that were typed. If one exists, it appears in the

text

> > > box; otherwise the selected text is removed and no more

searching

> > > takes place. This process continues until the user shifts the
> input
> > > focus away from the control. If the UltraCombo's
> > > Infragistics. Win.UltraWinGrid .UltraCombo. DropDownStyle has

been

> > set
> > > to DropDownList, then setting the AutoEdit to true will enable
> > multi-
> > > character auto-edit functionality for the drop down list style.

In

> > > multi-character auto-edit mode, the control will select the item
> > > whose text starts with characters typed so far. After 500
> > > milliseconds of time span since last keystroke, a new auto-edit
> > > session begins where the previously typed characters are

discarded

> > > and new characters are used for multi-character matching.
> > >
> > > --- In vantage@yahoogroups .com, Tony Hughes <thughes281@ ...>
> > wrote:
> > > >
> > > >
> > > > I think the problem you are both seeing is that the combo box

on

> > > the Vantage form is "helpfully" suggesting for you.
> > > > This was why we had to take the concatenated JOB+ASM+OPR

barcode

> > > out of our traveler, for just this reason.
> > > >
> > > > What happens is, after you scan the Job number, the Assembly

and

> > > Operation combo boxes refresh their dataset to reflect what
> > > assemblies and operations are valid for the scanned Job number.
> > > >
> > > > Say your job has operations 10 through 150.
> > > > Remembering that a barcode is nothing magical, just literally
> > > keystrokes, your Tab moves the focus to the Opr dropdown.
> > > > Your code types 1. as soon as it does the 1, the combobox
> > > suggests "10" so now, even though you have typed 1, the value in
> the
> > > combo box is now 10. So now your barcode sends the 0, but of
> course
> > 0
> > > appended to 10 is now 100.
> > > > That's why you see the 100.
> > > >
> > > > You are not doing anything wrong.
> > > >
> > > > I am sure there is a way to tell the @#$%^& combo box to stop
> > > suggesting, but I don't know how. If you figure that out, and

are

> in
> > > the Houston area anytime soon, I will buy you a beer.
> > > >
> > > >
> > > >
> > > >
> > > > ____________ _________ _________ __
> > > > From: Chris Thompson <chriselectrix@ ....>
> > > > To: vantage@yahoogroups .com
> > > > Sent: Wednesday, December 3, 2008 5:28:54 AM
> > > > Subject: Re: [Vantage] Re: Barcode Question
> > > >
> > > >
> > > > Hi Eric,
> > > >
> > > > I have had the exact same problem recently.
> > > >
> > > > I was using "*" & ToText({JobOper. OprSeq}," 0") & "$I" & "*"
> > > >
> > > > I was having trouble with operation 10 where it was scanning

it

> as
> > > 100, but all of the others were ok.
> > > >
> > > > If I scanned our code into word or excel etc it would scan as
> 10,
> > > so this pointed the problem to Vantage.
> > > >
> > > > I have also tried "*" & ToText({JobOper. OprSeq}," 0.00" & "."
> > > & "$I" & "*" but that doesn't work.
> > > >
> > > > Secondly, I have found that to format a number field within a
> > > formula, it works better if you use e.g. ({number.field} ,"0").

I

> > > believe, but I could be wrong that if you put i.e.
> > > ({number.field} ,"0,000.00" ) the number will format i.e.
> 1,234.56.
> > > >
> > > > I must say, I started writing this email thinking that I had
> > sorted
> > > the problem myself, but now that I have tested it again, it
> doesn't
> > > work.
> > > >
> > > > Have you tried scanning the suspect numbers into Excel or Word
> to
> > > see if they scan alright?
> > > >
> > > > Also have you tried leaving the TAB off at the end of the
> barcode?
> > > >
> > > > Also, I don't think this will may any difference, but when I
> used
> > > cstr, it made by barcode much bigger than my barcode was when I
> was
> > > using ToText and as far as I am aware they do the same thing, so
> if
> > > space is an issue in your design, ToText may be a good solution.
> > > >
> > > > If you find a solution, I would be greatful if you could pass

it

> > on.
> > > >
> > > > I am going to ask Epicor to have a look in the meantime.
> > > >
> > > > Thanks,
> > > >
> > > > CHRIS
> > > >
> > > > ____________ _________ _________ __
> > > > From: homestyleindustries <homestyleindustrie s @...>
> > > > To: vantage@yahoogroups .com
> > > > Sent: Tuesday, December 2, 2008 11:58:50 PM
> > > > Subject: [Vantage] Re: Barcode Question
> > > >
> > > > After some more testing we figured out that the ,0 has no

effect

> > > > outside of leaving the decimal places off. I took out the ,0

out

> > > and
> > > > it still populated the operation sequence number as 700, whith
> two
> > > > decimal places obviously. So, new question is why would

Vantage

> > > bring
> > > > in last operation of a job with an extra 0? I tried this on
> > > multiple
> > > > jobs and had the same results.
> > > >
> > > > --- In vantage@yahoogroups .com, "homestyleindustrie s"
> > > > <homestyleindustrie s@...> wrote:
> > > > >
> > > > > Here is my problem:
> > > > >
> > > > > I have a job with 6 operations. I created a formula to
> populate
> > > > > barcodes for each operation to be used with MES. The formula
> is:
> > > > >
> > > > > "*" + {JobHead.JobNum} + "$I" + cstr({JobAsmbl. AssemblySeq}

)

> > > + "$I"
> > > > +
> > > > > cstr({JobOper. OprSeq},0) + "$I" + "*"
> > > > >
> > > > > I have tried a number of different formulas and this seems

to

> > > work
> > > > the
> > > > > best. Yet, for whatever reason on the very last operation it
> > adds
> > > > an
> > > > > extra 0 to the Operation Sequence Number. I figure this is
> > > > populating
> > > > > the irregularity from the (JobOper.OprSeq} ,0). My
> understanding
> > > is
> > > > > that the ,0 is suppose to leave off the decimal places,

which

> it
> > > > does.
> > > > > With that said, my question is how do I fix this? How can I
> get
> > > it
> > > > to
> > > > > populate operation 60 instead of 600, while keeping the
> decimal
> > > > places
> > > > > off?
> > > > >
> > > > > Thanks in advance.
> > > > >
> > > > > Eric
> > > > >
> > > >
> > > > [Non-text portions of this message have been removed]
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > [Non-text portions of this message have been removed]
> > > >
> > >
> > > [Non-text portions of this message have been removed]
> > >
> > >
> > >
> > >
> > >
> > >
> > > [Non-text portions of this message have been removed]
> > >
> >
> >
> >
> >
> >
> >
> > [Non-text portions of this message have been removed]
> >
>
>
>
>
>
>
> [Non-text portions of this message have been removed]
>

[system]

Here is my problem:

I have a job with 6 operations. I created a formula to populate
barcodes for each operation to be used with MES. The formula is:

"*" + {JobHead.JobNum} + "$I" + cstr({JobAsmbl.AssemblySeq}) + "$I" +
cstr({JobOper.OprSeq},0) + "$I" + "*"

I have tried a number of different formulas and this seems to work the
best. Yet, for whatever reason on the very last operation it adds an
extra 0 to the Operation Sequence Number. I figure this is populating
the irregularity from the (JobOper.OprSeq},0). My understanding is
that the ,0 is suppose to leave off the decimal places, which it does.
With that said, my question is how do I fix this? How can I get it to
populate operation 60 instead of 600, while keeping the decimal places
off?

Thanks in advance.

Eric

[system]

After some more testing we figured out that the ,0 has no effect
outside of leaving the decimal places off. I took out the ,0 out and
it still populated the operation sequence number as 700, whith two
decimal places obviously. So, new question is why would Vantage bring
in last operation of a job with an extra 0? I tried this on multiple
jobs and had the same results.




--- In vantage@yahoogroups.com, "homestyleindustries"
<homestyleindustries@...> wrote:

>
> Here is my problem:
>
> I have a job with 6 operations. I created a formula to populate
> barcodes for each operation to be used with MES. The formula is:
>
> "*" + {JobHead.JobNum} + "$I" + cstr({JobAsmbl.AssemblySeq}) + "$I"

+

> cstr({JobOper.OprSeq},0) + "$I" + "*"
>
> I have tried a number of different formulas and this seems to work

the

> best. Yet, for whatever reason on the very last operation it adds

an

> extra 0 to the Operation Sequence Number. I figure this is

populating

> the irregularity from the (JobOper.OprSeq},0). My understanding is
> that the ,0 is suppose to leave off the decimal places, which it

does.

> With that said, my question is how do I fix this? How can I get it

to

> populate operation 60 instead of 600, while keeping the decimal

places

> off?
>
> Thanks in advance.
>
> Eric
>

[system]

Hi Eric,

I have had the exact same problem recently.

I was using "*" & ToText({JobOper.OprSeq},"0") & "$I" & "*"

I was having trouble with operation 10 where it was scanning it as 100, but all of the others were ok.

If I scanned our code into word or excel etc it would scan as 10, so this pointed the problem to Vantage.

I have also tried "*" & ToText({JobOper.OprSeq},"0.00" & "." & "$I" & "*" but that doesn't work.

Secondly, I have found that to format a number field within a formula, it works better if you use e.g. ({number.field},"0"). I believe, but I could be wrong that if you put i.e. ({number.field},"0,000.00") the number will format i.e. 1,234.56.


I must say, I started writing this email thinking that I had sorted the problem myself, but now that I have tested it again, it doesn't work.

Have you tried scanning the suspect numbers into Excel or Word to see if they scan alright?

Also have you tried leaving the TAB off at the end of the barcode?

Also, I don't think this will may any difference, but when I used cstr, it made by barcode much bigger than my barcode was when I was using ToText and as far as I am aware they do the same thing, so if space is an issue in your design, ToText may be a good solution.

If you find a solution, I would be greatful if you could pass it on.

I am going to ask Epicor to have a look in the meantime.

Thanks,



CHRIS




________________________________
From: homestyleindustries <homestyleindustries@...>
To: vantage@yahoogroups.com
Sent: Tuesday, December 2, 2008 11:58:50 PM
Subject: [Vantage] Re: Barcode Question


After some more testing we figured out that the ,0 has no effect
outside of leaving the decimal places off. I took out the ,0 out and
it still populated the operation sequence number as 700, whith two
decimal places obviously. So, new question is why would Vantage bring
in last operation of a job with an extra 0? I tried this on multiple
jobs and had the same results.

--- In vantage@yahoogroups .com, "homestyleindustrie s"
<homestyleindustrie s@...> wrote:

>
> Here is my problem:
>
> I have a job with 6 operations. I created a formula to populate
> barcodes for each operation to be used with MES. The formula is:
>
> "*" + {JobHead.JobNum} + "$I" + cstr({JobAsmbl. AssemblySeq} ) + "$I"

+

> cstr({JobOper. OprSeq},0) + "$I" + "*"
>
> I have tried a number of different formulas and this seems to work

the

> best. Yet, for whatever reason on the very last operation it adds

an

> extra 0 to the Operation Sequence Number. I figure this is

populating

> the irregularity from the (JobOper.OprSeq} ,0). My understanding is
> that the ,0 is suppose to leave off the decimal places, which it

does.

> With that said, my question is how do I fix this? How can I get it

to

> populate operation 60 instead of 600, while keeping the decimal

places

> off?
>
> Thanks in advance.
>
> Eric
>

[Non-text portions of this message have been removed]

[system]

I think the problem you are both seeing is that the combo box on the Vantage form is "helpfully" suggesting for you.
This was why we had to take the concatenated JOB+ASM+OPR barcode out of our traveler, for just this reason.

What happens is, after you scan the Job number, the Assembly and Operation combo boxes refresh their dataset to reflect what assemblies and operations are valid for the scanned Job number.

Say your job has operations 10 through 150.
Remembering that a barcode is nothing magical, just literally keystrokes, your Tab moves the focus to the Opr dropdown.
Your code types 1. as soon as it does the 1, the combobox suggests "10" so now, even though you have typed 1, the value in the combo box is now 10. So now your barcode sends the 0, but of course 0 appended to 10 is now 100.
That's why you see the 100.

You are not doing anything wrong.

I am sure there is a way to tell the @#$%^& combo box to stop suggesting, but I don't know how. If you figure that out, and are in the Houston area anytime soon, I will buy you a beer.




________________________________
From: Chris Thompson <chriselectrix@...>
To: vantage@yahoogroups.com
Sent: Wednesday, December 3, 2008 5:28:54 AM
Subject: Re: [Vantage] Re: Barcode Question


Hi Eric,

I have had the exact same problem recently.

I was using "*" & ToText({JobOper. OprSeq}," 0") & "$I" & "*"

I was having trouble with operation 10 where it was scanning it as 100, but all of the others were ok.

If I scanned our code into word or excel etc it would scan as 10, so this pointed the problem to Vantage.

I have also tried "*" & ToText({JobOper. OprSeq}," 0.00" & "." & "$I" & "*" but that doesn't work.

Secondly, I have found that to format a number field within a formula, it works better if you use e.g. ({number.field} ,"0"). I believe, but I could be wrong that if you put i.e. ({number.field} ,"0,000.00" ) the number will format i.e. 1,234.56.

I must say, I started writing this email thinking that I had sorted the problem myself, but now that I have tested it again, it doesn't work.

Have you tried scanning the suspect numbers into Excel or Word to see if they scan alright?

Also have you tried leaving the TAB off at the end of the barcode?

Also, I don't think this will may any difference, but when I used cstr, it made by barcode much bigger than my barcode was when I was using ToText and as far as I am aware they do the same thing, so if space is an issue in your design, ToText may be a good solution.

If you find a solution, I would be greatful if you could pass it on.

I am going to ask Epicor to have a look in the meantime.

Thanks,

CHRIS

____________ _________ _________ __
From: homestyleindustries <homestyleindustries @...>
To: vantage@yahoogroups .com
Sent: Tuesday, December 2, 2008 11:58:50 PM
Subject: [Vantage] Re: Barcode Question

After some more testing we figured out that the ,0 has no effect
outside of leaving the decimal places off. I took out the ,0 out and
it still populated the operation sequence number as 700, whith two
decimal places obviously. So, new question is why would Vantage bring
in last operation of a job with an extra 0? I tried this on multiple
jobs and had the same results.

--- In vantage@yahoogroups .com, "homestyleindustrie s"
<homestyleindustrie s@...> wrote:

>
> Here is my problem:
>
> I have a job with 6 operations. I created a formula to populate
> barcodes for each operation to be used with MES. The formula is:
>
> "*" + {JobHead.JobNum} + "$I" + cstr({JobAsmbl. AssemblySeq} ) + "$I"

+

> cstr({JobOper. OprSeq},0) + "$I" + "*"
>
> I have tried a number of different formulas and this seems to work

the

> best. Yet, for whatever reason on the very last operation it adds

an

> extra 0 to the Operation Sequence Number. I figure this is

populating

> the irregularity from the (JobOper.OprSeq} ,0). My understanding is
> that the ,0 is suppose to leave off the decimal places, which it

does.

> With that said, my question is how do I fix this? How can I get it

to

> populate operation 60 instead of 600, while keeping the decimal

places

> off?
>
> Thanks in advance.
>
> Eric
>

[Non-text portions of this message have been removed]






[Non-text portions of this message have been removed]

[system]

Try setting the AutoEdit property to false (if not available in
designer propeties, it will have to be done in code)

here is a description of the property:

public bool AutoEdit { set; get; }
Member of Infragistics.Win.UltraWinGrid.UltraCombo

Summary:
Determines if the combo will support automatic value completion.
(Default is true).

Remarks:
Setting the AutoEdit property to True will enable automatic edit
value completion for the text area of the combo, based on the values
in the value list. When AutoEdit is True and the user types a
character in the combo's text box, the control will search the
contents of the
Infragistics.Win.UltraWinGrid.UltraDropDownBase.DisplayMember column
to see if it contains a value that begins with the same character. If
it does, this value will appear in the text box, with all of its
characters highlighted except the one that the user typed. If the
user types a second character, the control will check to see if it is
the next highlighted character is in the value that appeared. If it
is, the value stays and the character typed becomes deselected. If
the second character does not appear in the value, the control
searches the list again for a value that begins with the first two
characters that were typed. If one exists, it appears in the text
box; otherwise the selected text is removed and no more searching
takes place. This process continues until the user shifts the input
focus away from the control. If the UltraCombo's
Infragistics.Win.UltraWinGrid.UltraCombo.DropDownStyle has been set
to DropDownList, then setting the AutoEdit to true will enable multi-
character auto-edit functionality for the drop down list style. In
multi-character auto-edit mode, the control will select the item
whose text starts with characters typed so far. After 500
milliseconds of time span since last keystroke, a new auto-edit
session begins where the previously typed characters are discarded
and new characters are used for multi-character matching.

--- In vantage@yahoogroups.com, Tony Hughes <thughes281@...> wrote:
>
>
> I think the problem you are both seeing is that the combo box on
the Vantage form is "helpfully" suggesting for you.
> This was why we had to take the concatenated JOB+ASM+OPR barcode
out of our traveler, for just this reason.
>
> What happens is, after you scan the Job number, the Assembly and
Operation combo boxes refresh their dataset to reflect what
assemblies and operations are valid for the scanned Job number.
>
> Say your job has operations 10 through 150.
> Remembering that a barcode is nothing magical, just literally
keystrokes, your Tab moves the focus to the Opr dropdown.
> Your code types 1. as soon as it does the 1, the combobox
suggests "10" so now, even though you have typed 1, the value in the
combo box is now 10. So now your barcode sends the 0, but of course 0
appended to 10 is now 100.
> That's why you see the 100.
>
> You are not doing anything wrong.
>
> I am sure there is a way to tell the @#$%^& combo box to stop
suggesting, but I don't know how. If you figure that out, and are in
the Houston area anytime soon, I will buy you a beer.
>
>
>
>
> ________________________________
> From: Chris Thompson <chriselectrix@...>
> To: vantage@yahoogroups.com
> Sent: Wednesday, December 3, 2008 5:28:54 AM
> Subject: Re: [Vantage] Re: Barcode Question
>
>
> Hi Eric,
>
> I have had the exact same problem recently.
>
> I was using "*" & ToText({JobOper. OprSeq}," 0") & "$I" & "*"
>
> I was having trouble with operation 10 where it was scanning it as
100, but all of the others were ok.
>
> If I scanned our code into word or excel etc it would scan as 10,
so this pointed the problem to Vantage.
>
> I have also tried "*" & ToText({JobOper. OprSeq}," 0.00" & "."
& "$I" & "*" but that doesn't work.
>
> Secondly, I have found that to format a number field within a
formula, it works better if you use e.g. ({number.field} ,"0"). I
believe, but I could be wrong that if you put i.e.
({number.field} ,"0,000.00" ) the number will format i.e. 1,234.56.
>
> I must say, I started writing this email thinking that I had sorted
the problem myself, but now that I have tested it again, it doesn't
work.
>
> Have you tried scanning the suspect numbers into Excel or Word to
see if they scan alright?
>
> Also have you tried leaving the TAB off at the end of the barcode?
>
> Also, I don't think this will may any difference, but when I used
cstr, it made by barcode much bigger than my barcode was when I was
using ToText and as far as I am aware they do the same thing, so if
space is an issue in your design, ToText may be a good solution.
>
> If you find a solution, I would be greatful if you could pass it on.
>
> I am going to ask Epicor to have a look in the meantime.
>
> Thanks,
>
> CHRIS
>
> ____________ _________ _________ __
> From: homestyleindustries <homestyleindustries @...>
> To: vantage@yahoogroups .com
> Sent: Tuesday, December 2, 2008 11:58:50 PM
> Subject: [Vantage] Re: Barcode Question
>
> After some more testing we figured out that the ,0 has no effect
> outside of leaving the decimal places off. I took out the ,0 out
and
> it still populated the operation sequence number as 700, whith two
> decimal places obviously. So, new question is why would Vantage
bring
> in last operation of a job with an extra 0? I tried this on
multiple
> jobs and had the same results.
>
> --- In vantage@yahoogroups .com, "homestyleindustrie s"
> <homestyleindustrie s@...> wrote:
> >
> > Here is my problem:
> >
> > I have a job with 6 operations. I created a formula to populate
> > barcodes for each operation to be used with MES. The formula is:
> >
> > "*" + {JobHead.JobNum} + "$I" + cstr({JobAsmbl. AssemblySeq} )
+ "$I"
> +
> > cstr({JobOper. OprSeq},0) + "$I" + "*"
> >
> > I have tried a number of different formulas and this seems to
work
> the
> > best. Yet, for whatever reason on the very last operation it adds
> an
> > extra 0 to the Operation Sequence Number. I figure this is
> populating
> > the irregularity from the (JobOper.OprSeq} ,0). My understanding
is
> > that the ,0 is suppose to leave off the decimal places, which it
> does.
> > With that said, my question is how do I fix this? How can I get
it
> to
> > populate operation 60 instead of 600, while keeping the decimal
> places
> > off?
> >
> > Thanks in advance.
> >
> > Eric
> >
>
> [Non-text portions of this message have been removed]
>
>
>
>
>
>
> [Non-text portions of this message have been removed]
>

[system]

Hi Tony,

Well I don't think I will be figuring it out and Im not in the Houston area, so I guess the beer is out of the question, unless there is a Houston in the UK I dont know about! :-)

What you suggest makes sense, but why would it only do it for certain numbers?

I had thought similar, because 20, 30 etc scan fine, but there isn't an operation 200 or 300..

However, Eric's problem was with operaion 70 out of 70 and all of the others were ok which seems to put a dampner on the theory.

However I have created a code which is literally *1* and that scans as 10 in MES, so now Im thinking of some kind of exceptions formula. But then again if Erics works all the way up to 70 then it doesnt sound like that be a fix.

I have one traveller with 10-100 opr seq so I figure this should work as follows:

The scanner reads 1 which auto populates to 10 and then adds the zero making 100 (because there is a valid option for 100).

However, on our example of 10-100, 10 always scans as ten.

I have tried adding a zero in front which doesnt work and also a . after which doesnt work.

I currently have Epicor looking into this for me as believe or not, 'nobody else has reported the problem' .... I seem to be the first to report so many problems, it's incredible :-)

I will keep you all posted if I get an answer. They are going to investigate if there is a way to turn off the autopopulate on the field in MES.

Cheers,


CHRIS




________________________________
From: Tony Hughes <thughes281@...>
To: vantage@yahoogroups.com
Sent: Wednesday, December 3, 2008 1:40:24 PM
Subject: Re: [Vantage] Re: Barcode Question



I think the problem you are both seeing is that the combo box on the Vantage form is "helpfully" suggesting for you.
This was why we had to take the concatenated JOB+ASM+OPR barcode out of our traveler, for just this reason.

What happens is, after you scan the Job number, the Assembly and Operation combo boxes refresh their dataset to reflect what assemblies and operations are valid for the scanned Job number.

Say your job has operations 10 through 150.
Remembering that a barcode is nothing magical, just literally keystrokes, your Tab moves the focus to the Opr dropdown.
Your code types 1. as soon as it does the 1, the combobox suggests "10" so now, even though you have typed 1, the value in the combo box is now 10. So now your barcode sends the 0, but of course 0 appended to 10 is now 100.
That's why you see the 100.

You are not doing anything wrong.

I am sure there is a way to tell the @#$%^& combo box to stop suggesting, but I don't know how. If you figure that out, and are in the Houston area anytime soon, I will buy you a beer.

____________ _________ _________ __
From: Chris Thompson <chriselectrix@ ymail.com>
To: vantage@yahoogroups .com
Sent: Wednesday, December 3, 2008 5:28:54 AM
Subject: Re: [Vantage] Re: Barcode Question

Hi Eric,

I have had the exact same problem recently..

I was using "*" & ToText({JobOper. OprSeq}," 0") & "$I" & "*"

I was having trouble with operation 10 where it was scanning it as 100, but all of the others were ok.

If I scanned our code into word or excel etc it would scan as 10, so this pointed the problem to Vantage.

I have also tried "*" & ToText({JobOper. OprSeq}," 0.00" & "." & "$I" & "*" but that doesn't work.

Secondly, I have found that to format a number field within a formula, it works better if you use e.g. ({number.field} ,"0"). I believe, but I could be wrong that if you put i.e. ({number.field} ,"0,000.00" ) the number will format i.e. 1,234.56.

I must say, I started writing this email thinking that I had sorted the problem myself, but now that I have tested it again, it doesn't work.

Have you tried scanning the suspect numbers into Excel or Word to see if they scan alright?

Also have you tried leaving the TAB off at the end of the barcode?

Also, I don't think this will may any difference, but when I used cstr, it made by barcode much bigger than my barcode was when I was using ToText and as far as I am aware they do the same thing, so if space is an issue in your design, ToText may be a good solution.

If you find a solution, I would be greatful if you could pass it on.

I am going to ask Epicor to have a look in the meantime.

Thanks,

CHRIS

____________ _________ _________ __
From: homestyleindustries <homestyleindustrie s @...>
To: vantage@yahoogroups .com
Sent: Tuesday, December 2, 2008 11:58:50 PM
Subject: [Vantage] Re: Barcode Question

After some more testing we figured out that the ,0 has no effect
outside of leaving the decimal places off. I took out the ,0 out and
it still populated the operation sequence number as 700, whith two
decimal places obviously. So, new question is why would Vantage bring
in last operation of a job with an extra 0? I tried this on multiple
jobs and had the same results.

--- In vantage@yahoogroups .com, "homestyleindustrie s"
<homestyleindustrie s@...> wrote:

>
> Here is my problem:
>
> I have a job with 6 operations. I created a formula to populate
> barcodes for each operation to be used with MES. The formula is:
>
> "*" + {JobHead.JobNum} + "$I" + cstr({JobAsmbl. AssemblySeq} ) + "$I"

+

> cstr({JobOper. OprSeq},0) + "$I" + "*"
>
> I have tried a number of different formulas and this seems to work

the

> best. Yet, for whatever reason on the very last operation it adds

an

> extra 0 to the Operation Sequence Number. I figure this is

populating

> the irregularity from the (JobOper.OprSeq} ,0). My understanding is
> that the ,0 is suppose to leave off the decimal places, which it

does.

> With that said, my question is how do I fix this? How can I get it

to

> populate operation 60 instead of 600, while keeping the decimal

places

> off?
>
> Thanks in advance.
>
> Eric
>

[Non-text portions of this message have been removed]

[Non-text portions of this message have been removed]






[Non-text portions of this message have been removed]

[system]

Hi,

That sounds great - but how do I do it?

Thanks,

CHRIS



________________________________
From: bw2868bond <bwalker@...>
To: vantage@yahoogroups.com
Sent: Wednesday, December 3, 2008 2:00:26 PM
Subject: [Vantage] Re: Barcode Question


Try setting the AutoEdit property to false (if not available in
designer propeties, it will have to be done in code)

here is a description of the property:

public bool AutoEdit { set; get; }
Member of Infragistics. Win.UltraWinGrid .UltraCombo

Summary:
Determines if the combo will support automatic value completion.
(Default is true).

Remarks:
Setting the AutoEdit property to True will enable automatic edit
value completion for the text area of the combo, based on the values
in the value list.. When AutoEdit is True and the user types a
character in the combo's text box, the control will search the
contents of the
Infragistics. Win..UltraWinGrid .UltraDropDownBa se.DisplayMember column
to see if it contains a value that begins with the same character. If
it does, this value will appear in the text box, with all of its
characters highlighted except the one that the user typed. If the
user types a second character, the control will check to see if it is
the next highlighted character is in the value that appeared. If it
is, the value stays and the character typed becomes deselected. If
the second character does not appear in the value, the control
searches the list again for a value that begins with the first two
characters that were typed. If one exists, it appears in the text
box; otherwise the selected text is removed and no more searching
takes place. This process continues until the user shifts the input
focus away from the control. If the UltraCombo's
Infragistics. Win.UltraWinGrid .UltraCombo. DropDownStyle has been set
to DropDownList, then setting the AutoEdit to true will enable multi-
character auto-edit functionality for the drop down list style. In
multi-character auto-edit mode, the control will select the item
whose text starts with characters typed so far. After 500
milliseconds of time span since last keystroke, a new auto-edit
session begins where the previously typed characters are discarded
and new characters are used for multi-character matching.

--- In vantage@yahoogroups .com, Tony Hughes <thughes281@ ...> wrote:
>
>
> I think the problem you are both seeing is that the combo box on
the Vantage form is "helpfully" suggesting for you.
> This was why we had to take the concatenated JOB+ASM+OPR barcode
out of our traveler, for just this reason.
>
> What happens is, after you scan the Job number, the Assembly and
Operation combo boxes refresh their dataset to reflect what
assemblies and operations are valid for the scanned Job number.
>
> Say your job has operations 10 through 150.
> Remembering that a barcode is nothing magical, just literally
keystrokes, your Tab moves the focus to the Opr dropdown.
> Your code types 1. as soon as it does the 1, the combobox
suggests "10" so now, even though you have typed 1, the value in the
combo box is now 10. So now your barcode sends the 0, but of course 0
appended to 10 is now 100.
> That's why you see the 100.
>
> You are not doing anything wrong.
>
> I am sure there is a way to tell the @#$%^& combo box to stop
suggesting, but I don't know how. If you figure that out, and are in
the Houston area anytime soon, I will buy you a beer.
>
>
>
>
> ____________ _________ _________ __
> From: Chris Thompson <chriselectrix@ ...>
> To: vantage@yahoogroups .com
> Sent: Wednesday, December 3, 2008 5:28:54 AM
> Subject: Re: [Vantage] Re: Barcode Question
>
>
> Hi Eric,
>
> I have had the exact same problem recently.
>
> I was using "*" & ToText({JobOper. OprSeq}," 0") & "$I" & "*"
>
> I was having trouble with operation 10 where it was scanning it as
100, but all of the others were ok.
>
> If I scanned our code into word or excel etc it would scan as 10,
so this pointed the problem to Vantage.
>
> I have also tried "*" & ToText({JobOper. OprSeq}," 0.00" & "."
& "$I" & "*" but that doesn't work.
>
> Secondly, I have found that to format a number field within a
formula, it works better if you use e.g. ({number.field} ,"0"). I
believe, but I could be wrong that if you put i.e.
({number.field} ,"0,000.00" ) the number will format i.e. 1,234.56.
>
> I must say, I started writing this email thinking that I had sorted
the problem myself, but now that I have tested it again, it doesn't
work.
>
> Have you tried scanning the suspect numbers into Excel or Word to
see if they scan alright?
>
> Also have you tried leaving the TAB off at the end of the barcode?
>
> Also, I don't think this will may any difference, but when I used
cstr, it made by barcode much bigger than my barcode was when I was
using ToText and as far as I am aware they do the same thing, so if
space is an issue in your design, ToText may be a good solution.
>
> If you find a solution, I would be greatful if you could pass it on.
>
> I am going to ask Epicor to have a look in the meantime.
>
> Thanks,
>
> CHRIS
>
> ____________ _________ _________ __
> From: homestyleindustries <homestyleindustrie s @...>
> To: vantage@yahoogroups .com
> Sent: Tuesday, December 2, 2008 11:58:50 PM
> Subject: [Vantage] Re: Barcode Question
>
> After some more testing we figured out that the ,0 has no effect
> outside of leaving the decimal places off. I took out the ,0 out
and
> it still populated the operation sequence number as 700, whith two
> decimal places obviously. So, new question is why would Vantage
bring
> in last operation of a job with an extra 0? I tried this on
multiple
> jobs and had the same results.
>
> --- In vantage@yahoogroups .com, "homestyleindustrie s"
> <homestyleindustrie s@...> wrote:
> >
> > Here is my problem:
> >
> > I have a job with 6 operations. I created a formula to populate
> > barcodes for each operation to be used with MES. The formula is:
> >
> > "*" + {JobHead.JobNum} + "$I" + cstr({JobAsmbl. AssemblySeq} )
+ "$I"
> +
> > cstr({JobOper. OprSeq},0) + "$I" + "*"
> >
> > I have tried a number of different formulas and this seems to
work
> the
> > best. Yet, for whatever reason on the very last operation it adds
> an
> > extra 0 to the Operation Sequence Number. I figure this is
> populating
> > the irregularity from the (JobOper.OprSeq} ,0). My understanding
is
> > that the ,0 is suppose to leave off the decimal places, which it
> does.
> > With that said, my question is how do I fix this? How can I get
it
> to
> > populate operation 60 instead of 600, while keeping the decimal
> places
> > off?
> >
> > Thanks in advance.
> >
> > Eric
> >
>
> [Non-text portions of this message have been removed]
>
>
>
>
>
>
> [Non-text portions of this message have been removed]
>






[Non-text portions of this message have been removed]

[system]

Hi Eric & Tony,

I believe I may have a solution to all of our problems!!

Ok, the problem appears to be the auto fill function as pointed out by Tony.

When the scanner scans ie 10, it scans 1 then auto fills the 0 to make ten but then when it it reads the zero (from the original ten) for some reason it adds it on the end so scan 10 = scan 1, auto fill 10, add 0 = 100.

What I have done which seems to have fixed the problem (certainly on my traveller) is to use

"*"&ToText({JobOper.OprSeq},"0")&"$H"&"$I"&"*" ....

obviously you will have to add you job no. and asm to the beginning if you want one code to do everything,

Basically, I have added a $H before the final $I (TAB) which is the full ascii key for 'Delete' not 'Backspace', which will delete the character after the cursor where backspace would delete the character to the left of the cursor.

I have tried opr seq 10 - 100 and this works well.

I would be interested if this fixes your problems, because at present it looks as if it has fixed our problem.

I would suggest using ToText as the code is shorter and it works the same.

Cheers,



CHRIS




________________________________
From: Chris Thompson <chriselectrix@...>
To: vantage@yahoogroups.com
Sent: Wednesday, December 3, 2008 2:32:45 PM
Subject: Re: [Vantage] Re: Barcode Question


Hi,

That sounds great - but how do I do it?

Thanks,

CHRIS

____________ _________ _________ __
From: bw2868bond <bwalker@adcocircuit s.com>
To: vantage@yahoogroups .com
Sent: Wednesday, December 3, 2008 2:00:26 PM
Subject: [Vantage] Re: Barcode Question

Try setting the AutoEdit property to false (if not available in
designer propeties, it will have to be done in code)

here is a description of the property:

public bool AutoEdit { set; get; }
Member of Infragistics. Win.UltraWinGrid .UltraCombo

Summary:
Determines if the combo will support automatic value completion.
(Default is true).

Remarks:
Setting the AutoEdit property to True will enable automatic edit
value completion for the text area of the combo, based on the values
in the value list.. When AutoEdit is True and the user types a
character in the combo's text box, the control will search the
contents of the
Infragistics. Win..UltraWinGrid .UltraDropDownBa se.DisplayMember column
to see if it contains a value that begins with the same character. If
it does, this value will appear in the text box, with all of its
characters highlighted except the one that the user typed. If the
user types a second character, the control will check to see if it is
the next highlighted character is in the value that appeared. If it
is, the value stays and the character typed becomes deselected. If
the second character does not appear in the value, the control
searches the list again for a value that begins with the first two
characters that were typed. If one exists, it appears in the text
box; otherwise the selected text is removed and no more searching
takes place. This process continues until the user shifts the input
focus away from the control. If the UltraCombo's
Infragistics. Win.UltraWinGrid .UltraCombo. DropDownStyle has been set
to DropDownList, then setting the AutoEdit to true will enable multi-
character auto-edit functionality for the drop down list style. In
multi-character auto-edit mode, the control will select the item
whose text starts with characters typed so far. After 500
milliseconds of time span since last keystroke, a new auto-edit
session begins where the previously typed characters are discarded
and new characters are used for multi-character matching.

--- In vantage@yahoogroups .com, Tony Hughes <thughes281@ ...> wrote:
>
>
> I think the problem you are both seeing is that the combo box on
the Vantage form is "helpfully" suggesting for you.
> This was why we had to take the concatenated JOB+ASM+OPR barcode
out of our traveler, for just this reason.
>
> What happens is, after you scan the Job number, the Assembly and
Operation combo boxes refresh their dataset to reflect what
assemblies and operations are valid for the scanned Job number.
>
> Say your job has operations 10 through 150.
> Remembering that a barcode is nothing magical, just literally
keystrokes, your Tab moves the focus to the Opr dropdown.
> Your code types 1. as soon as it does the 1, the combobox
suggests "10" so now, even though you have typed 1, the value in the
combo box is now 10. So now your barcode sends the 0, but of course 0
appended to 10 is now 100.
> That's why you see the 100.
>
> You are not doing anything wrong.
>
> I am sure there is a way to tell the @#$%^& combo box to stop
suggesting, but I don't know how. If you figure that out, and are in
the Houston area anytime soon, I will buy you a beer.
>
>
>
>
> ____________ _________ _________ __
> From: Chris Thompson <chriselectrix@ ...>
> To: vantage@yahoogroups .com
> Sent: Wednesday, December 3, 2008 5:28:54 AM
> Subject: Re: [Vantage] Re: Barcode Question
>
>
> Hi Eric,
>
> I have had the exact same problem recently.
>
> I was using "*" & ToText({JobOper. OprSeq}," 0") & "$I" & "*"
>
> I was having trouble with operation 10 where it was scanning it as
100, but all of the others were ok.
>
> If I scanned our code into word or excel etc it would scan as 10,
so this pointed the problem to Vantage.
>
> I have also tried "*" & ToText({JobOper. OprSeq}," 0.00" & "."
& "$I" & "*" but that doesn't work.
>
> Secondly, I have found that to format a number field within a
formula, it works better if you use e.g. ({number.field} ,"0"). I
believe, but I could be wrong that if you put i.e.
({number.field} ,"0,000.00" ) the number will format i.e. 1,234.56.
>
> I must say, I started writing this email thinking that I had sorted
the problem myself, but now that I have tested it again, it doesn't
work.
>
> Have you tried scanning the suspect numbers into Excel or Word to
see if they scan alright?
>
> Also have you tried leaving the TAB off at the end of the barcode?
>
> Also, I don't think this will may any difference, but when I used
cstr, it made by barcode much bigger than my barcode was when I was
using ToText and as far as I am aware they do the same thing, so if
space is an issue in your design, ToText may be a good solution.
>
> If you find a solution, I would be greatful if you could pass it on.
>
> I am going to ask Epicor to have a look in the meantime.
>
> Thanks,
>
> CHRIS
>
> ____________ _________ _________ __
> From: homestyleindustries <homestyleindustrie s @...>
> To: vantage@yahoogroups .com
> Sent: Tuesday, December 2, 2008 11:58:50 PM
> Subject: [Vantage] Re: Barcode Question
>
> After some more testing we figured out that the ,0 has no effect
> outside of leaving the decimal places off. I took out the ,0 out
and
> it still populated the operation sequence number as 700, whith two
> decimal places obviously. So, new question is why would Vantage
bring
> in last operation of a job with an extra 0? I tried this on
multiple
> jobs and had the same results.
>
> --- In vantage@yahoogroups .com, "homestyleindustrie s"
> <homestyleindustrie s@...> wrote:
> >
> > Here is my problem:
> >
> > I have a job with 6 operations. I created a formula to populate
> > barcodes for each operation to be used with MES. The formula is:
> >
> > "*" + {JobHead.JobNum} + "$I" + cstr({JobAsmbl. AssemblySeq} )
+ "$I"
> +
> > cstr({JobOper. OprSeq},0) + "$I" + "*"
> >
> > I have tried a number of different formulas and this seems to
work
> the
> > best. Yet, for whatever reason on the very last operation it adds
> an
> > extra 0 to the Operation Sequence Number. I figure this is
> populating
> > the irregularity from the (JobOper.OprSeq} ,0). My understanding
is
> > that the ,0 is suppose to leave off the decimal places, which it
> does.
> > With that said, my question is how do I fix this? How can I get
it
> to
> > populate operation 60 instead of 600, while keeping the decimal
> places
> > off?
> >
> > Thanks in advance.
> >
> > Eric
> >
>
> [Non-text portions of this message have been removed]
>
>
>
>
>
>
> [Non-text portions of this message have been removed]
>

[Non-text portions of this message have been removed]






[Non-text portions of this message have been removed]

[system]

I've been working on implementing barcodes, and use this formula in Vantage
6.1 without any extra zeros added except I have one problem (which may be a
variation of yours) I want to stop after the OP CODE is scanned so the
operators can verify that they started the correct operation, but the scan
returns a "carriage return" after the OP CODE, only on Operation 10 on
Assembly Level 0 with jobs that have OP CODES 100 or higher - so the next
screen is opened - not giving the operator a chance to verify a correct
entry.

"*"+Trim({JobAsmbl.JobNum})+"$M"+trim(totext({JobAsmbl.AssemblySeq},0))+"$M"
+trim(totext({JobOper.OprSeq},0))+"*"

Norm Watkins
Engineering Mgr.
ELECPAC
847-639-2307

-----Original Message-----
From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com]On Behalf
Of homestyleindustries
Sent: Tuesday, December 02, 2008 5:49 PM
To: vantage@yahoogroups.com
Subject: [Vantage] Barcode Question


Here is my problem:

I have a job with 6 operations. I created a formula to populate
barcodes for each operation to be used with MES. The formula is:

"*" + {JobHead.JobNum} + "$I" + cstr({JobAsmbl.AssemblySeq}) + "$I" +
cstr({JobOper.OprSeq},0) + "$I" + "*"

I have tried a number of different formulas and this seems to work the
best. Yet, for whatever reason on the very last operation it adds an
extra 0 to the Operation Sequence Number. I figure this is populating
the irregularity from the (JobOper.OprSeq},0). My understanding is
that the ,0 is suppose to leave off the decimal places, which it does.
With that said, my question is how do I fix this? How can I get it to
populate operation 60 instead of 600, while keeping the decimal places
off?

Thanks in advance.

Eric


------------------------------------

Useful links for the Yahoo!Groups Vantage Board are: ( Note: You must have
already linked your email address to a yahoo id to enable access. )
(1) To access the Files Section of our Yahoo!Group for Report Builder and
Crystal Reports and other 'goodies', please goto:
http://groups.yahoo.com/group/vantage/files/.
(2) To search through old msg's goto:
http://groups.yahoo.com/group/vantage/messages
(3) To view links to Vendors that provide Vantage services goto:
http://groups.yahoo.com/group/vantage/linksYahoo! Groups Links

[system]

Chris,

You are a genius. Thank you.

Eric

--- In vantage@yahoogroups.com, Chris Thompson <chriselectrix@...>
wrote:

>
> Hi Eric & Tony,
>
> I believe I may have a solution to all of our problems!!
>
> Ok, the problem appears to be the auto fill function as pointed out

by Tony.

>
> When the scanner scans ie 10, it scans 1 then auto fills the 0 to

make ten but then when it it reads the zero (from the original ten)
for some reason it adds it on the end so scan 10 = scan 1, auto fill
10, add 0 = 100.

>
> What I have done which seems to have fixed the problem (certainly on

my traveller) is to use

>
> "*"&ToText({JobOper.OprSeq},"0")&"$H"&"$I"&"*" ....
>
> obviously you will have to add you job no. and asm to the beginning

if you want one code to do everything,

>
> Basically, I have added a $H before the final $I (TAB) which is the

full ascii key for 'Delete' not 'Backspace', which will delete the
character after the cursor where backspace would delete the character
to the left of the cursor.

>
> I have tried opr seq 10 - 100 and this works well.
>
> I would be interested if this fixes your problems, because at

present it looks as if it has fixed our problem.

>
> I would suggest using ToText as the code is shorter and it works the

same.

>
> Cheers,
>
>
>
> CHRIS
>
>
>
>
> ________________________________
> From: Chris Thompson <chriselectrix@...>
> To: vantage@yahoogroups.com
> Sent: Wednesday, December 3, 2008 2:32:45 PM
> Subject: Re: [Vantage] Re: Barcode Question
>
>
> Hi,
>
> That sounds great - but how do I do it?
>
> Thanks,
>
> CHRIS
>
> ____________ _________ _________ __
> From: bw2868bond <bwalker@adcocircuit s.com>
> To: vantage@yahoogroups .com
> Sent: Wednesday, December 3, 2008 2:00:26 PM
> Subject: [Vantage] Re: Barcode Question
>
> Try setting the AutoEdit property to false (if not available in
> designer propeties, it will have to be done in code)
>
> here is a description of the property:
>
> public bool AutoEdit { set; get; }
> Member of Infragistics. Win.UltraWinGrid .UltraCombo
>
> Summary:
> Determines if the combo will support automatic value completion.
> (Default is true).
>
> Remarks:
> Setting the AutoEdit property to True will enable automatic edit
> value completion for the text area of the combo, based on the values
> in the value list.. When AutoEdit is True and the user types a
> character in the combo's text box, the control will search the
> contents of the
> Infragistics. Win..UltraWinGrid .UltraDropDownBa se.DisplayMember

column

> to see if it contains a value that begins with the same character.

If

> it does, this value will appear in the text box, with all of its
> characters highlighted except the one that the user typed. If the
> user types a second character, the control will check to see if it

is

> the next highlighted character is in the value that appeared. If it
> is, the value stays and the character typed becomes deselected. If
> the second character does not appear in the value, the control
> searches the list again for a value that begins with the first two
> characters that were typed. If one exists, it appears in the text
> box; otherwise the selected text is removed and no more searching
> takes place. This process continues until the user shifts the input
> focus away from the control. If the UltraCombo's
> Infragistics. Win.UltraWinGrid .UltraCombo. DropDownStyle has been

set

> to DropDownList, then setting the AutoEdit to true will enable

multi-

> character auto-edit functionality for the drop down list style. In
> multi-character auto-edit mode, the control will select the item
> whose text starts with characters typed so far. After 500
> milliseconds of time span since last keystroke, a new auto-edit
> session begins where the previously typed characters are discarded
> and new characters are used for multi-character matching.
>
> --- In vantage@yahoogroups .com, Tony Hughes <thughes281@ ...>

wrote:

> >
> >
> > I think the problem you are both seeing is that the combo box on
> the Vantage form is "helpfully" suggesting for you.
> > This was why we had to take the concatenated JOB+ASM+OPR barcode
> out of our traveler, for just this reason.
> >
> > What happens is, after you scan the Job number, the Assembly and
> Operation combo boxes refresh their dataset to reflect what
> assemblies and operations are valid for the scanned Job number.
> >
> > Say your job has operations 10 through 150.
> > Remembering that a barcode is nothing magical, just literally
> keystrokes, your Tab moves the focus to the Opr dropdown.
> > Your code types 1. as soon as it does the 1, the combobox
> suggests "10" so now, even though you have typed 1, the value in the
> combo box is now 10. So now your barcode sends the 0, but of course

0

> appended to 10 is now 100.
> > That's why you see the 100.
> >
> > You are not doing anything wrong.
> >
> > I am sure there is a way to tell the @#$%^& combo box to stop
> suggesting, but I don't know how. If you figure that out, and are in
> the Houston area anytime soon, I will buy you a beer.
> >
> >
> >
> >
> > ____________ _________ _________ __
> > From: Chris Thompson <chriselectrix@ ...>
> > To: vantage@yahoogroups .com
> > Sent: Wednesday, December 3, 2008 5:28:54 AM
> > Subject: Re: [Vantage] Re: Barcode Question
> >
> >
> > Hi Eric,
> >
> > I have had the exact same problem recently.
> >
> > I was using "*" & ToText({JobOper. OprSeq}," 0") & "$I" & "*"
> >
> > I was having trouble with operation 10 where it was scanning it as
> 100, but all of the others were ok.
> >
> > If I scanned our code into word or excel etc it would scan as 10,
> so this pointed the problem to Vantage.
> >
> > I have also tried "*" & ToText({JobOper. OprSeq}," 0.00" & "."
> & "$I" & "*" but that doesn't work.
> >
> > Secondly, I have found that to format a number field within a
> formula, it works better if you use e.g. ({number.field} ,"0"). I
> believe, but I could be wrong that if you put i.e.
> ({number.field} ,"0,000.00" ) the number will format i.e. 1,234.56.
> >
> > I must say, I started writing this email thinking that I had

sorted

> the problem myself, but now that I have tested it again, it doesn't
> work.
> >
> > Have you tried scanning the suspect numbers into Excel or Word to
> see if they scan alright?
> >
> > Also have you tried leaving the TAB off at the end of the barcode?
> >
> > Also, I don't think this will may any difference, but when I used
> cstr, it made by barcode much bigger than my barcode was when I was
> using ToText and as far as I am aware they do the same thing, so if
> space is an issue in your design, ToText may be a good solution.
> >
> > If you find a solution, I would be greatful if you could pass it

on.

> >
> > I am going to ask Epicor to have a look in the meantime.
> >
> > Thanks,
> >
> > CHRIS
> >
> > ____________ _________ _________ __
> > From: homestyleindustries <homestyleindustrie s @...>
> > To: vantage@yahoogroups .com
> > Sent: Tuesday, December 2, 2008 11:58:50 PM
> > Subject: [Vantage] Re: Barcode Question
> >
> > After some more testing we figured out that the ,0 has no effect
> > outside of leaving the decimal places off. I took out the ,0 out
> and
> > it still populated the operation sequence number as 700, whith two
> > decimal places obviously. So, new question is why would Vantage
> bring
> > in last operation of a job with an extra 0? I tried this on
> multiple
> > jobs and had the same results.
> >
> > --- In vantage@yahoogroups .com, "homestyleindustrie s"
> > <homestyleindustrie s@...> wrote:
> > >
> > > Here is my problem:
> > >
> > > I have a job with 6 operations. I created a formula to populate
> > > barcodes for each operation to be used with MES. The formula is:
> > >
> > > "*" + {JobHead.JobNum} + "$I" + cstr({JobAsmbl. AssemblySeq} )
> + "$I"
> > +
> > > cstr({JobOper. OprSeq},0) + "$I" + "*"
> > >
> > > I have tried a number of different formulas and this seems to
> work
> > the
> > > best. Yet, for whatever reason on the very last operation it

adds

> > an
> > > extra 0 to the Operation Sequence Number. I figure this is
> > populating
> > > the irregularity from the (JobOper.OprSeq} ,0). My understanding
> is
> > > that the ,0 is suppose to leave off the decimal places, which it
> > does.
> > > With that said, my question is how do I fix this? How can I get
> it
> > to
> > > populate operation 60 instead of 600, while keeping the decimal
> > places
> > > off?
> > >
> > > Thanks in advance.
> > >
> > > Eric
> > >
> >
> > [Non-text portions of this message have been removed]
> >
> >
> >
> >
> >
> >
> > [Non-text portions of this message have been removed]
> >
>
> [Non-text portions of this message have been removed]
>
>
>
>
>
>
> [Non-text portions of this message have been removed]
>

[system]

Eric,

Does that work on all of your Opr Seq?

I can't take all of the credit .... but I will!!

Cheers,


CHRIS




________________________________
From: homestyleindustries <homestyleindustries@...>
To: vantage@yahoogroups.com
Sent: Wednesday, December 3, 2008 3:50:13 PM
Subject: [Vantage] Re: Barcode Question


Chris,

You are a genius. Thank you.

Eric

--- In vantage@yahoogroups ..com, Chris Thompson <chriselectrix@ ...>
wrote:

>
> Hi Eric & Tony,
>
> I believe I may have a solution to all of our problems!!
>
> Ok, the problem appears to be the auto fill function as pointed out

by Tony.

>
> When the scanner scans ie 10, it scans 1 then auto fills the 0 to

make ten but then when it it reads the zero (from the original ten)
for some reason it adds it on the end so scan 10 = scan 1, auto fill
10, add 0 = 100.

>
> What I have done which seems to have fixed the problem (certainly on

my traveller) is to use

>
> "*"&ToText({ JobOper.OprSeq} ,"0")&"$H" &"$I"&"*" ....
>
> obviously you will have to add you job no. and asm to the beginning

if you want one code to do everything,

>
> Basically, I have added a $H before the final $I (TAB) which is the

full ascii key for 'Delete' not 'Backspace', which will delete the
character after the cursor where backspace would delete the character
to the left of the cursor.

>
> I have tried opr seq 10 - 100 and this works well.
>
> I would be interested if this fixes your problems, because at

present it looks as if it has fixed our problem.

>
> I would suggest using ToText as the code is shorter and it works the

same.

>
> Cheers,
>
>
>
> CHRIS
>
>
>
>
> ____________ _________ _________ __
> From: Chris Thompson <chriselectrix@ ...>
> To: vantage@yahoogroups .com
> Sent: Wednesday, December 3, 2008 2:32:45 PM
> Subject: Re: [Vantage] Re: Barcode Question
>
>
> Hi,
>
> That sounds great - but how do I do it?
>
> Thanks,
>
> CHRIS
>
> ____________ _________ _________ __
> From: bw2868bond <bwalker@adcocircui t s.com>
> To: vantage@yahoogroups .com
> Sent: Wednesday, December 3, 2008 2:00:26 PM
> Subject: [Vantage] Re: Barcode Question
>
> Try setting the AutoEdit property to false (if not available in
> designer propeties, it will have to be done in code)
>
> here is a description of the property:
>
> public bool AutoEdit { set; get; }
> Member of Infragistics. Win.UltraWinGrid .UltraCombo
>
> Summary:
> Determines if the combo will support automatic value completion.
> (Default is true).
>
> Remarks:
> Setting the AutoEdit property to True will enable automatic edit
> value completion for the text area of the combo, based on the values
> in the value list.. When AutoEdit is True and the user types a
> character in the combo's text box, the control will search the
> contents of the
> Infragistics. Win..UltraWinGrid .UltraDropDownBa se.DisplayMember

column

> to see if it contains a value that begins with the same character.

If

> it does, this value will appear in the text box, with all of its
> characters highlighted except the one that the user typed. If the
> user types a second character, the control will check to see if it

is

> the next highlighted character is in the value that appeared. If it
> is, the value stays and the character typed becomes deselected. If
> the second character does not appear in the value, the control
> searches the list again for a value that begins with the first two
> characters that were typed. If one exists, it appears in the text
> box; otherwise the selected text is removed and no more searching
> takes place. This process continues until the user shifts the input
> focus away from the control. If the UltraCombo's
> Infragistics. Win.UltraWinGrid .UltraCombo. DropDownStyle has been

set

> to DropDownList, then setting the AutoEdit to true will enable

multi-

> character auto-edit functionality for the drop down list style. In
> multi-character auto-edit mode, the control will select the item
> whose text starts with characters typed so far. After 500
> milliseconds of time span since last keystroke, a new auto-edit
> session begins where the previously typed characters are discarded
> and new characters are used for multi-character matching.
>
> --- In vantage@yahoogroups .com, Tony Hughes <thughes281@ ...>

wrote:

> >
> >
> > I think the problem you are both seeing is that the combo box on
> the Vantage form is "helpfully" suggesting for you.
> > This was why we had to take the concatenated JOB+ASM+OPR barcode
> out of our traveler, for just this reason.
> >
> > What happens is, after you scan the Job number, the Assembly and
> Operation combo boxes refresh their dataset to reflect what
> assemblies and operations are valid for the scanned Job number.
> >
> > Say your job has operations 10 through 150.
> > Remembering that a barcode is nothing magical, just literally
> keystrokes, your Tab moves the focus to the Opr dropdown.
> > Your code types 1. as soon as it does the 1, the combobox
> suggests "10" so now, even though you have typed 1, the value in the
> combo box is now 10. So now your barcode sends the 0, but of course

0

> appended to 10 is now 100.
> > That's why you see the 100.
> >
> > You are not doing anything wrong.
> >
> > I am sure there is a way to tell the @#$%^& combo box to stop
> suggesting, but I don't know how. If you figure that out, and are in
> the Houston area anytime soon, I will buy you a beer.
> >
> >
> >
> >
> > ____________ _________ _________ __
> > From: Chris Thompson <chriselectrix@ ...>
> > To: vantage@yahoogroups .com
> > Sent: Wednesday, December 3, 2008 5:28:54 AM
> > Subject: Re: [Vantage] Re: Barcode Question
> >
> >
> > Hi Eric,
> >
> > I have had the exact same problem recently.
> >
> > I was using "*" & ToText({JobOper. OprSeq}," 0") & "$I" & "*"
> >
> > I was having trouble with operation 10 where it was scanning it as
> 100, but all of the others were ok.
> >
> > If I scanned our code into word or excel etc it would scan as 10,
> so this pointed the problem to Vantage.
> >
> > I have also tried "*" & ToText({JobOper. OprSeq}," 0.00" & "."
> & "$I" & "*" but that doesn't work.
> >
> > Secondly, I have found that to format a number field within a
> formula, it works better if you use e.g. ({number.field} ,"0"). I
> believe, but I could be wrong that if you put i.e.
> ({number.field} ,"0,000.00" ) the number will format i.e. 1,234.56.
> >
> > I must say, I started writing this email thinking that I had

sorted

> the problem myself, but now that I have tested it again, it doesn't
> work.
> >
> > Have you tried scanning the suspect numbers into Excel or Word to
> see if they scan alright?
> >
> > Also have you tried leaving the TAB off at the end of the barcode?
> >
> > Also, I don't think this will may any difference, but when I used
> cstr, it made by barcode much bigger than my barcode was when I was
> using ToText and as far as I am aware they do the same thing, so if
> space is an issue in your design, ToText may be a good solution.
> >
> > If you find a solution, I would be greatful if you could pass it

on.

> >
> > I am going to ask Epicor to have a look in the meantime.
> >
> > Thanks,
> >
> > CHRIS
> >
> > ____________ _________ _________ __
> > From: homestyleindustries <homestyleindustrie s @...>
> > To: vantage@yahoogroups .com
> > Sent: Tuesday, December 2, 2008 11:58:50 PM
> > Subject: [Vantage] Re: Barcode Question
> >
> > After some more testing we figured out that the ,0 has no effect
> > outside of leaving the decimal places off. I took out the ,0 out
> and
> > it still populated the operation sequence number as 700, whith two
> > decimal places obviously. So, new question is why would Vantage
> bring
> > in last operation of a job with an extra 0? I tried this on
> multiple
> > jobs and had the same results.
> >
> > --- In vantage@yahoogroups .com, "homestyleindustrie s"
> > <homestyleindustrie s@...> wrote:
> > >
> > > Here is my problem:
> > >
> > > I have a job with 6 operations. I created a formula to populate
> > > barcodes for each operation to be used with MES. The formula is:
> > >
> > > "*" + {JobHead.JobNum} + "$I" + cstr({JobAsmbl. AssemblySeq} )
> + "$I"
> > +
> > > cstr({JobOper. OprSeq},0) + "$I" + "*"
> > >
> > > I have tried a number of different formulas and this seems to
> work
> > the
> > > best. Yet, for whatever reason on the very last operation it

adds

> > an
> > > extra 0 to the Operation Sequence Number. I figure this is
> > populating
> > > the irregularity from the (JobOper.OprSeq} ,0). My understanding
> is
> > > that the ,0 is suppose to leave off the decimal places, which it
> > does.
> > > With that said, my question is how do I fix this? How can I get
> it
> > to
> > > populate operation 60 instead of 600, while keeping the decimal
> > places
> > > off?
> > >
> > > Thanks in advance.
> > >
> > > Eric
> > >
> >
> > [Non-text portions of this message have been removed]
> >
> >
> >
> >
> >
> >
> > [Non-text portions of this message have been removed]
> >
>
> [Non-text portions of this message have been removed]
>
>
>
>
>
>
> [Non-text portions of this message have been removed]
>

[Non-text portions of this message have been removed]

[system]

Hi Norm,

Is scanner set up to automatically add a carriage return as there isnt a $M at the end of your code.

It sounds to be like your problem may be a variation of our problem. Try the $H before the final asterisk..

It sounds like your scanner is automatically adding a carriage return at the end because it shouldn't be doing it otherwise.

If you go into wordpad and create *100* (in barcode font) and then scan that into wordpad, does it scan n move the cursor to the nex or does the cursor just flash after 100?

Cheers,


CHRIS




________________________________
From: Norm Watkins <nwatkins@...>
To: vantage@yahoogroups.com
Sent: Wednesday, December 3, 2008 3:38:20 PM
Subject: RE: [Vantage] Barcode Question


I've been working on implementing barcodes, and use this formula in Vantage
6.1 without any extra zeros added except I have one problem (which may be a
variation of yours) I want to stop after the OP CODE is scanned so the
operators can verify that they started the correct operation, but the scan
returns a "carriage return" after the OP CODE, only on Operation 10 on
Assembly Level 0 with jobs that have OP CODES 100 or higher - so the next
screen is opened - not giving the operator a chance to verify a correct
entry.

"*"+Trim({JobAsmbl. JobNum})+ "$M"+trim( totext({JobAsmbl .AssemblySeq} ,0))+"$M"
+trim(totext( {JobOper. OprSeq},0) )+"*"

Norm Watkins
Engineering Mgr.
ELECPAC
847-639-2307

-----Original Message-----
From: vantage@yahoogroups .com [mailto:vantage@yahoogroups .com]On Behalf
Of homestyleindustries
Sent: Tuesday, December 02, 2008 5:49 PM
To: vantage@yahoogroups .com
Subject: [Vantage] Barcode Question

Here is my problem:

I have a job with 6 operations. I created a formula to populate
barcodes for each operation to be used with MES. The formula is:

"*" + {JobHead.JobNum} + "$I" + cstr({JobAsmbl. AssemblySeq} ) + "$I" +
cstr({JobOper. OprSeq},0) + "$I" + "*"

I have tried a number of different formulas and this seems to work the
best. Yet, for whatever reason on the very last operation it adds an
extra 0 to the Operation Sequence Number. I figure this is populating
the irregularity from the (JobOper.OprSeq} ,0). My understanding is
that the ,0 is suppose to leave off the decimal places, which it does.
With that said, my question is how do I fix this? How can I get it to
populate operation 60 instead of 600, while keeping the decimal places
off?

Thanks in advance.

Eric

------------ --------- --------- ------

Useful links for the Yahoo!Groups Vantage Board are: ( Note: You must have
already linked your email address to a yahoo id to enable access. )
(1) To access the Files Section of our Yahoo!Group for Report Builder and
Crystal Reports and other 'goodies', please goto:
http://groups. yahoo.com/ group/vantage/ files/.
(2) To search through old msg's goto:
http://groups. yahoo.com/ group/vantage/ messages
(3) To view links to Vendors that provide Vantage services goto:
http://groups. yahoo.com/ group/vantage/ linksYahoo! Groups Links






[Non-text portions of this message have been removed]

[system]

if anyone is interested, there is another fix for the barcode trailing zero problem but it's a little more technical ....

In the userSettings section of the specialmes.mfgsys file, set the value for SelectTextOnEnter node to true. This will select the entire data contents of a control when focus transfers to the control via a Tab or programmatic set-focus. I believe that we do not select the entire data if a mouse event initiates focus.

<SelectTextOnEnter value="True" bool="" /> "
I dont know if that s any sense but it's worth a try.

Thanks.



________________________________
From: Chris Thompson <chriselectrix@...>
To: vantage@yahoogroups.com
Sent: Wednesday, December 3, 2008 4:06:46 PM
Subject: Re: [Vantage] Barcode Question


Hi Norm,

Is scanner set up to automatically add a carriage return as there isnt a $M at the end of your code.

It sounds to be like your problem may be a variation of our problem. Try the $H before the final asterisk..

It sounds like your scanner is automatically adding a carriage return at the end because it shouldn't be doing it otherwise.

If you go into wordpad and create *100* (in barcode font) and then scan that into wordpad, does it scan n move the cursor to the nex or does the cursor just flash after 100?

Cheers,

CHRIS

____________ _________ _________ __
From: Norm Watkins <nwatkins@elecpac. com>
To: vantage@yahoogroups .com
Sent: Wednesday, December 3, 2008 3:38:20 PM
Subject: RE: [Vantage] Barcode Question

I've been working on implementing barcodes, and use this formula in Vantage
6.1 without any extra zeros added except I have one problem (which may be a
variation of yours) I want to stop after the OP CODE is scanned so the
operators can verify that they started the correct operation, but the scan
returns a "carriage return" after the OP CODE, only on Operation 10 on
Assembly Level 0 with jobs that have OP CODES 100 or higher - so the next
screen is opened - not giving the operator a chance to verify a correct
entry.

"*"+Trim({JobAsmbl. JobNum})+ "$M"+trim( totext({JobAsmbl .AssemblySeq} ,0))+"$M"
+trim(totext( {JobOper. OprSeq},0) )+"*"

Norm Watkins
Engineering Mgr.
ELECPAC
847-639-2307

-----Original Message-----
From: vantage@yahoogroups .com [mailto:vantage@ yahoogroups .com]On Behalf
Of homestyleindustries
Sent: Tuesday, December 02, 2008 5:49 PM
To: vantage@yahoogroups .com
Subject: [Vantage] Barcode Question

Here is my problem:

I have a job with 6 operations. I created a formula to populate
barcodes for each operation to be used with MES. The formula is:

"*" + {JobHead.JobNum} + "$I" + cstr({JobAsmbl. AssemblySeq} ) + "$I" +
cstr({JobOper. OprSeq},0) + "$I" + "*"

I have tried a number of different formulas and this seems to work the
best. Yet, for whatever reason on the very last operation it adds an
extra 0 to the Operation Sequence Number. I figure this is populating
the irregularity from the (JobOper..OprSeq} ,0). My understanding is
that the ,0 is suppose to leave off the decimal places, which it does.
With that said, my question is how do I fix this? How can I get it to
populate operation 60 instead of 600, while keeping the decimal places
off?

Thanks in advance.

Eric

------------ --------- --------- ------

Useful links for the Yahoo!Groups Vantage Board are: ( Note: You must have
already linked your email address to a yahoo id to enable access. )
(1) To access the Files Section of our Yahoo!Group for Report Builder and
Crystal Reports and other 'goodies', please goto:
http://groups. yahoo.com/ group/vantage/ files/.
(2) To search through old msg's goto:
http://groups. yahoo.com/ group/vantage/ messages
(3) To view links to Vendors that provide Vantage services goto:
http://groups. yahoo.com/ group/vantage/ linksYahoo! Groups Links

[Non-text portions of this message have been removed]






[Non-text portions of this message have been removed]

[system]

There will an occasion where this won't work, unfortunately - when whatever you scan does not result in a suggestion.

Example, we use multiples of 10 for the sequencing at the MOM level.
If a rework or added operation is inserted, say between operation 40 and operation 50, we might number it 41.
Scan operation 41: first scanner "types" the '4', the combo-box suggests '40'. Now scan the scanner types the '1' and appends that to the 40 it suggested, so now you have 401. Now backspace reduces that to 40.






________________________________
From: Chris Thompson <chriselectrix@...>
To: vantage@yahoogroups.com
Sent: Wednesday, December 3, 2008 9:21:16 AM
Subject: Re: [Vantage] Re: Barcode Question


Hi Eric & Tony,

I believe I may have a solution to all of our problems!!

Ok, the problem appears to be the auto fill function as pointed out by Tony.

When the scanner scans ie 10, it scans 1 then auto fills the 0 to make ten but then when it it reads the zero (from the original ten) for some reason it adds it on the end so scan 10 = scan 1, auto fill 10, add 0 = 100.

What I have done which seems to have fixed the problem (certainly on my traveller) is to use

"*"&ToText({ JobOper.OprSeq} ,"0")&"$H" &"$I"&"*" ....

obviously you will have to add you job no. and asm to the beginning if you want one code to do everything,

Basically, I have added a $H before the final $I (TAB) which is the full ascii key for 'Delete' not 'Backspace', which will delete the character after the cursor where backspace would delete the character to the left of the cursor.

I have tried opr seq 10 - 100 and this works well.

I would be interested if this fixes your problems, because at present it looks as if it has fixed our problem.

I would suggest using ToText as the code is shorter and it works the same.

Cheers,

CHRIS

____________ _________ _________ __
From: Chris Thompson <chriselectrix@ ymail.com>
To: vantage@yahoogroups .com
Sent: Wednesday, December 3, 2008 2:32:45 PM
Subject: Re: [Vantage] Re: Barcode Question

Hi,

That sounds great - but how do I do it?

Thanks,

CHRIS

____________ _________ _________ __
From: bw2868bond <bwalker@adcocircui t s.com>
To: vantage@yahoogroups .com
Sent: Wednesday, December 3, 2008 2:00:26 PM
Subject: [Vantage] Re: Barcode Question

Try setting the AutoEdit property to false (if not available in
designer propeties, it will have to be done in code)

here is a description of the property:

public bool AutoEdit { set; get; }
Member of Infragistics. Win.UltraWinGrid .UltraCombo

Summary:
Determines if the combo will support automatic value completion.
(Default is true).

Remarks:
Setting the AutoEdit property to True will enable automatic edit
value completion for the text area of the combo, based on the values
in the value list.. When AutoEdit is True and the user types a
character in the combo's text box, the control will search the
contents of the
Infragistics. Win..UltraWinGrid .UltraDropDownBa se.DisplayMember column
to see if it contains a value that begins with the same character. If
it does, this value will appear in the text box, with all of its
characters highlighted except the one that the user typed. If the
user types a second character, the control will check to see if it is
the next highlighted character is in the value that appeared. If it
is, the value stays and the character typed becomes deselected. If
the second character does not appear in the value, the control
searches the list again for a value that begins with the first two
characters that were typed. If one exists, it appears in the text
box; otherwise the selected text is removed and no more searching
takes place. This process continues until the user shifts the input
focus away from the control. If the UltraCombo's
Infragistics. Win.UltraWinGrid .UltraCombo. DropDownStyle has been set
to DropDownList, then setting the AutoEdit to true will enable multi-
character auto-edit functionality for the drop down list style. In
multi-character auto-edit mode, the control will select the item
whose text starts with characters typed so far. After 500
milliseconds of time span since last keystroke, a new auto-edit
session begins where the previously typed characters are discarded
and new characters are used for multi-character matching.

--- In vantage@yahoogroups .com, Tony Hughes <thughes281@ ...> wrote:
>
>
> I think the problem you are both seeing is that the combo box on
the Vantage form is "helpfully" suggesting for you.
> This was why we had to take the concatenated JOB+ASM+OPR barcode
out of our traveler, for just this reason.
>
> What happens is, after you scan the Job number, the Assembly and
Operation combo boxes refresh their dataset to reflect what
assemblies and operations are valid for the scanned Job number.
>
> Say your job has operations 10 through 150.
> Remembering that a barcode is nothing magical, just literally
keystrokes, your Tab moves the focus to the Opr dropdown.
> Your code types 1. as soon as it does the 1, the combobox
suggests "10" so now, even though you have typed 1, the value in the
combo box is now 10. So now your barcode sends the 0, but of course 0
appended to 10 is now 100.
> That's why you see the 100.
>
> You are not doing anything wrong.
>
> I am sure there is a way to tell the @#$%^& combo box to stop
suggesting, but I don't know how. If you figure that out, and are in
the Houston area anytime soon, I will buy you a beer.
>
>
>
>
> ____________ _________ _________ __
> From: Chris Thompson <chriselectrix@ ...>
> To: vantage@yahoogroups .com
> Sent: Wednesday, December 3, 2008 5:28:54 AM
> Subject: Re: [Vantage] Re: Barcode Question
>
>
> Hi Eric,
>
> I have had the exact same problem recently.
>
> I was using "*" & ToText({JobOper. OprSeq}," 0") & "$I" & "*"
>
> I was having trouble with operation 10 where it was scanning it as
100, but all of the others were ok.
>
> If I scanned our code into word or excel etc it would scan as 10,
so this pointed the problem to Vantage.
>
> I have also tried "*" & ToText({JobOper. OprSeq}," 0.00" & "."
& "$I" & "*" but that doesn't work.
>
> Secondly, I have found that to format a number field within a
formula, it works better if you use e.g. ({number.field} ,"0"). I
believe, but I could be wrong that if you put i.e.
({number.field} ,"0,000.00" ) the number will format i.e. 1,234.56.
>
> I must say, I started writing this email thinking that I had sorted
the problem myself, but now that I have tested it again, it doesn't
work.
>
> Have you tried scanning the suspect numbers into Excel or Word to
see if they scan alright?
>
> Also have you tried leaving the TAB off at the end of the barcode?
>
> Also, I don't think this will may any difference, but when I used
cstr, it made by barcode much bigger than my barcode was when I was
using ToText and as far as I am aware they do the same thing, so if
space is an issue in your design, ToText may be a good solution.
>
> If you find a solution, I would be greatful if you could pass it on.
>
> I am going to ask Epicor to have a look in the meantime.
>
> Thanks,
>
> CHRIS
>
> ____________ _________ _________ __
> From: homestyleindustries <homestyleindustrie s @...>
> To: vantage@yahoogroups .com
> Sent: Tuesday, December 2, 2008 11:58:50 PM
> Subject: [Vantage] Re: Barcode Question
>
> After some more testing we figured out that the ,0 has no effect
> outside of leaving the decimal places off. I took out the ,0 out
and
> it still populated the operation sequence number as 700, whith two
> decimal places obviously. So, new question is why would Vantage
bring
> in last operation of a job with an extra 0? I tried this on
multiple
> jobs and had the same results.
>
> --- In vantage@yahoogroups .com, "homestyleindustrie s"
> <homestyleindustrie s@...> wrote:
> >
> > Here is my problem:
> >
> > I have a job with 6 operations. I created a formula to populate
> > barcodes for each operation to be used with MES. The formula is:
> >
> > "*" + {JobHead.JobNum} + "$I" + cstr({JobAsmbl. AssemblySeq} )
+ "$I"
> +
> > cstr({JobOper. OprSeq},0) + "$I" + "*"
> >
> > I have tried a number of different formulas and this seems to
work
> the
> > best. Yet, for whatever reason on the very last operation it adds
> an
> > extra 0 to the Operation Sequence Number. I figure this is
> populating
> > the irregularity from the (JobOper.OprSeq} ,0). My understanding
is
> > that the ,0 is suppose to leave off the decimal places, which it
> does.
> > With that said, my question is how do I fix this? How can I get
it
> to
> > populate operation 60 instead of 600, while keeping the decimal
> places
> > off?
> >
> > Thanks in advance.
> >
> > Eric
> >
>
> [Non-text portions of this message have been removed]
>
>
>
>
>
>
> [Non-text portions of this message have been removed]
>

[Non-text portions of this message have been removed]

[Non-text portions of this message have been removed]






[Non-text portions of this message have been removed]

[system]

Hi Tony,

Hadnhought of that, but we are using the standard Vantage Opr Seq and havent encountered opr seq f anything other than multiples of 10.

We had added operations in between operations and it always number the sequences in multiples of 10.

Whversion of Vantage are you on?

IÂ see where you are coming from, but have never encountered ie opr 4n with our legacy system.

There was another potential fix:

In the userSettings section of their specialmes.mfgsys file, set the value for SelectTextOnEnter node to true. This will select the entire data contents of a control when focus transfers to the control via a Tab or programmatic set-focus. I believe that we do not select the entire data if a mouse event initiates focus.

<SelectTextOnEnter value="True" bool="" /> "
Â
I dont know how to do that though as Im not clued up on the whole user settings area.
Â
Cheers,
Â
Â
CHRIS




________________________________
From: Tony Hughes <thughes281@...>
To: vantage@yahoogroups.com
Sent: Wednesday, December 3, 2008 4:25:32 PM
Subject: Re: [Vantage] Re: Barcode Question


There will an occasion where this won't work, unfortunately - when whatever you scan does not result in a suggestion.

Example, we use multiples of 10 for the sequencing at the MOM level.
If a rework or added operation is inserted, say between operation 40 and operation 50, we might number it 41.
Scan operation 41: first scanner "types" the '4', the combo-box suggests '40'. Now scan the scanner types the '1' and appends that to the 40 it suggested, so now you have 401. Now backspace reduces that to 40.

____________ _________ _________ __
From: Chris Thompson <chriselectrix@ ymail.com>
To: vantage@yahoogroups .com
Sent: Wednesday, December 3, 2008 9:21:16 AM
Subject: Re: [Vantage] Re: Barcode Question

Hi Eric & Tony,

I believe I may have a solution to all of our problems!!

Ok, the problem appears to be the auto fill function as pointed out by Tony.

When the scanner scans ie 10, it scans 1 then auto fills the 0 to make ten but then when it it reads the zero (from the original ten) for some reason it adds it on the end so scan 10 = scan 1, auto fill 10, add 0 = 100.

What I have done which seems to have fixed the problem (certainly on my traveller) is to use

"*"&ToText({ JobOper.OprSeq} ,"0")&"$H" &"$I"&"*" ....

obviously you will have to add you job no. and asm to the beginning if you want one code to do everything,

Basically, I have added a $H before the final $I (TAB) which is the full ascii key for 'Delete' not 'Backspace', which will delete the character after the cursor where backspace would delete the character to the left of the cursor.

I have tried opr seq 10 - 100 and this works well.

I would be interested if this fixes your problems, because at present it looks as if it has fixed our problem.

I would suggest using ToText as the code is shorter and it works the same.

Cheers,

CHRIS

____________ _________ _________ __
From: Chris Thompson <chriselectrix@ ymail.com>
To: vantage@yahoogroups .com
Sent: Wednesday, December 3, 2008 2:32:45 PM
Subject: Re: [Vantage] Re: Barcode Question

Hi,

That sounds great - but how do I do it?

Thanks,

CHRIS

____________ _________ _________ __
From: bw2868bond <bwalker@adcocircui t s.com>
To: vantage@yahoogroups .com
Sent: Wednesday, December 3, 2008 2:00:26 PM
Subject: [Vantage] Re: Barcode Question

Try setting the AutoEdit property to false (if not available in
designer propeties, it will have to be done in code)

here is a description of the property:

public bool AutoEdit { set; get; }
Member of Infragistics. Win.UltraWinGrid .UltraCombo

Summary:
Determines if the combo will support automatic value completion.
(Default is true).

Remarks:
Setting the AutoEdit property to True will enable automatic edit
value completion for the text area of the combo, based on the values
in the value list.. When AutoEdit is True and the user types a
character in the combo's text box, the control will search the
contents of the
Infragistics. Win..UltraWinGrid .UltraDropDownBa se.DisplayMember column
to see if it contains a value that begins with the same character. If
it does, this value will appear in the text box, with all of its
characters highlighted except the one that the user typed. If the
user types a second character, the control will check to see if it is
the next highlighted character is in the value that appeared. If it
is, the value stays and the character typed becomes deselected. If
the second character does not appear in the value, the control
searches the list again for a value that begins with the first two
characters that were typed. If one exists, it appears in the text
box; otherwise the selected text is removed and no more searching
takes place. This process continues until the user shifts the input
focus away from the control. If the UltraCombo's
Infragistics. Win.UltraWinGrid .UltraCombo. DropDownStyle has been set
to DropDownList, then setting the AutoEdit to true will enable multi-
character auto-edit functionality for the drop down list style. In
multi-character auto-edit mode, the control will select the item
whose text starts with characters typed so far. After 500
milliseconds of time span since last keystroke, a new auto-edit
session begins where the previously typed characters are discarded
and new characters are used for multi-character matching.

--- In vantage@yahoogroups .com, Tony Hughes <thughes281@ ...> wrote:
>
>
> I think the problem you are both seeing is that the combo box on
the Vantage form is "helpfully" suggesting for you.
> This was why we had to take the concatenated JOB+ASM+OPR barcode
out of our traveler, for just this reason.
>
> What happens is, after you scan the Job number, the Assembly and
Operation combo boxes refresh their dataset to reflect what
assemblies and operations are valid for the scanned Job number.
>
> Say your job has operations 10 through 150.
> Remembering that a barcode is nothing magical, just literally
keystrokes, your Tab moves the focus to the Opr dropdown.
> Your code types 1. as soon as it does the 1, the combobox
suggests "10" so now, even though you have typed 1, the value in the
combo box is now 10. So now your barcode sends the 0, but of course 0
appended to 10 is now 100.
> That's why you see the 100.
>
> You are not doing anything wrong.
>
> I am sure there is a way to tell the @#$%^& combo box to stop
suggesting, but I don't know how. If you figure that out, and are in
the Houston area anytime soon, I will buy you a beer.
>
>
>
>
> ____________ _________ _________ __
> From: Chris Thompson <chriselectrix@ ...>
> To: vantage@yahoogroups .com
> Sent: Wednesday, December 3, 2008 5:28:54 AM
> Subject: Re: [Vantage] Re: Barcode Question
>
>
> Hi Eric,
>
> I have had the exact same problem recently.
>
> I was using "*" & ToText({JobOper. OprSeq}," 0") & "$I" & "*"
>
> I was having trouble with operation 10 where it was scanning it as
100, but all of the others were ok.
>
> If I scanned our code into word or excel etc it would scan as 10,
so this pointed the problem to Vantage.
>
> I have also tried "*" & ToText({JobOper. OprSeq}," 0.00" & "."
& "$I" & "*" but that doesn't work.
>
> Secondly, I have found that to format a number field within a
formula, it works better if you use e.g. ({number.field} ,"0"). I
believe, but I could be wrong that if you put i.e.
({number.field} ,"0,000.00" ) the number will format i.e. 1,234.56.
>
> I must say, I started writing this email thinking that I had sorted
the problem myself, but now that I have tested it again, it doesn't
work.
>
> Have you tried scanning the suspect numbers into Excel or Word to
see if they scan alright?
>
> Also have you tried leaving the TAB off at the end of the barcode?
>
> Also, I don't think this will may any difference, but when I used
cstr, it made by barcode much bigger than my barcode was when I was
using ToText and as far as I am aware they do the same thing, so if
space is an issue in your design, ToText may be a good solution.
>
> If you find a solution, I would be greatful if you could pass it on.
>
> I am going to ask Epicor to have a look in the meantime.
>
> Thanks,
>
> CHRIS
>
> ____________ _________ _________ __
> From: homestyleindustries <homestyleindustrie s @...>
> To: vantage@yahoogroups .com
> Sent: Tuesday, December 2, 2008 11:58:50 PM
> Subject: [Vantage] Re: Barcode Question
>
> After some more testing we figured out that the ,0 has no effect
> outside of leaving the decimal places off. I took out the ,0 out
and
> it still populated the operation sequence number as 700, whith two
> decimal places obviously. So, new question is why would Vantage
bring
> in last operation of a job with an extra 0? I tried this on
multiple
> jobs and had the same results.
>
> --- In vantage@yahoogroups .com, "homestyleindustrie s"
> <homestyleindustrie s@...> wrote:
> >
> > Here is my problem:
> >
> > I have a job with 6 operations. I created a formula to populate
> > barcodes for each operation to be used with MES. The formula is:
> >
> > "*" + {JobHead.JobNum} + "$I" + cstr({JobAsmbl. AssemblySeq} )
+ "$I"
> +
> > cstr({JobOper. OprSeq},0) + "$I" + "*"
> >
> > I have tried a number of different formulas and this seems to
work
> the
> > best. Yet, for whatever reason on the very last operation it adds
> an
> > extra 0 to the Operation Sequence Number. I figure this is
> populating
> > the irregularity from the (JobOper.OprSeq} ,0). My understanding
is
> > that the ,0 is suppose to leave off the decimal places, which it
> does.
> > With that said, my question is how do I fix this? How can I get
it
> to
> > populate operation 60 instead of 600, while keeping the decimal
> places
> > off?
> >
> > Thanks in advance.
> >
> > Eric
> >
>
> [Non-text portions of this message have been removed]
>
>
>
>
>
>
> [Non-text portions of this message have been removed]
>

[Non-text portions of this message have been removed]

[Non-text portions of this message have been removed]

[Non-text portions of this message have been removed]






[Non-text portions of this message have been removed]

[system]

> Example, we use multiples of 10 for the sequencing at the MOM level.
> If a rework or added operation is inserted, say between operation 40 and
> operation 50, we might number it 41.
> Scan operation 41: first scanner "types" the '4', the combo-box suggests
> '40'. Now scan the scanner types the '1' and appends that to the 40 it
> suggested, so now you have 401. Now backspace reduces that to 40.

Some barcode formats, like the AIAG Automotive format
(http://barcode.toshibatec.co.jp/eng/whatRU/labels/index.html) have a
leading character in the barcode field to indicate what the field does. For
example, the part number is prefixed by a 'P', the quantity by a 'Q', etc.
The idea is to make sure that you can't be in the wrong field on the screen
and accidentally scan in the wrong item. If the scanner saw a 'P' in the
first position, it stripped off the prefix and sent the part number directly
to the part field.

If one expanded on this idea, you could create a single "scanning field" on
your form that would:

- read the barcode
- scan the prefix
- populate the correct field (and maybe refreshing the form to get default
values)
- set the focus back to the "scanning field"

This way, you avoid the whole tabbing issue and user can't scan the wrong
item into the wrong field. Food for thought...

Mark W.

[system]

It could still effect you, say your job only has up to Opr 90, or Opr 100 is a backflushed or some other situation where it won't appear in that Opr list.

Scan 10,
1 is typed, system suggests the 0 to make 10.
0 is typed, system suggests nothing, there's no 100, so leaves the 10 alone.
$H is sent, backspaces over the 0 and you're left with 1.







________________________________
From: Chris Thompson <chriselectrix@...>
To: vantage@yahoogroups.com
Sent: Wednesday, December 3, 2008 10:42:13 AM
Subject: Re: [Vantage] Re: Barcode Question


Hi Tony,

Hadnhought of that, but we are using the standard Vantage Opr Seq and havent encountered opr seq f anything other than multiples of 10.

We had added operations in between operations and it always number the sequences in multiples of 10.

Whversion of Vantage are you on?

I see where you are coming from, but have never encountered ie opr 4n with our legacy system.

There was another potential fix:

In the userSettings section of their specialmes.mfgsys file, set the value for SelectTextOnEnter node to true. This will select the entire data contents of a control when focus transfers to the control via a Tab or programmatic set-focus. I believe that we do not select the entire data if a mouse event initiates focus.

<SelectTextOnEnter value="True" bool="" /> "

I dont know how to do that though as Im not clued up on the whole user settings area.

Cheers,


CHRIS

____________ _________ _________ __
From: Tony Hughes <thughes281@yahoo. com>
To: vantage@yahoogroups .com
Sent: Wednesday, December 3, 2008 4:25:32 PM
Subject: Re: [Vantage] Re: Barcode Question

There will an occasion where this won't work, unfortunately - when whatever you scan does not result in a suggestion.

Example, we use multiples of 10 for the sequencing at the MOM level.
If a rework or added operation is inserted, say between operation 40 and operation 50, we might number it 41.
Scan operation 41: first scanner "types" the '4', the combo-box suggests '40'. Now scan the scanner types the '1' and appends that to the 40 it suggested, so now you have 401. Now backspace reduces that to 40.

____________ _________ _________ __
From: Chris Thompson <chriselectrix@ ymail.com>
To: vantage@yahoogroups .com
Sent: Wednesday, December 3, 2008 9:21:16 AM
Subject: Re: [Vantage] Re: Barcode Question

Hi Eric & Tony,

I believe I may have a solution to all of our problems!!

Ok, the problem appears to be the auto fill function as pointed out by Tony.

When the scanner scans ie 10, it scans 1 then auto fills the 0 to make ten but then when it it reads the zero (from the original ten) for some reason it adds it on the end so scan 10 = scan 1, auto fill 10, add 0 = 100.

What I have done which seems to have fixed the problem (certainly on my traveller) is to use

"*"&ToText({ JobOper.OprSeq} ,"0")&"$H" &"$I"&"*" ....

obviously you will have to add you job no. and asm to the beginning if you want one code to do everything,

Basically, I have added a $H before the final $I (TAB) which is the full ascii key for 'Delete' not 'Backspace', which will delete the character after the cursor where backspace would delete the character to the left of the cursor.

I have tried opr seq 10 - 100 and this works well.

I would be interested if this fixes your problems, because at present it looks as if it has fixed our problem.

I would suggest using ToText as the code is shorter and it works the same.

Cheers,

CHRIS

____________ _________ _________ __
From: Chris Thompson <chriselectrix@ ymail.com>
To: vantage@yahoogroups .com
Sent: Wednesday, December 3, 2008 2:32:45 PM
Subject: Re: [Vantage] Re: Barcode Question

Hi,

That sounds great - but how do I do it?

Thanks,

CHRIS

____________ _________ _________ __
From: bw2868bond <bwalker@adcocircui t s.com>
To: vantage@yahoogroups .com
Sent: Wednesday, December 3, 2008 2:00:26 PM
Subject: [Vantage] Re: Barcode Question

Try setting the AutoEdit property to false (if not available in
designer propeties, it will have to be done in code)

here is a description of the property:

public bool AutoEdit { set; get; }
Member of Infragistics. Win.UltraWinGrid .UltraCombo

Summary:
Determines if the combo will support automatic value completion.
(Default is true).

Remarks:
Setting the AutoEdit property to True will enable automatic edit
value completion for the text area of the combo, based on the values
in the value list.. When AutoEdit is True and the user types a
character in the combo's text box, the control will search the
contents of the
Infragistics. Win..UltraWinGrid .UltraDropDownBa se.DisplayMember column
to see if it contains a value that begins with the same character. If
it does, this value will appear in the text box, with all of its
characters highlighted except the one that the user typed. If the
user types a second character, the control will check to see if it is
the next highlighted character is in the value that appeared. If it
is, the value stays and the character typed becomes deselected. If
the second character does not appear in the value, the control
searches the list again for a value that begins with the first two
characters that were typed. If one exists, it appears in the text
box; otherwise the selected text is removed and no more searching
takes place. This process continues until the user shifts the input
focus away from the control. If the UltraCombo's
Infragistics. Win.UltraWinGrid .UltraCombo. DropDownStyle has been set
to DropDownList, then setting the AutoEdit to true will enable multi-
character auto-edit functionality for the drop down list style. In
multi-character auto-edit mode, the control will select the item
whose text starts with characters typed so far. After 500
milliseconds of time span since last keystroke, a new auto-edit
session begins where the previously typed characters are discarded
and new characters are used for multi-character matching.

--- In vantage@yahoogroups .com, Tony Hughes <thughes281@ ...> wrote:
>
>
> I think the problem you are both seeing is that the combo box on
the Vantage form is "helpfully" suggesting for you.
> This was why we had to take the concatenated JOB+ASM+OPR barcode
out of our traveler, for just this reason.
>
> What happens is, after you scan the Job number, the Assembly and
Operation combo boxes refresh their dataset to reflect what
assemblies and operations are valid for the scanned Job number.
>
> Say your job has operations 10 through 150.
> Remembering that a barcode is nothing magical, just literally
keystrokes, your Tab moves the focus to the Opr dropdown.
> Your code types 1. as soon as it does the 1, the combobox
suggests "10" so now, even though you have typed 1, the value in the
combo box is now 10. So now your barcode sends the 0, but of course 0
appended to 10 is now 100.
> That's why you see the 100.
>
> You are not doing anything wrong.
>
> I am sure there is a way to tell the @#$%^& combo box to stop
suggesting, but I don't know how. If you figure that out, and are in
the Houston area anytime soon, I will buy you a beer.
>
>
>
>
> ____________ _________ _________ __
> From: Chris Thompson <chriselectrix@ ...>
> To: vantage@yahoogroups .com
> Sent: Wednesday, December 3, 2008 5:28:54 AM
> Subject: Re: [Vantage] Re: Barcode Question
>
>
> Hi Eric,
>
> I have had the exact same problem recently.
>
> I was using "*" & ToText({JobOper. OprSeq}," 0") & "$I" & "*"
>
> I was having trouble with operation 10 where it was scanning it as
100, but all of the others were ok.
>
> If I scanned our code into word or excel etc it would scan as 10,
so this pointed the problem to Vantage.
>
> I have also tried "*" & ToText({JobOper. OprSeq}," 0.00" & "."
& "$I" & "*" but that doesn't work.
>
> Secondly, I have found that to format a number field within a
formula, it works better if you use e.g. ({number.field} ,"0"). I
believe, but I could be wrong that if you put i.e.
({number.field} ,"0,000.00" ) the number will format i.e. 1,234.56.
>
> I must say, I started writing this email thinking that I had sorted
the problem myself, but now that I have tested it again, it doesn't
work.
>
> Have you tried scanning the suspect numbers into Excel or Word to
see if they scan alright?
>
> Also have you tried leaving the TAB off at the end of the barcode?
>
> Also, I don't think this will may any difference, but when I used
cstr, it made by barcode much bigger than my barcode was when I was
using ToText and as far as I am aware they do the same thing, so if
space is an issue in your design, ToText may be a good solution.
>
> If you find a solution, I would be greatful if you could pass it on.
>
> I am going to ask Epicor to have a look in the meantime.
>
> Thanks,
>
> CHRIS
>
> ____________ _________ _________ __
> From: homestyleindustries <homestyleindustrie s @...>
> To: vantage@yahoogroups .com
> Sent: Tuesday, December 2, 2008 11:58:50 PM
> Subject: [Vantage] Re: Barcode Question
>
> After some more testing we figured out that the ,0 has no effect
> outside of leaving the decimal places off. I took out the ,0 out
and
> it still populated the operation sequence number as 700, whith two
> decimal places obviously. So, new question is why would Vantage
bring
> in last operation of a job with an extra 0? I tried this on
multiple
> jobs and had the same results.
>
> --- In vantage@yahoogroups .com, "homestyleindustrie s"
> <homestyleindustrie s@...> wrote:
> >
> > Here is my problem:
> >
> > I have a job with 6 operations. I created a formula to populate
> > barcodes for each operation to be used with MES. The formula is:
> >
> > "*" + {JobHead.JobNum} + "$I" + cstr({JobAsmbl. AssemblySeq} )
+ "$I"
> +
> > cstr({JobOper. OprSeq},0) + "$I" + "*"
> >
> > I have tried a number of different formulas and this seems to
work
> the
> > best. Yet, for whatever reason on the very last operation it adds
> an
> > extra 0 to the Operation Sequence Number. I figure this is
> populating
> > the irregularity from the (JobOper.OprSeq} ,0). My understanding
is
> > that the ,0 is suppose to leave off the decimal places, which it
> does.
> > With that said, my question is how do I fix this? How can I get
it
> to
> > populate operation 60 instead of 600, while keeping the decimal
> places
> > off?
> >
> > Thanks in advance.
> >
> > Eric
> >
>
> [Non-text portions of this message have been removed]
>
>
>
>
>
>
> [Non-text portions of this message have been removed]
>

[Non-text portions of this message have been removed]

[Non-text portions of this message have been removed]

[Non-text portions of this message have been removed]

[Non-text portions of this message have been removed]






[Non-text portions of this message have been removed]

[system]

Thank you for the tip, if this were C or Visual Basic, I'd be done by now.
But with the way these forms and their code is, I don't see an event to hook in to?
I would say OnLoad of the form, right, and set the Object.Property = x.
But I have no idea here. Where would I put the code?

Thank you,

Tony




________________________________
From: bw2868bond <bwalker@...>
To: vantage@yahoogroups.com
Sent: Wednesday, December 3, 2008 8:00:26 AM
Subject: [Vantage] Re: Barcode Question


Try setting the AutoEdit property to false (if not available in
designer propeties, it will have to be done in code)

here is a description of the property:

public bool AutoEdit { set; get; }
Member of Infragistics. Win.UltraWinGrid .UltraCombo

Summary:
Determines if the combo will support automatic value completion.
(Default is true).

Remarks:
Setting the AutoEdit property to True will enable automatic edit
value completion for the text area of the combo, based on the values
in the value list. When AutoEdit is True and the user types a
character in the combo's text box, the control will search the
contents of the
Infragistics. Win.UltraWinGrid .UltraDropDownBa se.DisplayMember column
to see if it contains a value that begins with the same character. If
it does, this value will appear in the text box, with all of its
characters highlighted except the one that the user typed. If the
user types a second character, the control will check to see if it is
the next highlighted character is in the value that appeared. If it
is, the value stays and the character typed becomes deselected. If
the second character does not appear in the value, the control
searches the list again for a value that begins with the first two
characters that were typed. If one exists, it appears in the text
box; otherwise the selected text is removed and no more searching
takes place. This process continues until the user shifts the input
focus away from the control. If the UltraCombo's
Infragistics. Win.UltraWinGrid .UltraCombo. DropDownStyle has been set
to DropDownList, then setting the AutoEdit to true will enable multi-
character auto-edit functionality for the drop down list style. In
multi-character auto-edit mode, the control will select the item
whose text starts with characters typed so far. After 500
milliseconds of time span since last keystroke, a new auto-edit
session begins where the previously typed characters are discarded
and new characters are used for multi-character matching.

--- In vantage@yahoogroups .com, Tony Hughes <thughes281@ ...> wrote:
>
>
> I think the problem you are both seeing is that the combo box on
the Vantage form is "helpfully" suggesting for you.
> This was why we had to take the concatenated JOB+ASM+OPR barcode
out of our traveler, for just this reason.
>
> What happens is, after you scan the Job number, the Assembly and
Operation combo boxes refresh their dataset to reflect what
assemblies and operations are valid for the scanned Job number.
>
> Say your job has operations 10 through 150.
> Remembering that a barcode is nothing magical, just literally
keystrokes, your Tab moves the focus to the Opr dropdown.
> Your code types 1. as soon as it does the 1, the combobox
suggests "10" so now, even though you have typed 1, the value in the
combo box is now 10. So now your barcode sends the 0, but of course 0
appended to 10 is now 100.
> That's why you see the 100.
>
> You are not doing anything wrong.
>
> I am sure there is a way to tell the @#$%^& combo box to stop
suggesting, but I don't know how. If you figure that out, and are in
the Houston area anytime soon, I will buy you a beer.
>
>
>
>
> ____________ _________ _________ __
> From: Chris Thompson <chriselectrix@ ...>
> To: vantage@yahoogroups .com
> Sent: Wednesday, December 3, 2008 5:28:54 AM
> Subject: Re: [Vantage] Re: Barcode Question
>
>
> Hi Eric,
>
> I have had the exact same problem recently.
>
> I was using "*" & ToText({JobOper. OprSeq}," 0") & "$I" & "*"
>
> I was having trouble with operation 10 where it was scanning it as
100, but all of the others were ok.
>
> If I scanned our code into word or excel etc it would scan as 10,
so this pointed the problem to Vantage.
>
> I have also tried "*" & ToText({JobOper. OprSeq}," 0.00" & "."
& "$I" & "*" but that doesn't work.
>
> Secondly, I have found that to format a number field within a
formula, it works better if you use e.g. ({number.field} ,"0"). I
believe, but I could be wrong that if you put i.e.
({number.field} ,"0,000.00" ) the number will format i.e. 1,234.56.
>
> I must say, I started writing this email thinking that I had sorted
the problem myself, but now that I have tested it again, it doesn't
work.
>
> Have you tried scanning the suspect numbers into Excel or Word to
see if they scan alright?
>
> Also have you tried leaving the TAB off at the end of the barcode?
>
> Also, I don't think this will may any difference, but when I used
cstr, it made by barcode much bigger than my barcode was when I was
using ToText and as far as I am aware they do the same thing, so if
space is an issue in your design, ToText may be a good solution.
>
> If you find a solution, I would be greatful if you could pass it on.
>
> I am going to ask Epicor to have a look in the meantime.
>
> Thanks,
>
> CHRIS
>
> ____________ _________ _________ __
> From: homestyleindustries <homestyleindustrie s @...>
> To: vantage@yahoogroups .com
> Sent: Tuesday, December 2, 2008 11:58:50 PM
> Subject: [Vantage] Re: Barcode Question
>
> After some more testing we figured out that the ,0 has no effect
> outside of leaving the decimal places off. I took out the ,0 out
and
> it still populated the operation sequence number as 700, whith two
> decimal places obviously. So, new question is why would Vantage
bring
> in last operation of a job with an extra 0? I tried this on
multiple
> jobs and had the same results.
>
> --- In vantage@yahoogroups .com, "homestyleindustrie s"
> <homestyleindustrie s@...> wrote:
> >
> > Here is my problem:
> >
> > I have a job with 6 operations. I created a formula to populate
> > barcodes for each operation to be used with MES. The formula is:
> >
> > "*" + {JobHead.JobNum} + "$I" + cstr({JobAsmbl. AssemblySeq} )
+ "$I"
> +
> > cstr({JobOper. OprSeq},0) + "$I" + "*"
> >
> > I have tried a number of different formulas and this seems to
work
> the
> > best. Yet, for whatever reason on the very last operation it adds
> an
> > extra 0 to the Operation Sequence Number. I figure this is
> populating
> > the irregularity from the (JobOper.OprSeq} ,0). My understanding
is
> > that the ,0 is suppose to leave off the decimal places, which it
> does.
> > With that said, my question is how do I fix this? How can I get
it
> to
> > populate operation 60 instead of 600, while keeping the decimal
> places
> > off?
> >
> > Thanks in advance.
> >
> > Eric
> >
>
> [Non-text portions of this message have been removed]
>
>
>
>
>
>
> [Non-text portions of this message have been removed]
>






[Non-text portions of this message have been removed]

[system]

Hi All,

Ok, I have been informed that this issue ahs been addressed in .408 which they are working on at present.

You need to find this line in your xyz.mfgsys file <SelectTextOnEnter value="False" bool="" /> and change the False to True.

Im not 100% sure if this has to be done on the server or on your local files.

I anyone has any idea Id be appreciated.

They also recommend saving the file as i.e. xyzmes.mfgsys then re-configuring the icon to access it.

Thanks,


CHRIS



________________________________
From: Tony Hughes <thughes281@...>
To: vantage@yahoogroups.com
Sent: Wednesday, December 3, 2008 7:17:32 PM
Subject: Re: [Vantage] Re: Barcode Question


Thank you for the tip, if this were C or Visual Basic, I'd be done by now.
But with the way these forms and their code is, I don't see an event to hook in to?
I would say OnLoad of the form, right, and set the Object.Property = x.
But I have no idea here. Where would I put the code?

Thank you,

Tony

____________ _________ _________ __
From: bw2868bond <bwalker@adcocircuit s.com>
To: vantage@yahoogroups .com
Sent: Wednesday, December 3, 2008 8:00:26 AM
Subject: [Vantage] Re: Barcode Question

Try setting the AutoEdit property to false (if not available in
designer propeties, it will have to be done in code)

here is a description of the property:

public bool AutoEdit { set; get; }
Member of Infragistics. Win.UltraWinGrid .UltraCombo

Summary:
Determines if the combo will support automatic value completion.
(Default is true).

Remarks:
Setting the AutoEdit property to True will enable automatic edit
value completion for the text area of the combo, based on the values
in the value list. When AutoEdit is True and the user types a
character in the combo's text box, the control will search the
contents of the
Infragistics. Win.UltraWinGrid .UltraDropDownBa se.DisplayMember column
to see if it contains a value that begins with the same character. If
it does, this value will appear in the text box, with all of its
characters highlighted except the one that the user typed. If the
user types a second character, the control will check to see if it is
the next highlighted character is in the value that appeared. If it
is, the value stays and the character typed becomes deselected. If
the second character does not appear in the value, the control
searches the list again for a value that begins with the first two
characters that were typed. If one exists, it appears in the text
box; otherwise the selected text is removed and no more searching
takes place. This process continues until the user shifts the input
focus away from the control. If the UltraCombo's
Infragistics. Win.UltraWinGrid .UltraCombo. DropDownStyle has been set
to DropDownList, then setting the AutoEdit to true will enable multi-
character auto-edit functionality for the drop down list style. In
multi-character auto-edit mode, the control will select the item
whose text starts with characters typed so far. After 500
milliseconds of time span since last keystroke, a new auto-edit
session begins where the previously typed characters are discarded
and new characters are used for multi-character matching.

--- In vantage@yahoogroups .com, Tony Hughes <thughes281@ ...> wrote:
>
>
> I think the problem you are both seeing is that the combo box on
the Vantage form is "helpfully" suggesting for you.
> This was why we had to take the concatenated JOB+ASM+OPR barcode
out of our traveler, for just this reason.
>
> What happens is, after you scan the Job number, the Assembly and
Operation combo boxes refresh their dataset to reflect what
assemblies and operations are valid for the scanned Job number.
>
> Say your job has operations 10 through 150.
> Remembering that a barcode is nothing magical, just literally
keystrokes, your Tab moves the focus to the Opr dropdown.
> Your code types 1. as soon as it does the 1, the combobox
suggests "10" so now, even though you have typed 1, the value in the
combo box is now 10. So now your barcode sends the 0, but of course 0
appended to 10 is now 100.
> That's why you see the 100.
>
> You are not doing anything wrong.
>
> I am sure there is a way to tell the @#$%^& combo box to stop
suggesting, but I don't know how. If you figure that out, and are in
the Houston area anytime soon, I will buy you a beer.
>
>
>
>
> ____________ _________ _________ __
> From: Chris Thompson <chriselectrix@ ...>
> To: vantage@yahoogroups .com
> Sent: Wednesday, December 3, 2008 5:28:54 AM
> Subject: Re: [Vantage] Re: Barcode Question
>
>
> Hi Eric,
>
> I have had the exact same problem recently.
>
> I was using "*" & ToText({JobOper. OprSeq}," 0") & "$I" & "*"
>
> I was having trouble with operation 10 where it was scanning it as
100, but all of the others were ok.
>
> If I scanned our code into word or excel etc it would scan as 10,
so this pointed the problem to Vantage.
>
> I have also tried "*" & ToText({JobOper. OprSeq}," 0.00" & "."
& "$I" & "*" but that doesn't work.
>
> Secondly, I have found that to format a number field within a
formula, it works better if you use e.g. ({number.field} ,"0"). I
believe, but I could be wrong that if you put i.e.
({number.field} ,"0,000.00" ) the number will format i.e. 1,234.56.
>
> I must say, I started writing this email thinking that I had sorted
the problem myself, but now that I have tested it again, it doesn't
work.
>
> Have you tried scanning the suspect numbers into Excel or Word to
see if they scan alright?
>
> Also have you tried leaving the TAB off at the end of the barcode?
>
> Also, I don't think this will may any difference, but when I used
cstr, it made by barcode much bigger than my barcode was when I was
using ToText and as far as I am aware they do the same thing, so if
space is an issue in your design, ToText may be a good solution.
>
> If you find a solution, I would be greatful if you could pass it on.
>
> I am going to ask Epicor to have a look in the meantime.
>
> Thanks,
>
> CHRIS
>
> ____________ _________ _________ __
> From: homestyleindustries <homestyleindustrie s @...>
> To: vantage@yahoogroups .com
> Sent: Tuesday, December 2, 2008 11:58:50 PM
> Subject: [Vantage] Re: Barcode Question
>
> After some more testing we figured out that the ,0 has no effect
> outside of leaving the decimal places off. I took out the ,0 out
and
> it still populated the operation sequence number as 700, whith two
> decimal places obviously. So, new question is why would Vantage
bring
> in last operation of a job with an extra 0? I tried this on
multiple
> jobs and had the same results.
>
> --- In vantage@yahoogroups .com, "homestyleindustrie s"
> <homestyleindustrie s@...> wrote:
> >
> > Here is my problem:
> >
> > I have a job with 6 operations. I created a formula to populate
> > barcodes for each operation to be used with MES. The formula is:
> >
> > "*" + {JobHead.JobNum} + "$I" + cstr({JobAsmbl. AssemblySeq} )
+ "$I"
> +
> > cstr({JobOper. OprSeq},0) + "$I" + "*"
> >
> > I have tried a number of different formulas and this seems to
work
> the
> > best. Yet, for whatever reason on the very last operation it adds
> an
> > extra 0 to the Operation Sequence Number. I figure this is
> populating
> > the irregularity from the (JobOper.OprSeq} ,0). My understanding
is
> > that the ,0 is suppose to leave off the decimal places, which it
> does.
> > With that said, my question is how do I fix this? How can I get
it
> to
> > populate operation 60 instead of 600, while keeping the decimal
> places
> > off?
> >
> > Thanks in advance.
> >
> > Eric
> >
>
> [Non-text portions of this message have been removed]
>
>
>
>
>
>
> [Non-text portions of this message have been removed]
>

[Non-text portions of this message have been removed]






[Non-text portions of this message have been removed]