Author Topic: Index was outside the bounds of the array  (Read 6660 times)

Hugove

  • Newbie
  • *
  • Posts: 43
Index was outside the bounds of the array
« on: July 12, 2013, 05:19:57 am »
Hi Guys,

Urgent help needed here! I searched the forums but the answer to this q below is unrelated to me. I run Sambapos 2.99 and my kitchen printer kicks out this error.

---------------------------
Bilgi
---------------------------


There is a problem while printing. Please review printer and printer template settings.



Error Message:

Index was outside the bounds of the array.

   
---------------------------
OK   
---------------------------

JohnS

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 677
Re: Index was outside the bounds of the array
« Reply #1 on: July 12, 2013, 05:42:51 am »
Post your printer template.
Is it all or just one?
SambaPOS - POS'n the World, one Terminal at a time.

Hugove

  • Newbie
  • *
  • Posts: 43
Re: Index was outside the bounds of the array
« Reply #2 on: July 12, 2013, 05:50:14 am »
Hi John,

Just this one

Header:
<EB>
<T>{TABLE USER}
<F>-
<L00>Date:{TICKET DATE}
<L00>Time:{TIME}

<F>-

[<C01>Note
<L>
{NOTE}
<L>]
<DB>


group template:
<C01>{PRODUCT GROUP}
<C>

Line Template:

<T><L00>{QUANTITY} {NAME}
        * {PROPERTIES}

Gift line template:

<L00>{QUANTITY} {NAME}
        * {PROPERTIES}

Void line template:

<L00>**VOID**{QUANTITY} {NAME}
        * {PROPERTIES}

Footer template:

<EB>
<L>
<L00>Waitron:  {TICKETTAG:Waitron}
<L00>Table No: {TABLE}
<L00>Guests:   {TICKETTAG:Guest Count}
<DB>

JohnS

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 677
Re: Index was outside the bounds of the array
« Reply #3 on: July 12, 2013, 06:00:27 am »
Why is there a <T> in your line template?
What did you change just before this happened?
SambaPOS - POS'n the World, one Terminal at a time.

Hugove

  • Newbie
  • *
  • Posts: 43
Re: Index was outside the bounds of the array
« Reply #4 on: July 12, 2013, 06:05:25 am »
Who knows??? Damn I need to get use to these templates. It was indeed the problem.

Working now.

Best