Greetings Access gurus. First time posting here so be gentle.
While I am not an Access expert, I know enough to be dangerous. I have recently did some updating/upgrading to a database that my company uses and have a "bug".
For a new order our Shipping clerk would scan in a serial number (for our product to be shipped), it would auto tab to the next field, then scan the Order number, auto tab, it would auto populate the "Sold to field" and auto tab to create a new record.
Here's what is now broken.
After the first record is created, our Clerk scans in the next Serial number and auto tabs to the next field > it fills down from the previous record and stays on that field and never auto tabs. It waits for a manual tab.
The embedded macros for the field is super simple.
I thought the initial wait = yes was the problem, changed to know but still sits on that field and waits. It never tabs.
The original database format was 2003 and everything worked fine prior to upgrading to 2013 (we are now on 2019).
Did something change with the macro handling from 2003 to 2013? I will attach screen shot of the form for review.
Thanks in advance for any assistance!
While I am not an Access expert, I know enough to be dangerous. I have recently did some updating/upgrading to a database that my company uses and have a "bug".
For a new order our Shipping clerk would scan in a serial number (for our product to be shipped), it would auto tab to the next field, then scan the Order number, auto tab, it would auto populate the "Sold to field" and auto tab to create a new record.
Here's what is now broken.
After the first record is created, our Clerk scans in the next Serial number and auto tabs to the next field > it fills down from the previous record and stays on that field and never auto tabs. It waits for a manual tab.
The embedded macros for the field is super simple.
Code:
If [Forms]![Order Entry Form]![SERIAL NUMBERS.OrdNumber] Is Null Then
Sendkeys
Keystrokes ^'
Wait = Yes
End if
If [Forms]![Order Entry Form]![SERIAL NUMBERS.OrdNumber] Is Not Null
Sendkeys
Keystrokes {tab}
Wait = No.
End if.
I thought the initial wait = yes was the problem, changed to know but still sits on that field and waits. It never tabs.
The original database format was 2003 and everything worked fine prior to upgrading to 2013 (we are now on 2019).
Did something change with the macro handling from 2003 to 2013? I will attach screen shot of the form for review.
Thanks in advance for any assistance!