Troy, In our materials management group, (stockrooms), wireless barcode readers are used to interact with SAP. Talk to a good vendor you might be able to go wireless.
Myron -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Troy Sosamon Sent: Friday, July 11, 2003 7:35 PM To: RBASE-L Mailing List Subject: [RBASE-L] - Re: Barcodes There is nothing magical about bar code readers. They just read in numbers or characters and will input them just like you typed it on the keyboard. There are about 5000 different bar code readers. Some attach as a wedge between the keyboard and the pc and others plug into a usb port. I am sure there are serial ones too. Just barcode the employee id on their id badge and then they can scan it in, do a lookup of the number and you are off to the races. Has anyone seen a bar code scanner designed to work at long range (30 feet) outside? The scanners we have will read the bar code if you can hit it, but you can't see the lazer to aim them. Troy -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Javier Valencia Sent: Friday, July 11, 2003 3:14 PM To: RBASE-L Mailing List Subject: [RBASE-L] - Re: Passwords can be a pain in the #$!!% Dennis: Here is another though. I have been asked by a client to consider implementing a card reader that reads a bar code in the technicians ID and automatically picks their name and stores it with the work order plus it determines access rights to generated reports with confidential hourly rates, etc. I have not gotten to it yet and probably will not get to it until August but it is something to think about.... Javier, Javier Valencia, PE President Valencia Technology Group, L.L.C. 14315 S. Twilight Ln, Suite #14 Olathe, Kansas 66962-4578 Office (913)829-0888 Fax (913)649-2904 Cell (913)915-3137 -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Dennis Fleming Sent: Friday, July 11, 2003 3:55 PM To: RBASE-L Mailing List Subject: [RBASE-L] - Re: Passwords can be a pain in the #$!!% Thanks Javier (and others) for responses. One of the design criteria is minimal keystrokes. They have no mouse on the production PC's... all navigation is with tab, space bar, enter, etc. I have their idents/pwords in a table but of course that's at least two extra steps. Plus they already logged in the mnf system. If they just picked their id again, they could pick someone else's. In the prior system, obscene or bogus requests did appear occasionally and there was no way to track it down. I think I'll just ask the mnf application to write the User Ident into a text file which I will put into the work request (and delete the file each time). Dennis **** At 02:12 PM 7/11/2003 -0500, you wrote: >Dennis: >All systems that I am familiar (including the ones I have developed) that >generate work orders, have a field to store the name of the individual >(operator) requesting the work. You can have a menu that pops up whenever >they generate a work order that allows the operator to select a name from a >valid list, or you can have the menu pop-up whenever they access the >application. Since they want to store the operator id with the work order >request, the operator ID should be entered along with the other work order >information. This is the only way to do it if more that one operator uses >the system. > >Javier Valencia, PE >President >Valencia Technology Group, L.L.C. >14315 S. Twilight Ln, Suite #14 >Olathe, Kansas 66962-4578 >Office (913)829-0888 >Fax (913)649-2904 >Cell (913)915-3137 > >-----Original Message----- >From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Dennis >Fleming >Sent: Friday, July 11, 2003 1:59 PM >To: RBASE-L Mailing List >Subject: [RBASE-L] - Re: Passwords can be a pain in the #$!!% > >Thanks Dick, > >I may not have explained this very well. >There is a production system on the floor on many PC's that runs 24/7 which >monitors their product at various locations throughout the plant. They have >function keys available which can call up other programs including our app >which is for work requests. They want the operator's login ident to be >picked up by our app to be stored with the work request (they don't login >windows). The operators change throughout the day. I'm looking for a way >for them to "pass" the current operator's id to Rbase. > >Thanks, > >Dennis >***** > >At 10:36 AM 7/11/2003 -0500, you wrote: >>Dennis: Put a column in a password or dummy table with a date. Have the >>date set to today when the user first logs in. Future logins check the date >>and if it is today, do not ask again. Works here. >> >>Dick Fey >>Carpet Broker Inc. >> >>PS We also use it for certain reminders we only want to see once each day. >> >> >> >> >> >>> A customer has a manufacturing app running all the time on the shop >floor. >>> Each new user must log in when they start their shift, take breaks, etc. >>> They can jump out (and return) to our RBase app to enter a work request >>> when they see a problem. Where is a good place for the manufacturing app >>to >>> save the ident/password for us to pick up in RBase so we don't need to >ask >>> "who are you" again? (I guess they could save it in a text file, but >seems >>> a little clumsy). >>> >>> TIA, >>> >>> Dennis >>> ***** >>> Dennis Fleming >>> IISCO >>> http://www.TheBestCMMS.com >>> Phone: 570 775-7593 >>> Fax: 570 775-9797 >>> >>> >> >> >> >Dennis Fleming >IISCO >http://www.TheBestCMMS.com >Phone: 570 775-7593 >Fax: 570 775-9797 > > > Dennis Fleming IISCO http://www.TheBestCMMS.com Phone: 570 775-7593 Fax: 570 775-9797
