access replica and client/server applications

[temporaneo1234]

Yesterday night I was not so happy 'cause, after working for a month to convert my application from client.mde/server.mdb standard to client.mde/server.mdb + replica, I realized an application too slow.

On LAN, the client (FrontEnd) is very slow to link to a server (BackEnd) based on a file of access (*.mdb) replica (master).

Before replica convertion, the application opens in 1/2 seconds, and now it takes up 3 minutes, and everty time make an operation, the avarege time is so long...

Only if FrontEnd is located in the same pc of BackEnd, application works with normal access time.

I have found in newsgroup (posted from Michael michka Kaplan) that this situation can be based on shared resources/drive to deactivate.
I have tried in client-PC's (with WinXP) to remove sharing, but nothing changes.

The application is based on Access.2003 (same FE that BE)

There are some ideas before I left replica to past?

Bye
Gianluca

 

[BNPMike]

I'm getting lost here. Replication is a process to synchronise two or more databases. It is assumed they have become unsynchronised because transactions have been made to each separately. Your application should be unaffected except when you are synchronising.

You seem to do a transaction and then have replication work immediately. If your database can see the other database then you don't need replication. You simply update the two databases. Or more sensibly, just have one shared instance of the data. Replication is for databases that are disconnected.

What was the reason you decided to add replication?

 

[temporaneo1234]

I need replication because I have this configuration:

site 1
1 pc server with BE+FE
2 pc client with FE

site 2
1 pc server with BE+FE
1 pc client with FE

Two sites are in different street so I need replication to exchange data from each sites.

Gianluca