Access 2010 to Access 2019 Issue

[jlam]

Hi All,

First time on this forum. I'm looking for some help to troubleshoot a problem on a database that I didn't build. I also have little experience in Access and am learning on the fly. I have a database written using Access 2010.

The process is as follows: use a scanner to read a barcode and enter into a form then "tabs" to the next line. The database was programmed to use conditional formatting (DLookup) to identify if the input data was the same from another list using a query. After all of that is complete, a macro is run to do some other stuff (which I'm not quite sure what it does yet).

------------------------------------
Option Compare Database


Private Sub Box_Label_AfterUpdate()


Call Clear_Verification
End Sub




Private Sub Form_AfterDelConfirm(Status As Integer)
Call Clear_Verification
End Sub


Function Clear_Verification()


On Error GoTo Err_Clear_Verification


[Forms]![Verification]![Pallet_Verify].Value = False
[Forms]![Verification]![Message_Verify].Value = ""


Exit_Clear_Verification:
Exit Function


Err_Clear_Verification:
MsgBox Err.Description
Resume Exit_Clear_Verification
End Function
--------------------------------
Everything used to work when Access 2010 was still loaded on the computers, but now that we have migrated to Access 2019, the database will not enter all of the characters from the barcode scanner. I have tested numerous barcode scanners and numerous computers so I don't think it's the scanner or computer. It also doesn't feel like coincidence that this only started after moving to Access 2019. I am thinking the right way to have coded this I would move the DLookup into the Macro and have the macro run on an event trigger. I'm just not sure if this will actually fix the problem since I don't know what the problem is.

Has anyone else run into something similar or could provide some insight to where I should go from here?

Thanks,

confused user

[ArviLaanemets]

Was only Access upgraded, or is computer (or it's OS), from where the database is operated, changed too? Reading barcodes depends heavily on regional settings and used font, as much as I remember from my experience some 10 years ago.

[ranman256]

I don’t think it’s access. We use barcode readers on ALL versions of access, 2019,2010,and earlier.
it works on all.
It may be scanner settings.

[jlam]

We upgraded the OS on 2 of the computers/scanner tested, and didn't upgrade the OS on one of the computers/scanner tested.

[jlam]

We didn't change any drivers or settings on the barcode scanners, the scanners are used for input of the master table as well and that isn't having a problem.