On Feb 21, 9:28 am, "cefran...@yahoo.com" <cefran...@yahoo.comwrote:
Quote:
I have a Back End database (split) that is on a smokin' hot machine
(dual processor, 2 gig RAM, XP Pro SP2) and I'm getting an error that
says the database (back end file) is "opened exclusively" by someone
else.
>
I looked at the number of sessions and noticed that when the number of
sessions were at 10, any new user launching the front end would get
the "exclusive" error message.
>
There is no security in place and no login required.
>
I thought there would be a higher limit than this.
>
Is there some kind of limit to the number of sessions or files opened
for the XP machine (with the back end database)? If so, can that
number be raised to allow more users to connect?
>
Also, if the limit is a Microsoft license issue, where they would want
you to buy a Server OS, how does this speak to all the development
over the years promoting "front end/back end" senario? Is it
understood, all this time, that these applications (as described in
Developer books, magazines and articles, etc.) would "conveniently" be
in an environment where there are 10 or less simultaneous users?
I'm only asking because, NONE of the training or advice ever said,
"oh, by the way, this multi-user situation can only have a max of 10
concurrent users, unless you are deploying on a MS-Server
environment..."
>
I'm not looking for a hundred, but 10! Geeze, that seems to be a bit
constraining, no?
>
Thanks in Advance
Yo Al,
Are you saying this guy is a "FOOL", "INCOMPETENT"???
I think you over estimate yourself and have been living in these news
groups too long, perhaps? There is a world
outside, go have a look and get a girlfirend. You must be a momma's
boy and the bullies you had in school figured it out as well. This is
obvious.
Mr. Poopie Pants, you need a lesson in patience, and realize that
EVERYBODY DOESN"T KNOW AS MUCH AS YOU, only most people.
Well, at least most people do when it comes to being courteous.
These newsgroups are here for people to ask questions, BECAUSE THEY
DON"T KNOW!
Not to be clobbered by some insecure Most Vile Predator, like you. You
obviously never worked as a team player and are probably over paid by
a company under hostage by your little "tech secrets".
NOTE TO SELF: Never hire this guy for ANY kind of tech support.
Your social incompetence is probably why you still live at home with
your parents.
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
On to a more worthwhile response.....
cefrancke, I apologize for that inappropriate response. Some users
just don't get it.
According to Microsoft, in order to prevent worm and virus blasts, as
of Windows XP SP2, a change was made to the
tcpip connections in their network software as well as other file/
computer sharing software built in to Windows XP.
This setting for Windows XP SP2 is fixed at 10. It can not be changed
with the registry or any Windows administrative program.
The following lists the various limits...
XP Home 5 Users
XP Pro SP2 10 Users
Versions before XP SP2, like XP SP1, Windows 2000, and other non-
Server based operating systems, DID ALLOW more than 10 simultaneous
connections. (Mr. Poopie Pants!)
To get a bit more technical the limit may depend on inbound or
outbound connections, frequency of the connections and the ports these
connections are used. (There was a case where new connections were
denied once 10 was reached, however a Net Meeting session on an 11th
connection was allowed, and not even listed in the Computer Management
"session" view)
Poopie Pants, above, must not work with very many users or he has not
been working with computers for very long.
There are plenty of cases where much more than 10 users/connections
have been made on previous Microsoft Operating Systems without using a
Server version, and are still in use. This is NOT illegal and could be
increased or decreased with registry settings. (No one is going to get
fired.)
Microsoft has many knowledge base articles on how to make changes.
But, as said before, this is not the case for XP SP2.
In those articles, they discuss the limitation and why, a what various
OS's (Operating Systems) have what limits.
In my opinion, the proper solution is to upgrade to a Server based
system, Small Business Server or Enterprise. Or perhaps revert to a
previous version where you can adjust the connection limit.
Some suggest a Linux variant may help, but I'm not sure how it would
work for MS-Access.
Articles: (there are many more than these below)
Talks about the limit with respect to the Event Viewer message # 4426.
http://www.microsoft.com/technet/sup...cpip&LCID=1033
Inbound connections for XP
http://support.microsoft.com/kb/314882
Mentions the connection limit.
http://support.microsoft.com/kb/307874
Where in the news groups does it say you have to be courteous,
oh...wait, it DOES say that!
Disk space, file size, memory are always an issue. I dont understand
what Poopie Pants is getting at, but knowing the specifications and
limitations IS fundamental and any professional would endeavor to come
to know these things. And, like you, will come to know inevitably.
Here are some Access limits, etc.
http://office.microsoft.com/en-us/ac...868081033.aspx
I see no "complaining" on your part, just normal frustration that may
occur on your journey.
Did he answer your questions with references to back it up?...hmmm...
I dont think so,
But I'm sure he wet his pants ranting at you ;-)
It sounds like he has already, with prejudice, concluded that you are
trying to run a file sharing program.
I think you said MS-Access, with enough detail to be legit.
Reading IS fundamental, Mr. Poopie Pants, MVP
Hang in there cefrancke.
JDP, Ph,D., Esq., abc, xyz, bbc....whatever
