Barcode Scanner Invalid Scan

[nick243]

I am trying to deceiver this code here to see why a process is causing an invalid scan. This had previously been working but it reached its 2 GB limit and started having issues. I ran the compact and repair and it worked but I am still having issues with this code. I scan a sample ticket that reads like this
1 04 0331 83233 01. I can't scan the full number to the table without an invalid scan. This table is then exported to a flash drive then entered in a mainframe. Here is the code

Option Compare Database
Dim ScanTimeVar, StoreVar, LookUpVar ', CurrentVar, DiffVar

Private Sub Form_Load()


ScanTimeVar = Now()
DoCmd.GoToRecord , , acNewRec
End Sub

Private Sub Scan_BeforeUpdate(Cancel As Integer)
Forms![ScannerForm-Main]![LastTime] = Now()
StoreVar = (Mid(Me![Scan], 4, 4))
If IsNull(StoreVar) = False And IsNumeric(StoreVar) = True Then
StoreVar = Int(StoreVar)
LookUpVar = DLookup("STORE", "OpenStores", "STORE = " & StoreVar)
Else
LookUpVar = Null
End If

If Left(Me![Scan], 3) <> "104" Or Len(Me!Scan) <> 14 Or IsNull(LookUpVar) = True Then
Beep
Beep
Beep
Beep
Beep
MsgBox "Invalid Scan", vbCritical
Beep
Beep
Beep
Beep
Beep
'SendKeys "{Esc}"
'Me!Scan = Null
DoCmd.CancelEvent
SendKeys "{Esc}"
SendKeys "{Esc}"

End If

End Sub

Any suggestions?

I have tried removing the If left statement that was sending the invalid scan but then I am not able to import that scan into the mainframe.

Thanks,
Nick

[John_G]

Is the scan value with or without the blanks? Your sample that "looks like this" does contain blanks, but your code seems to assume that it doesn't.

Which is correct?

You could use msgbox or debug.print at the start of the procedure to see what Me![Scan] actually contains - maybe the problem is not in this procedure.

[nick243]

This sample is without blanks when it is scanned in. I have found since posting this that I am able to scan in the barcodes once I take out the code "if left me scan" statement. I used the word pad to do test scans and I figured out that my first scanner was incorrectly programmed. I have a correct scanner now as it seems. I am now having an issue with focusing by having the table pated into the mainframe. I have to click the mainframe to the focus or the go to record statement will fail. This seems to be my problem now.