Hi Julio, Not a stupid question at all! The hex string representation is simply the way this reader has decided to encode and transfer the RFID number. The actual RFID number has to be interoperable with other systems that expect it in the “regular” format. Also, users will sometimes hand enter the number which is printed on the tag and that would be in the “regular” format as well and would need to match what is in the database.
The real question is why this particular RFID reader has decided to encode the number in this way when every single reader I’ve dealt with in the past decade all do it the same “regular” way. Sigh. -- Cannon.Smith Synergy Farm Solutions Inc. Hill Spring, AB Canada 403-626-3236 <can...@synergyfarmsolutions.com> <www.synergyfarmsolutions.com> > On Apr 17, 2017, at 3:59 PM, Julio Carneiro via 4D_Tech > <4d_tech@lists.4d.com> wrote: > > Forgive my stupid question: why do you need to convert the hex string to > number? Can’t you simply use it as your RFID? (of course you’d have to > increase your key field to 16 chars). You’re already handling it as a string, > why change? ********************************************************************** 4D Internet Users Group (4D iNUG) FAQ: http://lists.4d.com/faqnug.html Archive: http://lists.4d.com/archives.html Options: http://lists.4d.com/mailman/options/4d_tech Unsub: mailto:4d_tech-unsubscr...@lists.4d.com **********************************************************************
