Re: Key violations???????

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

From: Dennis (Dennis_at_discussions.microsoft.com)
Date: 11/22/04 

Date: Mon, 22 Nov 2004 08:45:36 -0800

I was originally using straight ADO database commands to read/write the
tables. However, due to the size of the table, I was running out of system
resources on my PC. That generated all kinds of errors, including the one you
detailed in your first post. I switched to direct SQL statements instead, and
the problems disappeared.

Dennis

"Jay" wrote:

> Thanks, Dennis:
>
> What do you mean change to read/write? The target table I am using is
> read/write-able as it stands currently! I don't understand how what you did
> changed things in your case. Please explain further?
>
> Thanks
>
>
> "Dennis" wrote:
>
> > I got that as well. I was working with a huge table (500,000 records). Seemed
> > like a resource/timing issue to me. When I changed the method I was using to
> > read/write the table, the problem went away. (Thanks to the brain trust on
> > these newsgroups!)
> >
> > "Jay" wrote:
> >
> > > Is there a routine or function to check where a key violation occurs? I have
> > > taken the query and the target table apart and put them back together again
> > > to no avail.
> > >
> > > Everything seems to be be fine. All data types match, at least it seems that
> > > way, anyway! Only when I try to append the data to the target table I keep
> > > gettin a "Key Violation Error". The table is a pretty big, so, if there is
> > > any method for checking or trapping the field where the Key violation is,
> > > that would be big help!
> > >
> > > Thanks,