K
Kam
How would you go about developing multi-users applications?
The situation is as the following:
We have an existing application that allow the users to lock records (i.e.
prevent anyone else using the same application from selecting the same
record in order to modify it - Note: the user is able to select multiple
records at the same time). When the user finishes with the record (i.e.
unlock the record), the application saves the modified information as an
object and pass them into the database.
We are trying to create a new application that implements different
functionalities + modifying some of the information in the records mentioned
above (Note: it will have a complete different algorithm).
When the database was created, they haven't considered date/time stamps so
we are unable to check against it. Even if we change the database structure
and include a data/time stamp. That means changes have to be made to the
existing application which we don't want to do.
When the existing application was created, they didn't consider concurrency
either in the system analysis and design stages. So this also can't be used
or implemented as that means changing the current application too.
The last thing to do is to use the same functionality of the existing
application (Locking and unlocking records) although we don't want to change
the whole record only a portion of it. However, that would cause a problem
when everyone is using both applications as the new application will require
modifying multiple records at the same time (i.e. most of the records will
be locked by the new application which obviously will prevent the users of
the existing application from selecting any record!)
Any help, idea, site link, newsgroup would very much appreciated.
Thank you all in advance and hope to hear from you soon.
Regards,
Kam
The situation is as the following:
We have an existing application that allow the users to lock records (i.e.
prevent anyone else using the same application from selecting the same
record in order to modify it - Note: the user is able to select multiple
records at the same time). When the user finishes with the record (i.e.
unlock the record), the application saves the modified information as an
object and pass them into the database.
We are trying to create a new application that implements different
functionalities + modifying some of the information in the records mentioned
above (Note: it will have a complete different algorithm).
When the database was created, they haven't considered date/time stamps so
we are unable to check against it. Even if we change the database structure
and include a data/time stamp. That means changes have to be made to the
existing application which we don't want to do.
When the existing application was created, they didn't consider concurrency
either in the system analysis and design stages. So this also can't be used
or implemented as that means changing the current application too.
The last thing to do is to use the same functionality of the existing
application (Locking and unlocking records) although we don't want to change
the whole record only a portion of it. However, that would cause a problem
when everyone is using both applications as the new application will require
modifying multiple records at the same time (i.e. most of the records will
be locked by the new application which obviously will prevent the users of
the existing application from selecting any record!)
Any help, idea, site link, newsgroup would very much appreciated.
Thank you all in advance and hope to hear from you soon.
Regards,
Kam