Don Akin wrote:
> I use an INSERT statement in a C# program to add a row to a table
> that has about 50 fields. About 1 in 10 times, not all the fields get
> inserted into the new row. The fields that do not get inserted
> correctly are always one of the same 5 or 6 fields. I have 30 clients
> using this program. The same thing is happening in each client's
> database. I can insert the same row 10 times, and only once or twice
> will it not insert correctly. Blanks get inserted into the same 5 or
> 6 fields.
> I have tried doing a SELECT after the INSERT to see if the fields got
> filled in correctly, then, if the field is blank I try to do an
> UPDATE to correct the blank fields. This does not seem to work either.
Can you post an example of an isnert that does not work. Barring some
corruption, which seems unlikely given the frequency at many clients,
this is usually a programming issue. Could it be that you are inserting
unicode data into a non-unicode column? Are the problems always related
to character type columns?
Also post the table DDL.
--
David Gugick
Imceda Software
<a rel="nofollow" style='text-decoration: none;' href="http://www.imceda.com" target="_blank">www.imceda.com</a>
>> Stay informed about: Some fields randomly not updated in INSERT and UPDATE