Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion GroupsFormsForms ProgrammingQueriesModules / DAO / VBAReports / PrintingMacrosDatabase DesignSecurityConversionImporting / LinkingSQL Server / ADPMultiuser / NetworkingReplicationSetup / ConfigurationDeveloper ToolkitsActiveX ControlsNew UsersGeneral 1General 2
Access DirectoryToolsTutorialsUser Groups
Related Topics
SQL ServerOther DB ProductsMS OfficeMore Topics ...

MS Access Forum / Replication / March 2005

Tip: Looking for answers? Try searching our database.

Synchronise error "Data too large ..."

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Gavin of St Helens - 12 Mar 2005 11:49 GMT
When synchronising Design Master with replica get error message like "Data
too large for field ..." and synchro. fails. Does not always happen and the
actual amount of data being transferred does not seem to cause the problem!  
The replicas are stored on data 'pens'and transfered to remote desktop PCs
hence the PCs cannot physically be connected to the PC holding the Des. Mas.
This way of working seemed to cause problems for another newsgroup
contributor - on 3/3/05 "During sync, Master data goes to..."
We are running Access 2000 (not Developer edition and hence Replication
Manager not available.
Anyone met this before, or got any clues please?
Cheval - 15 Mar 2005 22:35 GMT
You're making a common mistake and causing the corruption.

Read the Posts from the message "During sync, master data goes to replica,
but not vice/versa" on the 2005/3/2 (Universal date format)

> When synchronising Design Master with replica get error message like "Data
> too large for field ..." and synchro. fails. Does not always happen and the
[quoted text clipped - 6 lines]
> Manager not available.
> Anyone met this before, or got any clues please?
Gavin of St Helens - 16 Mar 2005 13:03 GMT
Thank you Cheval.  From a careful reading of the messages identified, it
seems that we may not be able to use data 'pens' successfully.  However,
there is a slight difference in our set up - we use a separate data 'pen' for
each separate desktop that is in the system so any one pen is only ever
synch'ed with the Master and a single other PC, does this make any
difference?
You recommended to 'Rob' that he either sets up a LAN or uses Indirect
Replication; neither of these is available to us - the first because our
staff have remote desktop machines, the second because we don't have
Developer Edn. of Access = no Replication Manager = no Indirect Replication I
think.
Alternatively, is is possible to clear the list of 'known replicas' and set
up fresh copies now and then to avoid the 'list full' issue?
Again, many thaanks for the advice.
Gavin.

> You're making a common mistake and causing the corruption.
>
[quoted text clipped - 11 lines]
> > Manager not available.
> > Anyone met this before, or got any clues please?
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.