Search results

  1. V

    Synchronisation error

    Hi David: I have done a lot of work on this since I changed the retention period. I wasn't replicating temp tables, but originally I did have a lot of queries running that were updating every record in a table, rather than just the ones that needed to be updated. I have now changed this so...
  2. V

    Synchronisation error

    Hi David, David I am absolutely indebted to you. You advice is better than I dared hope to receive and I now have many new avenues to explore: On your inital comments: I changed the retention period to about 30 days so this is why I now use the DM for production editing (because then it...
  3. V

    Synchronisation error

    Hello all. I really hope you can help me. I have a replicated database - see attached for its structure. Most people have no problem synchronising but I have one user in the US who regularly gets the following error when trying to synchronise with the US Server: "The field is too small to...
  4. V

    Problem when synchronising - error 3163

    Hello. I am getting the following error when synchronising between 2 replicas: The field is too small to accept the amount of data you attempted to add. Try inserting or pasting less data. (Error 3163) I have no idea what is causing this, since there have been no design changes since the last...
  5. V

    Form not loading properly

    Hi. I am running a form on top of a query with around 1500 records in it. The query mostly uses tables that are joined with referential integrity. The form has buttons and conditional formatting. It was fine until today, when suddenly the form has stopped loading properly. It looks all...
  6. V

    Synchronisation conflicts that won't go away

    I have a database which i regularly synchronise with another. Recently some conflict errors appeared in tblPartNumbers: 3 of them had the following conflict message against them: "Delete/RI conflict. The primary key record has been deleted by another replica, therefore this referencing record...
  7. V

    Synchronisation conflicts

    Thanks for the tip Smart. I will try to resolve manually now I can see the conflicts. Voisine
  8. V

    Synchronisation conflicts

    Hello. I have a replicated database, and I synchronise with other members of the replica set using Access's own synchronisation tool. Everything was fine until recently, but now it keeps telling me that there is a conflict bur when I click to resolve the conflict it tells me that there are no...
  9. V

    KeepDesignChangeHistory

    Luckily for me there is a genius out there called Michael Kaplan. I've just been referred to his site http://www.trigeminal.com/ because he's designed some software called TSI Synchronizer which does exactly the job I need it to do. And he's been kind enough to distribute it for free!
  10. V

    KeepDesignChangeHistory

    My database is set to compact on close, but that is not what is causing the large file size. See http://support.microsoft.com/kb/q182464/ Thanks.
  11. V

    KeepDesignChangeHistory

    Sorry, I actually need MS Replication Manager for Office 2003, not XP. Any assistance greatly appreciated.
  12. V

    KeepDesignChangeHistory

    Hi All, I have a replicated database which has puzzled me for some time because it is growing in size extremely quickly. After doing some research I have found that this is because I have a number of delete queries running but because the KeepDesignChangeHistory property defaults to 1000, the...
  13. V

    OutputTo

    Thanks ghudson. I will have a look at this.
  14. V

    Access Database Replication

    Don't worry I have figured it out - I have to synchronise with the deleted replicas. Thanks, Kate
  15. V

    OutputTo

    I have a query that currently generates about 20,000 records. When I tried to write code to output it to excel using DoCmd.OutputTo acOutputQuery, "qryStockTurns4", acFormatXLS, , True It comes up with the following error: "Run time error '2306' There are too many rows to output, based on...
  16. V

    Access Database Replication

    I have a design master with 6 replicas. Historically there were more replicas which have now been deleted but how do I go about deleting the file paths of these deleted replicas from the list of possible synchronisation partners? Is it as simple as just deleting them from MsysReplicas? Thanks.
Back
Top Bottom