'field is too small' error

Stuart Hawkins

unread,

Jul 4, 2001, 2:16:28 AM7/4/01

to

Hi,
I'm intermittently getting the following error when attempting to directly
synchronise an access 2000 replica set. It started after I made a design
change (the design master is not involved in the replication) but since then
I have created new replicas on the remote sites from the HQ replica. There
have been no design changes since making the new replicas.

"The field is too small to accept the amount of data you attempted to add.
Try inserting or pasting less data"

Any ideas?

Thanks
Stuart Hawkins

Michael (michka) Kaplan

unread,

Jul 4, 2001, 11:53:44 AM7/4/01

to

What was the design change?

--
MichKa

the only book on internationalization in VB at
http://www.i18nWithVB.com/

"Stuart Hawkins" <stu...@sanctified.ltd.uk> wrote in message
news:eAygyCFBBHA.1928@tkmsftngp03...

Stuart Hawkins

unread,

Jul 4, 2001, 12:21:16 PM7/4/01

to

Thanks for the reply,
I changed the type of the key field on one of the tables from long integer
to text. Then also changed the same field where it was a foreign key in
other tables. The change was unavoidable!

Stuart

"Michael (michka) Kaplan" <forme...@spamfree.trigeminal.nospam.com> wrote
in message news:ufRWCGKBBHA.1816@tkmsftngp07...

Michael (michka) Kaplan

unread,

Jul 4, 2001, 2:50:26 PM7/4/01

to

So you intermittently get an error? Does that mean on a scond sync it will
not occur?

--
MichKa

the only book on internationalization in VB at
http://www.i18nWithVB.com/

"Stuart Hawkins" <stu...@sanctified.ltd.uk> wrote in message

news:u38fuUKBBHA.2016@tkmsftngp05...

Stuart Hawkins

unread,

Jul 4, 2001, 3:24:59 PM7/4/01

to

No, it runs ok for a couple of days (it synchronises
overnight) then the error re-appears. Once a replica
gives the error it no longer synchronises (though it will
compact without errors) and I have to import the
new/changed data into the good replica using queries then
create a new replica from it and send it back to the site
that wouldn't synchronise. Compacting the data appeared
to fix the problem once (i.e. it allowed the two replicas
to synchonise) but this only happened once!

Any ideas??

Stuart

>.
>

Michael (michka) Kaplan

unread,

Jul 4, 2001, 3:44:53 PM7/4/01

to

If the replica will not synchronize any more then it is clearly some form of
corruption. Do you have the latest version of Jet?

On the other hand, it could be due to a problem like the one described in
the KB

http://support.microsoft.com/support/kb/articles/Q121/5/12.asp

in which case it would suggest an underlying schema issue. Check out the
default valur prop in forms or queries in your app; perhaps one of them is
invalid and based on the old schema? The type of data that was not able to
be sync'ed may give clues as to where to look.

In other words, I would suspect pilot error here.

--
MichKa

the only book on internationalization in VB at
http://www.i18nWithVB.com/

"Stuart Hawkins" <stu...@sanctified.ltd.uk> wrote in message

news:265b01c104bf$040fe620$19ef2ecf@tkmsftngxa01...

Stuart Hawkins

unread,

Jul 6, 2001, 12:55:05 AM7/6/01

to

Thanks for the suggestions. I am having no success tracking down the source
of the corruption though. Is there a way of finding out which data
prevented the synchronisation? I have the latest version of Jet.

Stuart

"Michael (michka) Kaplan" <forme...@spamfree.trigeminal.nospam.com> wrote

in message news:OFZ8MHMBBHA.1872@tkmsftngp07...

Michael (michka) Kaplan

unread,

Jul 6, 2001, 1:01:23 AM7/6/01

to

If you look at the second half of this message I openly doubted that it WAS
corruption.

There is no specific way to find out what data could not be synchronized,
but all rows that were not synchronized have an s_generation of 0. I would
recommend you investigate based on the assumption that it was in fact a
schema issue and not corruption.

--
MichKa

the only book on internationalization in VB at
http://www.i18nWithVB.com/

"Stuart Hawkins" <stu...@sanctified.ltd.uk> wrote in message

news:O10ueedBBHA.1768@tkmsftngp03...