>Specific questions are:
>a) Does it matter what type of barcode I adopt.

All things considered, Code39 is the simplest barcode to use but it is not as dense as say 128. Avoid all UPC codings for obvious reasons. You can use code39 fonts (available as freeware) and print with a Windows printer. If you do not use a regular barcode printer, other code fonts will have to be purchased.

>b) Would a cheap (<$500) printer handle the production of barcodes for 500 employees. (My guess is Yes - but does anyone have any particular printer they can reccommend or diss)

There are several good label printers around $500 now from Eltron, Cognitive Solutions and even Brother. These are full-fledged barcode printers with windows drivers that include almost every barcode in use today. Use a thermal-transfer as direct thermal will fade with time. I have printed on business card size labels, stuck them to card stock, and use business card laminators from OfficeMax to protect them. These printers are B/W and print at 208 DPI, so graphics can be so-so. Here, I print on Avery ID Badge photo-grade paper with an Epson inkjet at high rez and include an employee picture, but this is labor intensive in large numbers. On the high side, Eltron makes a great ID card printer for $3-4K!

Check out www.systemid.com and have them send you a catalog - great resource, fine people, great prices.

>c) What reader would you recommend. It will probably read 100-200 cards/day.

If physically possible, I prefer "swipe" card readers for this application. You can mount them to the terminal for security, no cable strain, inexpensive... They are available to read mag stripe, barcode, and mag/barcode. A good serial barcode reader in a brand name is <$200, no name can be <$75. Make sure you get one with "decoded" output, no need to interpret the codes directly! I also prefer a serial output over a keyboard wedge. A keyboard wedge will enter the decoded barcode info into the keyboard buffer as if it were typed from the keyboard. This is fine for a "canned" application that you are adding barcode reading capabilities, but the correct field MUST be selected or you could over-type something important. This will also be the case in your app. I have seen complex coding schemes to allow the wedge to function properly, but believe me the serial implementation is much easier as it generates an event on a scan (let me know if you need help with MSCOMM32 and scanners). These are also available from SystemID.

It must integrate into VFP app.
>
>There is no requirement for any of this equipment to be mobile.
>
>TIA