M
michael rogovin
Apologies to those who have seen this post before; the
problem is still unresolved.
I created several database applications in Access 2002.
They started as Access97 simple databases and were
converted to Access2002 format and then modified
extensively into full applications. The errors did not
occur before. The network setup is Access running on user
workstations (win xp) and the datafile for each
application on the fileserver (Windows 2000 network) with
edited record locking. The problems occur whether or not
the datafile is opened by one or more users.
When running the database, Access will suddenly lose the
datafile; that is, Access continues to run, but the
datafile is suddenly empty. There are no tables, queries,
etc--it is as if I just opened a new blank database. Any
form on screen no longer works, since there are no
macros, queries etc. associated with it. Typically this
is accompanied by multiple "Disk or Network Error"
message boxes which appear every few seconds until they
fill the screen and have to be closed one by one.
Sometimes there is no error. Once, I got a windows error
in the system task bar about a delayed write and lost
data which caused the same effect in Access. Sometimes
compacting and repairing reduces instances of the
problem, but they reoccur shrtly thereafter. I am not
aware of any other problems on the net (all my word,
excel and outlook files are on the server and I have
never seen this problem with those apps).
I have looked on the KB but found only articles related
to Access 2.0 or IIS, neither of which apply to my
situation. I also tried replacing the network cable per
suggestions from this forum, to no avail. Several users
of the applications on the network have experienced the
problem, so it is not localized to my workstation.
Does Access create a tmp file like Word does when it
opens a data file? If so where (I could not find it). If
so, is it possible that something is happening to the TMP
file during a session that would cause this error? Any
other ideas? We are at a loss and are concerned about
possible data loss on mission critical applications.
Thanks.
problem is still unresolved.
I created several database applications in Access 2002.
They started as Access97 simple databases and were
converted to Access2002 format and then modified
extensively into full applications. The errors did not
occur before. The network setup is Access running on user
workstations (win xp) and the datafile for each
application on the fileserver (Windows 2000 network) with
edited record locking. The problems occur whether or not
the datafile is opened by one or more users.
When running the database, Access will suddenly lose the
datafile; that is, Access continues to run, but the
datafile is suddenly empty. There are no tables, queries,
etc--it is as if I just opened a new blank database. Any
form on screen no longer works, since there are no
macros, queries etc. associated with it. Typically this
is accompanied by multiple "Disk or Network Error"
message boxes which appear every few seconds until they
fill the screen and have to be closed one by one.
Sometimes there is no error. Once, I got a windows error
in the system task bar about a delayed write and lost
data which caused the same effect in Access. Sometimes
compacting and repairing reduces instances of the
problem, but they reoccur shrtly thereafter. I am not
aware of any other problems on the net (all my word,
excel and outlook files are on the server and I have
never seen this problem with those apps).
I have looked on the KB but found only articles related
to Access 2.0 or IIS, neither of which apply to my
situation. I also tried replacing the network cable per
suggestions from this forum, to no avail. Several users
of the applications on the network have experienced the
problem, so it is not localized to my workstation.
Does Access create a tmp file like Word does when it
opens a data file? If so where (I could not find it). If
so, is it possible that something is happening to the TMP
file during a session that would cause this error? Any
other ideas? We are at a loss and are concerned about
possible data loss on mission critical applications.
Thanks.