Replication and memo field

Collapse
This topic is closed.
X
X
Collapse
 
  • Page of 1
  • Time
  • Show
Clear All
new posts
Previous template Next
  • David C
    #1

    Replication and memo field

    I have a backend tables database that I created replicas from. It was
    unreplicated and I ran the Tools...Replica tion...Create Replica. It
    created the design master and a replica. I then opened up a table that had
    a memo field in it and tried to either add or edit a record. When I exit
    the memo field (and saving the record) the system blows with the stupid
    "Microsoft Access has
    encountered a problem and needs to close. We are sorry for the
    inconvenience." and has the send error buttons. How in the heck is a
    person suppose to troubleshoot this when you don't even get an error
    number/message?!!!???
    I then opened the unreplicated copy and had no errors. Has anyone run
    accross this problem? Help!


    Tags: None
    • David W. Fenton
      #2
      Re: Replication and memo field

      "David C" <dlchase@lifeti meinc.com> wrote in
      news:1%IWc.3072 $1W5.2823@newss vr31.news.prodi gy.com:
      [color=blue]
      > I have a backend tables database that I created replicas from. It
      > was unreplicated and I ran the Tools...Replica tion...Create
      > Replica. It created the design master and a replica. I then
      > opened up a table that had a memo field in it and tried to either
      > add or edit a record. When I exit the memo field (and saving the
      > record) the system blows with the stupid "Microsoft Access has
      > encountered a problem and needs to close. We are sorry for the
      > inconvenience." and has the send error buttons. How in the heck
      > is a person suppose to troubleshoot this when you don't even get
      > an error number/message?!!!???
      > I then opened the unreplicated copy and had no errors. Has anyone
      > run accross this problem? Help![/color]

      Is this in the replica or the design master?

      Have you compacted the MDB with the problem?

      Have you tried creating a new replica? If so, does it exhibit the
      same problem?

      Are you sure you need replication in the first place?

      There is nothing inherently wrong with replication and memo fields
      that is not also a weakness of unreplicated memo fields (because of
      the way they are stored, memo fields are more subject to corruption
      than other types of data).

      --
      David W. Fenton http://www.bway.net/~dfenton
      dfenton at bway dot net http://www.bway.net/~dfassoc

        Comment

        Previous template Next
        Working...