file sharing lock count

You should be able to have your network administrator increase the amount of file locks and record locks on the server.  

Another consideration:  If you have tables that are routinely cleared with Delete queries and they are being replicated, you should consider unreplicating those tables.  The nature of those tables would not be to share data across replicas; therefore, each replica should have its own copy of the table (just do an Export of the table from the Design Master after you have unreplicated the table and re-synchronized).

Thanks, MGrattan.
The master replica is not on a server, but on a client machine. I have read in the Access help that I can increase the Jet lock count in the registry, which I did (but maybe not enough).
I have read that I can do this programattically using SetOption() function. Do you have an example which uses this function?
Also, should this be done only on the 'server', or should this be done on the client machine as well?. I am asking this because on the client, the registry is locked by the admin, so it will be helpful to set the max locks with the SetOption function.
Good point about the 'delete all' then 'append' tables: I have one of those and I'll try to not replicate it. But... er... this happens when I FRESHLY RECREATED the replicas as well!!! All the databases are exactly the same, and I get this error :-(

I don't have any examples that set the SetOption function to set the jet lock count.  However, I've not received any errors during replication that were caused by this setting; they've always been related to the file locks and record locks on the server.  Even if the master is on a client machine, it still has to synchronize with replicas that are on a server, correct?  If that's the case, I would still concentrate on increasing the file locks and record locks on the server.  Here are the settings on my Novell server:

 Maximum Record Locks Per Connection         15000
 Maximum File Locks Per Connection           1000
 Maximum Record Locks                        20000
 Maximum File Locks                          5000

Hope that helps; if you need more assistance I can help you look into the jet locking settings as well.

Do you mean, even if I replicate between two client machines?
Let me give more info on what we are trying to do:
On the C: drive on one client machine, there is the master database.
On another machine, we made a shared folder and mapped this folder to a drive letter. This machine has the first replica.
These two machine are on the network of the company.

Then, we have a laptop, which is not possible to connect to the network. The laptop has a replica too.

For replication I made a program which worked fine, one button lets the user to replicate between the two machines on the network, and another button which lets replicate between the computer with the master database and the laptop.

This procedure worked fine for months, but from now, there is no way.

We are forced to put the master database on the client computer, because it is the only way we have to connect the laptop. Let me tell you that we are not allowed to connect the laptop on the company's network. This is why, when connecting the laptop, we disconnect the company's network. Thus the "two buttons" program.

Again, my question, is it related to lock settings on the server? I think not, because when replicating with the laptop, there is a peer to peer connection between two computers only.

Please apologize my phraseology, my english is a bit poor ;-)

OK, I understand your scenario now.  How are you connecting the laptop to the machine that contains the Design Master?  Direct peer-to-peer without a hub; with a hub; direct cable connection...etc.

Its a peer to peer connection, and there is a little hub.
Both machines are on Win 98.
The third machine, with the second replica is on Win 95

Thanks for the link. I'll try this when I return to the customer, this will be only next week, but will let you know.

Bon week-end.

OK, good luck and have a nice weekend.

Hi!

Good news: I have set maxlocksperfile value to the highest possible &FFFF, as we don't have a Novell network.
The replication took a very long time, but finished at last!

Thanks.

Great!  Glad to hear you got it working.

Mike