>>>We're using U.r.U finger scanner for our HRM systems with Payroll module. At first, we use VB with Pentacom's OCX control for interfacing with the finger scanner. If using Access MDB to handle the binary data emits by the scanner, there is no problem. With VFP table however, it can not handle the data (Memo field). This time, we tried VFP form with the same OCX control expecting it to work with DBF (Memo Binary or ordinary Memo) as field type but the data have different value. The CREATEBINARY() function does not help either.
>>>
>>>Is VFP capable of handling Binary Data? How do you handle Binary Data in VFP?
>>>
>>>Any help extended would be highly appreciated.
>>In addition to DF's offer:
>>Have you assured the data in the VFP memo is valid data?
>
>This is exactly my problem. Actually the OCX emits binary data. It is not a file.
>
>

>cBinary = Thisform.OleOCX.GetFingerPrint()
>Replace mydbffile.memofield With cBinary
>

>Above code successfully save the contents of the cBinary variable to a memo field (memo binary) but I don't know if it is a valid data.
>

>cBinaryCheck = Thisform.OleOCX.CheckFingerPrint(mydbffile.memofield)
>

>it always returns .T. even if the saved fingerprint was of my Thumb finger whereas scanned one was my index finger.
>
>>There maybe a GETCHUNK method available, check your control documentation.

Jess,
VFP can handle binary data and you can store any binary data to a memo (binary) - even an exe file as is. Even char binary fields can keep data as is (including chr(0)). An FTP file entry simply has a block header then the data as is. No conversion is done on memo side. That's OCX that cannot handle binary directly but convert to 8 bits byte array (BSTR to unsigned8bit char array - BstrToVector). CreateBinary() calls VectorToBstr to create back BSTR. If you could find a method in your OCX that would save w/o a conversion use it. See CreateBinary() help for details.
PS: I would hate if it didn't return .T. thumb vs index finger. Track pattern is same:)
Cetin