>> The only thing I am concerned about is dynamic input. If a user scans
>will
>> the data end up in the correct field. I thought I heard Code 39 was good
>
>> for this.
>>
>> Any suggestions out there?
>>
>It's been a while since I did barcode stuff actively, but back in '89 when
>I
>was first doing it, I had the same concerns you did about dynamic input.
>
>I actually had small bits of code, sorta like a prefix and a suffix, that
>delimited the data scanned so that when the FoxBase+ app (later FP1)
>read in the data, it had something to parse. Hey, it wasn't pretty, and
>there was no subclassing going on, but it worked.
>
>I was concerned mainly that the user would not always put the data in
>in the order the programmer intended. <g>
>
>Code 39 is what I used. I was even able to setup a paper menu that
>contained carriage returns, and Page Downs (yeah, page downs to get
>you all the way through a READ).
>
>I had some hand held units, one from Intermec, and some from CMT
>(Corvallis MicroTechnology, I think). The one from Intermec had its
>own proprietary language called Interactive Reader Language or IRL
>for short. They used to call me the Duke of IRL when I worked with
>what seemed like programming in an EDLINesque language. The
>CMT units actually had a version of dBase on board and had a bigger
>screen (or is that form).
>
>Anyhow, just my two cents...

Carl

Back in '89? The 'Duke'? Did you mean 1889? (g)

Thanks
Tom