Hi Len

I'd like to point out a couple of things here that might help you, though I cannot give a definitive solution.

First, you may or may not be aware that using Filemaker the way you are (in a 'peer-to-peer' network) is not a very solid practice. It does work, and Filemaker promotes it, but for a mission-critical situation it has some problems. You are facing one of them. That is, if for any reason (which may be external to Filemaker itself) a remote peer loses its connection to the server peer, there is a danger of damaging your database file(s). In the end, this spontaneous closing of the file will likely lead to corruption. You need to be aware of this if you continue to practice this form of Filemaker networking.

A second problem with peer-to-peer sharing is taking backups. You should never take backups of the files while they are open. That means the only opportunity you have for backups is during 'down' time. It is much more convenient to take backups at regular intervals, such as every 30 minutes during the working day. (Many people who run Filemaker Server would say it is essential, in the event of a spontaneous shutdown of Filemaker Server, to replace the shut-down files with the latest backup copy.)

So, one suggestion to you would be to evaluate carefully how important this database is to your business and determine whether you should upgrade to using Filemaker Server. Doing so would protect your actual files in the face of network or other problems that are causing the connection to be lost. It would also enable you to take regular, automatic backups. There is a cost, of course. But you might consider it like an insurance policy.

As to your actual network communication problems, these could arise anywhere. It is unlikely that Filemaker itself is the culprit. But Filemaker is very easily disrupted by the slightest networking problems, since it requires an always-up link (unlike a browser, for example).

I assume you are using latest revisions of both your OS (Windows 7, of which I know zilch) and Filemaker?

The problems with the not enough memory and licensed user warnings are, I think, fairly typical of what happens in Filemaker when files and network connections are lost spontaneously. Whatever your setup, it is not good for the network to go down. However, as above, Filemaker Server gives you much more protection if that eventuality does arise.

Though I said I couldn't give a definitive solution, all of this does point to two courses of action:

- Consider Filemaker Server so as to insure your many years of investment, both in the face of your current problems and possible future situations.

- Continue looking into possible network, OS, power supply, cabling and other problems as a way to correct the loss of network that you are seeing.

I'm sure others will pipe up with more detailed suggestions, particularly on the network problems.

Good luck!

Steve


On 19 Aug 2011, at 10:58, Leonard Siskin, DC wrote:

> I have been an amateur Filemaker user for years and run my chiropractic office on a database I built starting in FM5.
>  
> I am using 2 computers, one opens the file using FM11 and one opens it remotely FM 10.
>  
> The system always worked flawlessly but recently the network loses communication with the host spontaneously and I have to re-open the database from the remote location.
>  
> I’ve checked my security software and replaced my router and all three switches the office uses but the problem still exists.
>  
> Sometimes connectivity is lost every few minutes and after several times re-opening the database from the remote computer it will say not enough memory to open the database (I am using a core i7 processor, windows 7 professional and one of the two has 12GB ram and the other, 18GB).   Sometimes I receive an error message stating the maximum number of licensed users are already using the software and it shuts filemaker down on the remote computer.  (Both computers have licensed software)  The only way to re-open the database on the remote computer is to shut down filemaker on both computers and reopen the database then re-open from the remote location.
>  
> Does anyone have any idea why this is happening or how to fix it????
> 
> I really appreciate the input from the group as many of the conversations here have shed light on using the system better.
>  
> I’d appreciate any feedback anyone has.
>  
> Thanks.
>  
> Len