For some users they alwasy have problem for not able to connect to the
backend in the server.
The problem is as follows. In the server we have allowed users to connect to
the Server and the security is without pasword for the user to connect
therefore the options User must changed password at next log on is "
Unticked". But we do not know what makes it later " Ticked" then some users
can not access anymore the server from their Front Ends.
What I do is to delete the user and recreate again user for them and make
the option "unticked", then it works again.
But in one week or 2 weeks ( no regular interval) the same problem happens
again.
My question is what makes it happened and how can we solve this problem.
Thanks very much for any helps.
--
H. Frank Situmorang
Vanderghast, Access MVP
"Frank Situmorang" <hfsitu...@yahoo.com> wrote in message
news:F244484B-A7D3-4B4F...@microsoft.com...
Vanderghast, Access MVP
--
H. Frank Situmorang
Other source of problem could be a wrong connection: if you use cable, be
sure there is no electrical motor close to you cable, anywhere on its
length. Note that a connection problem is likely to occur always with the
same sub-set of machines, while, on the other hand, a user limit would
problem, in theory, would occur on any machine, more or less randomly
(unless the 11th user is always the same guy who always arrive late at the
job, so is always the one coming after the '10' other user made their
connection without problem). A connection problem, with cable, can also
occur if the screws holding the various threads of the cable, in the wall,
got loose, or if there is more than 5 hubs total on the local network, or if
you use more than 3 hubs with connections to machines (other than other
hubs), or a cable length in excess of its recommended length, etc. Sure,
'software' guys have a tendency to blame the 'hardware', so maybe the
hardware is not the source of the problem at all.
It is hard for me to say go for a Server OS (if you have none at the moment,
to test it), since the problem can be elsewhere and, if so, that would be an
expense (not only buying the OS, but also installing it, testing it, etc..)
that will not solve the problem, and that would not make you happy, in the
end.
Vanderghast, Access MVP
"Frank Situmorang" <hfsitu...@yahoo.com> wrote in message
news:C11111D9-89FD-4AB7...@microsoft.com...
Vanderghast, Access MVP
"dch3" <dc...@discussions.microsoft.com> wrote in message
news:D5EA3BEC-765E-41EE...@microsoft.com...
>Thanks Michel for your response, may be we need to give more information. The
>OS in our server is Windows 2000 professional. Does it have also limit for
>the user? and coulcd it be the problem, because as I said as soon as I
>recreated again for the same user and untick the option, it works again.
I just checked ... yes, W2K also has the 10 user limit.
RD
Thanks if anyone can still have any idea
--
H. Frank Situmorang
>I am not sure RD, if 10 users limit is the problem, because I noticed they
>are more than 10 users accessed that server at one time, but there is no
>problem occurrs. I am just confused what to do now. Yes..the company will
>alwasy need me in order to keep the system working, but I am not happy with
>my work because I am the one who created the " Supplier Invoice Tracking
>database". If I am not here anylonger I do not want to loose my reputation
>because of this problem.
>
>Thanks if anyone can still have any idea
Frankly, I think this is an issue with your server, not your
application. I went back and read your other posts and, after much
ruminating and cogitating, I figure there must be some other factor at
work. Perhaps another process (or person) is messing with the user's
permissions?
If neither of those are the issue then I'm at a loss.
Good luck,
RD