Network Down

[Karl Roes]

Hi all,

I am after some suggestions on ways to gracefully respond to
situations where the network goes down while the database is in use.
It doesn't happen that often, but when it does, the UI freezes up for
a short period and then displays a Windows msg - " can't find
\\Server\Backend ......etc ".

Thank You

Karl

[Alan Webb]

Karl,
Quit creating applications using bound objects. Even a linked table
connected to a back end database is a bad idea. If you used unbound forms,
etc., then your code would reach out and touch the database only when
necessary. And if it didn't find it, could respond with an appropriate
error message.

"Karl Roes" <ka******@hotmail.com> wrote in message
news:7c**************************@posting.google.c om...

Hi all,

I am after some suggestions on ways to gracefully respond to
situations where the network goes down while the database is in use.
It doesn't happen that often, but when it does, the UI freezes up for
a short period and then displays a Windows msg - " can't find
\\Server\Backend ......etc ".

Thank You

Karl

[MacDermott]

Karl's suggestion could alleviate the problem -
although it, too, is vulnerable if the server goes down during those few
moments when data is being transferred.

Giving up bound objects, of course, means giving up what Access does best.
While Access can use unbound forms, I've never seen Access Reports done
without binding -
and Access's report writer is one of its most popular features.
Unbound forms are also a whole lot more cumbersome to develop than bound
ones -
a lot more work for you.

Inhouse networks should generally be pretty reliable -
if they're going down with any frequency at all, your IT department
should be addressing this issue. It's got to be affecting more than just
your application.

If you're trying to run Access over a WAN, Karl might be right in hinting
that a non-Access solution might be preferable.

HTH
- Turtle

"Alan Webb" <kn*****@hotmail.com> wrote in message
news:Me****************@news.uswest.net...

Karl,
Quit creating applications using bound objects. Even a linked table
connected to a back end database is a bad idea. If you used unbound forms, etc., then your code would reach out and touch the database only when
necessary. And if it didn't find it, could respond with an appropriate
error message.

"Karl Roes" <ka******@hotmail.com> wrote in message
news:7c**************************@posting.google.c om...

Hi all,

I am after some suggestions on ways to gracefully respond to
situations where the network goes down while the database is in use.
It doesn't happen that often, but when it does, the UI freezes up for
a short period and then displays a Windows msg - " can't find
\\Server\Backend ......etc ".

Thank You

Karl

[Tony Toews]

ka******@hotmail.com (Karl Roes) wrote:

I am after some suggestions on ways to gracefully respond to
situations where the network goes down while the database is in use.
It doesn't happen that often, but when it does, the UI freezes up for
a short period and then displays a Windows msg - " can't find
\\Server\Backend ......etc ".

Actually it should hardly ever happen. The only time I've seen this happen is when
my previous laptops network card had a loose connection or when some idiot sys admin
took down a switch.

I'd be much more concerned with figuring out what causes this problem in the first
place. If only one or two computers then loose connections, etc. If a number then
the upstream hub or computer.

I don't see how you can gracefully recover from this as there is no error handling
available from the bound form logic in behind Access to which we don't have access.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm

[Karl Roes]

Tony Toews <tt****@telusplanet.net> wrote in message news:<po********************************@4ax.com>. ..

ka******@hotmail.com (Karl Roes) wrote:

I am after some suggestions on ways to gracefully respond to
situations where the network goes down while the database is in use.
It doesn't happen that often, but when it does, the UI freezes up for
a short period and then displays a Windows msg - " can't find
\\Server\Backend ......etc ".

Actually it should hardly ever happen. The only time I've seen this happen is when
my previous laptops network card had a loose connection or when some idiot sys admin
took down a switch.

I'd be much more concerned with figuring out what causes this problem in the first
place. If only one or two computers then loose connections, etc. If a number then
the upstream hub or computer.

I don't see how you can gracefully recover from this as there is no error handling
available from the bound form logic in behind Access to which we don't have access.

Tony

Thank you all,

The information provided is invaluable.

I have thus created a new standalone server for the backend's and all
works well at this stage. (The datafiles were previously on a users
pc.)
I will now begin investigation into restricting folder access on this
new XP machine.

Regards

Karl

[MacDermott]

Be aware that your users will need create, modify, and delete rights on that
folder, in order to effectively implement shared access to the mdb.

HTH
- Turtle

"Karl Roes" <ka******@hotmail.com> wrote in message
news:7c*************************@posting.google.co m...

Tony Toews <tt****@telusplanet.net> wrote in message

news:<po********************************@4ax.com>. ..

ka******@hotmail.com (Karl Roes) wrote:

I am after some suggestions on ways to gracefully respond to
situations where the network goes down while the database is in use.
It doesn't happen that often, but when it does, the UI freezes up for
a short period and then displays a Windows msg - " can't find
\\Server\Backend ......etc ".

Actually it should hardly ever happen. The only time I've seen this happen is when my previous laptops network card had a loose connection or when some idiot sys admin took down a switch.

I'd be much more concerned with figuring out what causes this problem in the first place. If only one or two computers then loose connections, etc. If a number then the upstream hub or computer.

I don't see how you can gracefully recover from this as there is no error handling available from the bound form logic in behind Access to which we don't have access.
Tony

Thank you all,

The information provided is invaluable.

I have thus created a new standalone server for the backend's and all
works well at this stage. (The datafiles were previously on a users
pc.)
I will now begin investigation into restricting folder access on this
new XP machine.

Regards

Karl

[Karl Roes]

Thanks again,

Your suggestions helped me to delve deep into WinXP and set things up just nicely.

Regards

Karl
"MacDermott" <ma********@nospam.com> wrote in message news:<Jx*****************@newsread2.news.atl.earth link.net>...

Be aware that your users will need create, modify, and delete rights on that
folder, in order to effectively implement shared access to the mdb.

HTH
- Turtle

"Karl Roes" <ka******@hotmail.com> wrote in message
news:7c*************************@posting.google.co m...

Tony Toews <tt****@telusplanet.net> wrote in message

news:<po********************************@4ax.com>. ..

ka******@hotmail.com (Karl Roes) wrote:

>I am after some suggestions on ways to gracefully respond to
>situations where the network goes down while the database is in use.
>It doesn't happen that often, but when it does, the UI freezes up for
>a short period and then displays a Windows msg - " can't find
>\\Server\Backend ......etc ".

Actually it should hardly ever happen. The only time I've seen this happen is when my previous laptops network card had a loose connection or when some idiot sys admin took down a switch.

I'd be much more concerned with figuring out what causes this problem in the first place. If only one or two computers then loose connections, etc. If a number then the upstream hub or computer.

I don't see how you can gracefully recover from this as there is no error handling available from the bound form logic in behind Access to which we don't have access.
Tony

Thank you all,

The information provided is invaluable.

I have thus created a new standalone server for the backend's and all
works well at this stage. (The datafiles were previously on a users
pc.)
I will now begin investigation into restricting folder access on this
new XP machine.

Regards

Karl