This is the classic airline reservation system issue. The problem is how to stop a travel agent in LA from booking the same seat as a travel agent in New York? The airline system works by holding the seat for a specified period of time. If the tickets are not purchased, then the hold is released. You may want to look at doing something similar.


>We have a foxpro comobject wrapped in COM+ that we want to use to do updates to an appointment book. The COM+ object resides on our data server and our users all have proxies of the COM+ object installed so that they can call it remotely. We do a check before updating a record to make sure that the appointment hasn't already been taken by using a simple check to ensure a field is still empty(field is filled with a customer ID when appointment is taken). It is obviously stateless and the table is closed after each call of the comobject's update procedure. Our worry is this, it looks like multiple instances of the comobject in COM+ are being created with every client that accesses it at the same time. Does this mean that two instances of the comobject can update the same record at the same time causing undesirable behavior or does COM+ handle this some how?
>
>Anybody know?