Mulitple Session With Updates

[Robert_DubYa]

I have a DB that will have multiple views open. I'm using the DB as an
auxilary component to our ERP system to push work orders through our factory.
I am connecting to our ERP via ODBC. Our ERP system will control the status
of the work order (what stage the work order is at). I'm updating our work
order status via the use of a timer. This works, but my fear is that once I
get past my testing stage and we start to deploy the DB factory wide I will
problems with:

1. Quiries "overlapping" because the update is being done by each terminal
that has a session open (ie failures do to two quiries running at the same
time).

2. The amount of network traffic that is being created that is not necessary.

I'm struggling with how to have just one computer doing the updates without
keeping a session up and going all the time.

I have thought about using an id (users have to sign into PC's) to assign
the job of the updates to the first PC into the DB. The problem I see with
this is if that PC is shut down or forced to exit Access I have no way to
update the query until the user signs back in.

Any thoughts or suggestions would be GREATLY apperciated.

thanks,
Robert