setting up an alert

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Hi,

Has anyone set up an alert at one particular workstation (preferably one
apart from the system beep) when a user request is raised at one front end?

Also, how best to implement this concept?
 
What does, "when a user request is raised at one front end" mean?

Please explain exactly what you are asking for.
 
Hi,

Has anyone set up an alert at one particular workstation (preferably one
apart from the system beep) when a user request is raised at one front end?

Also, how best to implement this concept?
Click to expand...

Are you setting an alert in a Microsoft Access database (the subject
of this newsgroup)? or in Windows? If the latter, please post your
question in a WindowsXP newsgroup; if in Access, please post a more
detailed description of the context - the nature of the database, what
triggers the alert, etc.

John W. Vinson[MVP]
 
I'm sorry that I wasn't clearer. It is a request to the Access database that
contains data(codes, links to images, etc.).

At one end of the database (in a warehouse) there are people assembling
items. When they run into an issue where they encounter either a defective
component, they post a request, highlighting the requirements to an Access
database and it is stored as a pending request. The other 'end' that i
mentioned was also in a warehouse that stores these replacements needs to be
'alerted' of this request and of any others in the queue. Once the person
responsible sanctions the request and releases replacements for the
assemblers, this request should be logged in the database with all relevant
information.

I would like to know how best to implement this system of a periodically
refreshing incoming request queue in the FIFO order.

Thanks for any suggestions.
 
I'm sorry that I wasn't clearer. It is a request to the Access database that
contains data(codes, links to images, etc.).

At one end of the database (in a warehouse) there are people assembling
items. When they run into an issue where they encounter either a defective
component, they post a request, highlighting the requirements to an Access
database and it is stored as a pending request. The other 'end' that i
mentioned was also in a warehouse that stores these replacements needs to be
'alerted' of this request and of any others in the queue. Once the person
responsible sanctions the request and releases replacements for the
assemblers, this request should be logged in the database with all relevant
information.

I would like to know how best to implement this system of a periodically
refreshing incoming request queue in the FIFO order.

Thanks for any suggestions.
Click to expand...

The recipient of the message could have an always-open continuous Form
showing the open requests; they would need to have Access open and
this form visible, if that's all that you do.

To get a message box or a beep, you'll need to use a Timer event on
some open form to periodically check the contents of the requests
table. This could get a bit complicated - you'll need to perhaps
record the most recent request date/time in a variable and use DLookUp
to see if there are any more recent records.

John W. Vinson[MVP]
 
This is not that hard, but will take a little work.
Create a table that will hold the information you want to pass from the
assemblers to the suppliers.
In the Assembler's form add the code to update this table with the requested
Information.

Then on the Supplier's form, Set a TimerInterval in the Load Event. You can
find detail info on this in VB Editor Help. Then in the Timer event, check
to see if there is anything in the table. If there is not, do nothing. If
there is a request, use a message box to alert the supplier. Once the
supplier has responded to the message box, do whatever needs to be done and
delete the request from the table.
 
Back
Top