Network Optimize Problems

[Tim Sutherland]

I have been running an application with 4.5 for about 10 years without any trouble. Until recently I was running it on one computer only and never had a problem. Recently I added a system to the network that also needed to access the database. I then moved my application to the server and pointed both computers to the data on the server and did a network optimize. One system is running the full version of 4.5 and the other is running with the runtime version.

Since I did this, random records are getting duplicated during data entry. Initially, I suspected user error but I just noticed that it is doing it on my system also and I know I am not entering duplicates.

I've deleted the shadow directories on each system and recreated them and the problem still occurs.

Any suggestions?

[CALocklin]

RE: Network Optimize Problems

Tim, my guess is that it has nothing to do with the Optimize. To verify this, try running it on the network without optimization.

I had an application that did the same thing. It ran on one computer just fine. It ran over the network just fine as long as only one workstation was accessing it. (In this case, the server is never used as a workstation.) It even seemed to run OK with 2 workstations - but get that 3rd or 4th workstation going and things started falling apart.

Here are the four steps I took to resolve the issues:
1. Pack all the tables. Do this periodically to avoid an excessive build up of deleted files. I can't prove this helps but it seemed to have more index problems when there were a lot of deleted records. (50-100?)
2. Rebuild indexes periodically to make sure they are working correctly. My personal preference is to have a routine that actually rebuilds them instead of just running the Update Production Indexes routine in case one of the indexes gets lost or deleted by a user.
3. Get memo fields out of your main tables. Peter Wayne and others were big advocates of this but I hadn't experienced the issue until recently - now I'm a believer too! Create a separate table with nothing but the memo field(s) and one linking field to the main table. The memo can then be accessed via a set or from a button that opens it in a separate window. As I recall, the separate window is the preferred method. Unfortunately, this was the last thing I did and everything has been working perfectly ever since.
4. Don't let users work in the "Enter" mode. Use routines that will create and immediately save a new record then allow the user to work in the Change mode. This may sound awkward but it can be done so that it is pretty transparent to the user. (You may need to use some bogus data to fill required fields.)

I can't be sure how much #4 actually helped in my case because I did it before #3 and still had trouble. However, #4 is another method that is highly recommended by others.

Good luck and let us know what finally solves your issue so we can all benefit by the experience.

Cal

[David Sander]

RE: Network Optimize Problems

Tim,

There was another user who had this problem recently with duplicate entries on just one networked computer. After much analysis he discovered that he had to both delete all his query files and then deoptimize/reoptimise his database for everything to work out right.

Dave

[Peter.Wayne]

RE: Network Optimize Problems

I found problems with connecting a WinXP Home computer to our network using v 4.5. I believe the problem may now have been solved, thanks to Finian Lennon, who suggested I change the "compatibility" of A5v4.5 to "windows2000". In WinXP the compatibility mode can be accessed by right-clicking on the alpha5.exe or its short-cut, clicking on Properties, then the Compatibility tab. Changing the compatibility to Win95 or Win98 does not work, incidentally--forms won't load.

I also found that v. 4.5 would allow create duplicates (even in Win98) where 4.03 would not if you are in the habit of hiding forms and then re-showing them rather than closing them and later re-viewing them. I changed all the hides/shows to closes/views and eliminated that problem.

[Shaun Holt]

RE: Network Optimize Problems

Cal,

I am new to Alpha and experiencing problems optimising a database developed in Alpha 5 v4.5 (build266). We have ten client workstations each running a full version of Vv4.5 (build266). I have copied the developed database to the server (please find attached a diagram).

When I purchased the ten licences from a vendor in the UK I explained that we wanted to run the database over a network. They supplied me with ten 1 user licences. I have assumed that this is correct.

When I have gone to the first workstation on which I want to run the optimise it works fine.

The problem occurs when I go to the next workstation and attempt to do the the same. First of all I get a 1033 licencing error and then the network optimise option is greyed out from the File menu.

The database is then lost to the rest of the network - To restore the database I have to copy a backed up copy of the unoptimised database back on to the server.

I feel I must have missed a fundamental but there is very little in the manuals on this.

Please find attached to this a network diagram that may help.

Many thanks in anticipation

Shaun Holt

[Shaun Holt]

RE: Network Optimize Problems

This is now solved - This was the method we used:

1 - With no users logged into the system or using the database I took a good copy of the server's directory with the database files in it.

2 - Went to the first PC and ran the network optimise. This was OK. Checked that the shortcuts on the client desktops were set up correctly (i.e. to the C:\ drive not the server).

3 - I restored the good copy of the database taken in Step 1.

4 - Optimised from the next PC.

5 - Restored good copy taken in Step 1.

6 .......(Repeat until last unit is optimised)

This worked very well and has shown the users a marked improvement in the speed of the database execution.


Many thanks to Thomas & Shelly for their help - greatly appreciated.