Preventing Access from crashing, when it looses connection to the database

Hi all,
>
I have a split database. Both the forms, and the tables are stored on
a shared network drive (this is Access 2003).
>
The users use the forms, and the tables on the network drive, there
are no local copies.
>
When connection to this drive is lost, Access CRASHES. It does it
every single time. Does anyone know if there is a way to check if
connection to the file has been lost, or do something to make this
experience less painful for the user?
>
Thanks,
Mark
>

>Hi all,
>
>I have a split database. Both the forms, and the tables are stored on
>a shared network drive (this is Access 2003).
>
>The users use the forms, and the tables on the network drive, there
>are no local copies.
>
>When connection to this drive is lost, Access CRASHES. It does it
>every single time. Does anyone know if there is a way to check if
>connection to the file has been lost, or do something to make this
>experience less painful for the user?
>
>Thanks,
>Mark

Hi all,
>
I have a split database. Both the forms, and the tables are stored on
a shared network drive (this is Access 2003).
>
The users use the forms, and the tables on the network drive, there
are no local copies.
>
When connection to this drive is lost, Access CRASHES. It does it
every single time. Does anyone know if there is a way to check if
connection to the file has been lost, or do something to make this
experience less painful for the user?
>
Thanks,
Mark
>

What do you mean by Access crashes? How do you know that the connection is
lost? What message, if any, does a user see when Access crashes? Does
Access close on the users computer or does it freeze?
Lost connections to a netwrok drive is an IT issue and that group should look
into this if it happens often
Your description of the database does not indicate that it is split if all
users use the network db. A truly split databse has the tables in the
backend on a network drive and tables (linked to the backend), queries, forms,
tables, macros, and modules in the frontend on the users computer. As a
general "rule", only tables should be in the backend.
That they are all using the same db could be your problem.
>
>
>
mark_aok wrote:>>>>>
--
Message posted viahttp://www.accessmonster.com

What do you mean by Access crashes? How do you know that the connection is
lost? What message, if any, does a user see when Access crashes? Does
Access close on the users computer or does it freeze?
Lost connections to a netwrok drive is an IT issue and that group should look
into this if it happens often
Your description of the database does not indicate that it is split if all
users use the network db. A truly split databse has the tables in the
backend on a network drive and tables (linked to the backend), queries, forms,
tables, macros, and modules in the frontend on the users computer. As a
general "rule", only tables should be in the backend.
That they are all using the same db could be your problem.
>
>
>
mark_aok wrote:>>>>>
--
Message posted viahttp://www.accessmonster.com

One more thing. Why would it make sense to keep a copy of the forms
on people's PC's?? Wouldn't that just complicate things? I have 5
users using this database, and 99.9% of the time, it is just one user
at a time...
>
Mark

"mark_aok" <mark_...@hotmail.comwrote in message
>
news:1182190657.644943.307260@n60g2000hse.googlegr oups.com...
>>>
Read my article as to why you don' want to do this:
>
http://www.members.shaw.ca/AlbertKal...plit/index.htm
>
Furthest, ask your IT people why for the least 20+ years, they always
installed every other piece of software on each computer..but all sudden
break with tradition here?
>
Further, READ VERY carefully the part above as to why you can't have a loss
of connection, else you likely to blow out your data file and have to go to
the previous days backup.
>
Further, keep in mind that breaking a connection to software that being run
"over" the network is going to be VERY MUCH more unstable, as parts of code,
or a form that requests other code and forms will most certainly crash when
the requested bits and pieces fail due to a loss of network.
>
How can you even have error code run when the connection breaks, and you
can't load that error code!! (do think about this for a second!!! If you
trap the error or loss of connection, then how will that error code load).
>
So, if you place your software on EACH workstation, you will find ms-access
to be much more stable. And, if you do put in some error trapping code, at
least the code can load and run because it on the workstation!! How can some
access code load and run error code when it is not your pc, and the
connection is broken? I not sure I really need to point this obvious
problem? In effect, this is not really a access issue or question, but
simply that of how can you load and run something when you don't have a
connection to what your trying to load and run!!!
>
So, think about how your IT been installing all software on each computer
for many many years now. Then all of a sudden, your code and applications
are NOT to installed on the workstation?
>
Anyway...read the above article, and perhaps give a copy to the IT people. I
sure once your IT people grasp the difference between data and an
application that runs code, then they will instantly see my point.
>
If your IT people can't tell the difference between data and code, then I
think we in trouble from the get go....
>
ms-access does not load everything into memory when it runs......
>
--
Albert D. Kallal (Access MVP)
Edmonton, Alberta Canada
pleaseNOOSpamKal...@msn.com

computers. But I had one final question. Your article mentioned
keeping connections to tables open at all times...this seemed
confusing.

>Are you suggesting that people remove all .close statements from there