I have a variety of databases that are hosted on a web based-dedicated server. These databases are accessed via button driven scripts. The buttons all live on a database called Bulletin Board. The BulletinBoard database has no fields. It only consists of a layout with the script buttons.

So far, everything is working fairly well except for one aspect.

Intermittently the server closes down and I get an error message that says:

"Communication with the host was interrupted and cannot be re-established. All affected windows will be closed."

I have a couple of questions about this:

[color:red]What causes this interruption to happen?

The second part of my question is how to elegantly re-establish communication. Each one of my databases are password protected and they share the same password. When the system goes down and needs to be rebooted it gets kind of annoying to have to re-enter all these passwords again.

I[color:red]s there a way to put these databases into a common folder and just have password protection at the folder level? The information that is in these databases is not particularly sensitive so security is not as important to me as convenience.

Can anybody shed some light on this?

Thanks,

Jarvis

One reason for communication errors are the energy saver settings spinning down the disk and putting the system to sleep.

Another reason is the disconnection setting in accounts and priviledges in each file

Another reason is the disconnection setting in server preferences

In file options you can specify a password to open files automatically, but a more secure method is to have an opener file that you enter a password in that runs a script to open the other files.

The username and password of the opener file is passed to the other files automatically in the Open File script step.

Thanks Stuart,

I think I can get there from here.

Jarvis

Check your hardware and network typology carefully, from the NIC card out to the end. You may have some issue that's causing the server to misbehave. Also, if this is not a dedicated server, then you increase the likelihood of this type behavior's happening.

Steven