R
Ronald Dodge
Given issues that I have dealing specifically with concurrent users using
unbound forms via ADO coding, is there a way to determine if the same user
is connected to the table/record within the same login, such as run periodic
checks to confirm this?
Example:
UserA is connected to the work order table and working on record number
1234567. UserA is using the FE part of the DB program to conect to the data
in the BE part of the DB program.
How does the BE part of the DB program know that the FE part is still
connected? If the connection should be broken off such as UserA experiences
a power failure or system crash on the PC side, but the server side is still
fully function, what indicates to the server side that UserA is no longer
connected.
Why for this:
So as I can control when editing can be done by what users at what times, I
have created a separate table specifically for this. Currently, the fields
that's in the table are the following:
Random ID Number (Unique and Primary Key)
Table ID
Record ID
User ID
EditMode
and I will also need to include a field for each specific login, which in
effect could replace the User ID field via a login ID.
If a user was to unexpected to lose it's connection, I would like to have
any recorded related to that specific connection or login to be removed from
this table as the user would need to log in again to reconnect to the BE DB.
unbound forms via ADO coding, is there a way to determine if the same user
is connected to the table/record within the same login, such as run periodic
checks to confirm this?
Example:
UserA is connected to the work order table and working on record number
1234567. UserA is using the FE part of the DB program to conect to the data
in the BE part of the DB program.
How does the BE part of the DB program know that the FE part is still
connected? If the connection should be broken off such as UserA experiences
a power failure or system crash on the PC side, but the server side is still
fully function, what indicates to the server side that UserA is no longer
connected.
Why for this:
So as I can control when editing can be done by what users at what times, I
have created a separate table specifically for this. Currently, the fields
that's in the table are the following:
Random ID Number (Unique and Primary Key)
Table ID
Record ID
User ID
EditMode
and I will also need to include a field for each specific login, which in
effect could replace the User ID field via a login ID.
If a user was to unexpected to lose it's connection, I would like to have
any recorded related to that specific connection or login to be removed from
this table as the user would need to log in again to reconnect to the BE DB.