Event Ticketing Admission with Access and Barcodes?

[dar77]

I guess this would be under forms, since that is the main component... I am a newcomer to the Access world. I already have a PHP form online (with credit card payment) that gathers information from people who buy tickets for an event I am hosting and puts them in a mySQL database. It's all working perfectly, and I've exported the data into excel spreadsheets and opened them on my computer.

MY QUESTION is how do I use Access to reference this data when a person enters the event? I have already assigned every ticket a barcode (which is their employee ID number), and those numbers are on my excel spreadsheet along with all of their other data.

What I assume I need:
Simple text box where I can scan the data (number) from the barcode into


Submit button, onclick references the table and sees whether a record for that person exists.
If there is a row with that employee ID in it, a "used" value is entered in their row, so that the ticket cannot be used again.
If there is not a row with that number (the ticket doesn't exist), I have feedback telling me that they have not purchased a ticket.

I can't have tickets being used more than once

Really what I am doing with all of this complicated work is scanning employees and either getting feedback of "yes" they purchased a ticket, or "no" they did not.

Since I have NO access experience whatsoever, any and all help is appreciated. I have been watching all kinds of tutorials online, but am not too comfortable with it all. Any templates I can start from? I want to learn access to use this in the future.

If you're feeling really helpful and don't have anything to do, I might even pay you to quickly build this for me and send it over, or you can just do it for free if youre really bored. I have a month and a half to find a solution.

[pbaldy]

I'm not surprised nobody is bored enough to do it for you. Lots of people here willing to help you do it yourself though. A month and a half is plenty of time to learn. Look at opening a recordset on an SQL statement, testing it for EOF, If/Then blocks and message boxes. Nothing you've described is terribly difficult.