I have messed around with this sufficient to get to the point where with a script I can enter find mode and then use a custom dialog box with two inputs (one for Item Name, and one for UPC). It looks like if I put a value into either one or the other, it performs the search. If I enter data into the Item Name field, the search performs really quickly. If I do it into the UPC field, it takes forever. Is this simply because that field is not indexed properly?
Any assistance is greatly appreciated.
Possibly. Or maybe it just takes the scanner a while to input the data. Do you really need the custom dialog box here? Might be simpler to scan/input the data into global fields and then use a script to enter find mode and perform the find--or use a relationship to match to a related record when it comes to using the bar code.
Thanks PhilModJunk! I appreciate the input. Your suggestion sounds like something I'd like to pursue. My problem is I am literally at ground level on this. I would not know where to start with your suggestion. Once I start to get the hang of methods and syntaxes within FM, I should be a little more on auto-pilot. Its very different from the dev environments I'm used to.
Any direction would be very much appreciated.
Oh and by the way, I added indexes to my SQL server tables on the appropriate fields and now the searches do not take long at all. Looks like it was an indexing issue in this instance.
In an ideal world, I'd love to have my users just scan one value and the application is smart enough to go find the associated Item Name and apply the find.
Do that all the time, either from a bar code scan or from user entered/selected data and there are multiple options. (I use the camera and insert from device to scan bar codes, but the same method should work for the blue tooth scanner.)
For a scanned bar code, I might well use a relationship where the field with the scanned barcode is used to match to a table of products and their bar code fields.