Access 97 - out of memory

[Sheila]

I have a client that runs a database on Access 97 on her
pc, she also has a duplicate of this on a server that runs
server 2000. The original programmer set this up so that
she could update and add to the database on her pc then
sychronize to the database on the server. Over the last
few months the database on the server doubles in size
during this synchronize and she receives an "out of
memory" error on her pc. Her tech states that both the
pc and server have adequate memory.

I am wondering if this is caused by some microsoft update
or patch recently installed. Has anyone else experienced
this problem?


Thank You

 

[GVaught]

More likely a network bottleneck. What is the distance between the client
and the server? Are we talking same building? external building? through the
Internet? Also assume when you say synchronize you mean replication?

 

[david epsom dot com dot au]

'Out of memory' just indicates a general replication
error - size of memory is probably not the problem. If
it is the problem (like on Windows 95), it is probably
out of resources, not out of general memory

There were some replication problems that were fixed in
SR2/SP3 for Access 97/Jet 3.5. Is it possible that the
problems you are seeing now are because you rebuilt the
PC and failed to rebuild Access/Jet?

But it may be a problem with a corrupt replica, or it may
be a network problem.

You should try re-creating the replica. If you don't know
how to do that, you should consider getting in a developer
with replication knowledge.

If you want to try it yourself, you should probably
direct your questions to
microsoft.public.access.replication

(david)