Suggested Workgroup Setup

[A P]

Hi!

I have 3 Workstation (2 Windows XP Prof, 1 Windows 2000 Prof) and 1 Server
(with Windows XP Prof). I know that Windows XP Prof have limitation in
connection that is why I limited computers that can connect. These
workstations are accessing a ms access file on the server 24hours. Can I
remove connection timeout of these machines since we are experiencing
disconnection for a particular time.

Me

 

[Dave]

Hi!

I have 3 Workstation (2 Windows XP Prof, 1 Windows 2000 Prof) and 1 Server
(with Windows XP Prof). I know that Windows XP Prof have limitation in
connection that is why I limited computers that can connect. These
workstations are accessing a ms access file on the server 24hours. Can I
remove connection timeout of these machines since we are experiencing
disconnection for a particular time.

Me

there is a number of connections limitation in pro, but have never heard of
or seen a timeout. what kind of connection are you talking about and what
is the timeout you are seeing?

 

[NobodyMan]

Hi!

I have 3 Workstation (2 Windows XP Prof, 1 Windows 2000 Prof) and 1 Server
(with Windows XP Prof). I know that Windows XP Prof have limitation in
connection that is why I limited computers that can connect. These
workstations are accessing a ms access file on the server 24hours. Can I
remove connection timeout of these machines since we are experiencing
disconnection for a particular time.

Me

In truth, a "connection" is not just one machine connecting to
another. Depending on the request, an accessing box may open more
than one connection to the receiving machine.

If you really want to run a client/server type schema, it's best to go
out and buy you a Server OS. It will likely get rid of the error you
are experiencing with time-outs.

 

[Phillip Windell]

Timeouts only relate to "mapped drives". You should not be using mapped
drives anyway. You should be using the UNC Path
(\\machinename\sharename\foldername).

Access MDB files do not behave well in a multi user situation. The file
often becomes locked ("in use") and so the first person to open it is fine,
but other cannot open it until the first person disconnects. MDBs are more
usuable with a web interface than the regular Access Interface because a Web
Interface connects only breifly "as needed" and does not hold a constant
connection the way the Access Application would do.

 

[A P]

Hi Philip!

Thanks for your reply. The scenario is this, I have a program that was
installed on the workstation PC that uses a central log (as ms access db)
located on the server machine. I want all program logs be saved on a single
database file which is on the server. I notice that on a particular time,
some workstations cannot save logs on the server db. How can we avoid this?
is there another way to handle this?

Me

Timeouts only relate to "mapped drives". You should not be using mapped
drives anyway. You should be using the UNC Path
(\\machinename\sharename\foldername).

Access MDB files do not behave well in a multi user situation. The file
often becomes locked ("in use") and so the first person to open it is fine,
but other cannot open it until the first person disconnects. MDBs are more
usuable with a web interface than the regular Access Interface because a Web
Interface connects only breifly "as needed" and does not hold a constant
connection the way the Access Application would do.

--

Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com

Hi!

I have 3 Workstation (2 Windows XP Prof, 1 Windows 2000 Prof) and 1 Server
(with Windows XP Prof). I know that Windows XP Prof have limitation in
connection that is why I limited computers that can connect. These
workstations are accessing a ms access file on the server 24hours. Can I
remove connection timeout of these machines since we are experiencing
disconnection for a particular time.

Me

 

[Phillip Windell]

Thanks for your reply. The scenario is this, I have a program that was
installed on the workstation PC that uses a central log (as ms access db)
located on the server machine. I want all program logs be saved on a single
database file which is on the server. I notice that on a particular time,
some workstations cannot save logs on the server db. How can we avoid this?
is there another way to handle this?

Well, I already explained why this is happening.

If this is a purchased Application then you need to contact who is
responsible for it and have them troublshoot it.

If this Application is written "in house" then it needs to be designed so
that when it access the database it:
1. Connects
2. Makes the changes (saves, deletes, edits)
3. Releases (disconnects)
4. It can only work "one user (connection) at a time".

It should not be written to maintain a constant connection. If you used an
SQL type of database (MS SQL Server, MSDE, MySQL, etc) then a constant
connection is fine,...but you can not do that with an Access MDB file.

I am not a programmer "officially". I cannot help you write software in any
kind of detail.