It looks like I figured out the cause, and it only sort of had to do
with the security prompts. Apparently, the second connection was
occuring before update was completing in the access database. The only
reason it would work when clicking the prompts was it allowed an extra
second or so for the update to happen, then run the check to get the
next number. I somewhat adjusted for this by putting a timeout in the
code, which I dont really like, but even a delay of 500 milliseconds
makes it work.
I am currently working on a PO form for our company and have run into a
bit of a snag. I have one one database with two tables that populate a
list of vendors and a list of PO #'s.On the form is a Get PO button that
connects to the databse, gets the first available PO # that is
available, updates the record to in use and addes a unique ID #
(generated off the curren time of when the button was clicked) and then
does another connection to the same database to get the PO where the # =
to that of t...