Barcode Question

Yahoo Archive
21
Hi Tony,

I don't know if this will help with your Opr Seq where they aren't in intervals of 10, but $X before my last $I is also working for me.

I think this is Delete rather than Backspace.

Have you tried this one?

Cheers,


CHRIS




________________________________
From: Chris Thompson <chriselectrix@...>
To: vantage@yahoogroups.com
Sent: Thursday, December 4, 2008 10:52:25 AM
Subject: Re: [Vantage] Re: Barcode Question


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@yahoo. com>
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@adcocircui t 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]






[Non-text portions of this message have been removed]
22
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 <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]
>
23
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]
24
A quick question from a barcode newbie. Why do you need the * at
either end of the barcode?

I am at the very beginning of the whole MES/barcode implementation
thing and any help is appreciated.

Andrew
--- 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]
>
25
It has to do with the Code39 format only. Code128 doesn't use bookends. In fact, I think asterisk enclosures are specific to Code39 only.

The *'s tell the scanner begin/end.



-----Original Message-----
From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of andrew.tapper
Sent: Thursday, December 04, 2008 1:50 PM
To: vantage@yahoogroups.com
Subject: [Vantage] Re: Barcode Question

A quick question from a barcode newbie. Why do you need the * at
either end of the barcode?

I am at the very beginning of the whole MES/barcode implementation
thing and any help is appreciated.

Andrew
--- 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]
>



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

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
26
It's only required if you are creating a bar code in Crystal Reports.

Barcode 39 requires an * at the beginning and end of the barcode to
act as start & stop characters.

Crystal Reports barcode 39 is not a "real" barcode; it is actually a
font. Since it is a font, you, the programmer, need to insert the
stop/start characters into your barcode field.

If you are using true bar-coding software like Label Matrix or
Bartender or TalBarCode Active X controls, this is not necessary.
These are true barcodes and Code 39 already has the * stop/start
characters built into those barcode fields.

Code 39 is the only barcode which uses the * character.

Lynn



--- In vantage@yahoogroups.com, "andrew.tapper" <atapper@...> wrote:
>
> A quick question from a barcode newbie. Why do you need the * at
> either end of the barcode?
>
> I am at the very beginning of the whole MES/barcode implementation
> thing and any help is appreciated.
>
> Andrew
> --- 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]
> >
>