DotNet access not locked

[Ray Theberge]

I logged into my Troopmaster database via DotNet this morning from home and accidently forgot and left the database open when I left home for work.

When I got to the office, I remembered some additional advancement that I wanted to log into Troopmaster so I logged in via DotNet and made the changes.

The DotNet interface at work never told me that I was already logged in at home and it allowed me to make the changes.

When I got home tonight, I saw that TM was running on my laptop and closed it. As it was uploading the database (via DotNet) and loggin out and releasing the "lock" on the database, I suddenly realized that I had just overwritten all the work that I had posted in the office.

How does this happen?

How does DotNet not lock out other users? (even if it is myself) ;-)

Thanks,

Ray

[Todd D. Taft]

It seems that DotNet locking depends, in part, on the value you put for
your name.  To deal with this, I've used different names on each computer,
e.g. "Todd Taft - home", "Todd Taft - mobile".  I don't think that having
different phone numbers or email addresses is sufficient if the name is
identical.  When I tried to report this behaviour to TSI as a bug, the
response I got back was "working as designed".

--Todd

On Tue, 13 Oct 2009, flaxin1 wrote:

> I logged into my Troopmaster database via DotNet this morning from home and accidently forgot and left the database open when I left home for work.
>
> When I got to the office, I remembered some additional advancement that I wanted to log into Troopmaster so I logged in via DotNet and made the changes.
>
> The DotNet interface at work never told me that I was already logged in at home and it allowed me to make the changes.
>
> When I got home tonight, I saw that TM was running on my laptop and closed it. As it was uploading the database (via DotNet) and loggin out and releasing the "lock" on the database, I suddenly realized that I had just overwritten all the work that I had posted in the office.
>
> How does this happen?
>
> How does DotNet not lock out other users? (even if it is myself) ;-)
>
> Thanks,
>
> Ray

--
Todd D. Taft
taft@...

[Tim W-2]

From the manual (3.16 TroopMaster DotNet):

Please make sure that the contact information entered is unique for each computer that will
be connecting to DotNet. If you enter the same contact information on multiple computers
and to login to DotNet on both machines at the same time, the system will not report the
database currently being locked since it appears to be the same user logging on.


--- In TMTUG@..., "Todd D. Taft" <taft@...> wrote:

>
> It seems that DotNet locking depends, in part, on the value you put for
> your name.  To deal with this, I've used different names on each computer,
> e.g. "Todd Taft - home", "Todd Taft - mobile".  I don't think that having
> different phone numbers or email addresses is sufficient if the name is
> identical.  When I tried to report this behaviour to TSI as a bug, the
> response I got back was "working as designed".
>
> --Todd
>
> On Tue, 13 Oct 2009, flaxin1 wrote:
>
> > I logged into my Troopmaster database via DotNet this morning from home and accidently forgot and left the database open when I left home for work.
> >
> > When I got to the office, I remembered some additional advancement that I wanted to log into Troopmaster so I logged in via DotNet and made the changes.
> >
> > The DotNet interface at work never told me that I was already logged in at home and it allowed me to make the changes.
> >
> > When I got home tonight, I saw that TM was running on my laptop and closed it. As it was uploading the database (via DotNet) and loggin out and releasing the "lock" on the database, I suddenly realized that I had just overwritten all the work that I had posted in the office.
> >
> > How does this happen?
> >
> > How does DotNet not lock out other users? (even if it is myself) ;-)
> >
> > Thanks,
> >
> > Ray
>
>
> --
> Todd D. Taft
> taft@...
>