workgroup information is missing

[Toxalot]

Client is receiving the following error when trying to use the
application after it has been left idle for 5-10 minutes.

"Cannot start your application.
The workgroup information is missing or opened exclusively by another
user."

I am unable to reproduce the error. Both client and I are using WinXP
SP 3 on standalone computers. I have full version of Access 2003.
Client is using Access 2003 runtime. FE is mde and BE is mdb. There is
no user-level security and no database password. I've tried
reproducing the error with the FE mdb, and the the FE mde, and the FE
mde via the following shortcut to simulate runtime.
"D:\Program Files\Microsoft Office\OFFICE11\MSACCESS.EXE" /runtime "F:
\mydata.mde"

In all cases, I've tried several functions and then left the
application idle for various intervals and never receive the error.
Client is able to use the database without error as long as they don't
leave it idle for more than a few minutes.

Here is the connection string being used:
strConnection = "Provider=Microsoft.Jet.OLEDB.4.0;" & _
"Data Source=" & gstrDataFilePath & ";"

I've been searching on the error message and reading for hours. All
issues seem to discuss setups using user-level security and the error
message occurs every time. I found one post where the OP had one
client getting the error randomly, but there were no replies.

There is really no reason why this application should be using ADO and
I am moving towards using DAO, but in the mean time this is extremely
frustrating.

Any ideas on what to try?

 

[John Spencer]

BIG HUGE SPECULATION FOLLOWS:

It could be a network issue. Where is the workgroup information stored that
you are using? If it is on a server and the connection to the server gets
"shut down" if the computer is not using the connection for a specified time
frame, then it might be that the mdw is not immediately accessible when the
user attempts to use the database.

John Spencer
Access MVP 2002-2005, 2007-2010
The Hilltop Institute
University of Maryland Baltimore County

 

[Toxalot]

It's a standalone PC. No network.

Jennifer

BIG HUGE SPECULATION FOLLOWS:

It could be a network issue.  Where is the workgroup information storedthat
you are using?  If it is on a server and the connection to the server gets
"shut down" if the computer is not using the connection for a specified time
frame, then it might be that the mdw is not immediately accessible when the
user attempts to use the database.

John Spencer
Access MVP 2002-2005, 2007-2010
The Hilltop Institute
University of Maryland Baltimore County

 

[James A. Fortune]

Client is receiving the following error when trying to use the
application after it has been left idle for 5-10 minutes.

"Cannot start your application.
The workgroup information is missing or opened exclusively by another
user."

I am unable to reproduce the error. Both client and I are using WinXP
SP 3 on standalone computers. I have full version of Access 2003.
Client is using Access 2003 runtime. FE is mde and BE is mdb. There is
no user-level security and no database password. I've tried
reproducing the error with the FE mdb, and the the FE mde, and the FE
mde via the following shortcut to simulate runtime.
"D:\Program Files\Microsoft Office\OFFICE11\MSACCESS.EXE" /runtime "F:
\mydata.mde"

In all cases, I've tried several functions and then left the
application idle for various intervals and never receive the error.
Client is able to use the database without error as long as they don't
leave it idle for more than a few minutes.

Here is the connection string being used:
strConnection = "Provider=Microsoft.Jet.OLEDB.4.0;" & _
"Data Source=" & gstrDataFilePath & ";"

I've been searching on the error message and reading for hours. All
issues seem to discuss setups using user-level security and the error
message occurs every time. I found one post where the OP had one
client getting the error randomly, but there were no replies.

There is really no reason why this application should be using ADO and
I am moving towards using DAO, but in the mean time this is extremely
frustrating.

Any ideas on what to try?

Toxalot,

Try looking at the timeout keys in:

HKEY_LOCAL_MACHINE\Software\Microsoft\Jet\4.0\Transporter

The Jet Engine Programmer's Guide mentions that a connection timeout
setting of 0 causes the connection to remain open. It also suggests
looking at the SetOption method for changing timeouts.

James A. Fortune
(e-mail address removed)

 

[a a r o n . k e m p f]

Yah, I'd stop blaming your problems on ADO.. and I'd stop rewriting
ADO --> DAO.

ADO is better... because it's more portable, it's faster, and it
allows you to move to SQL Server without rewriting your code