By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
425,635 Members | 917 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 425,635 IT Pros & Developers. It's quick & easy.

Replication and memo field

P: n/a
I have a backend tables database that I created replicas from. It was
unreplicated and I ran the Tools...Replication...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!
Nov 13 '05 #1
Share this Question
Share on Google+
1 Reply


P: n/a
"David C" <dl*****@lifetimeinc.com> wrote in
news:1%*****************@newssvr31.news.prodigy.co m:
I have a backend tables database that I created replicas from. It
was unreplicated and I ran the Tools...Replication...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!


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
Nov 13 '05 #2

This discussion thread is closed

Replies have been disabled for this discussion.