hello. recently Im having this error. Why is this?

why is that?

PS: after enter a 2nd person in the database it has imported and the first person in. Sometimes when import the data fast, it upload the person, if it take for a while (~40 seconds or more) it show that error on the picture.

I think maybe the command is too long so it need to cut the edges. I think it my also help if you could post the code as well.

this is the code for access database :P

    Me.AmzaBindingSource.EndEdit()
                Me.TableAdapterManager.UpdateAll(Me.AmzaDataSet)
                Me.Table1BindingSource.EndEdit()
                Me.TableAdapterManager1.UpdateAll(Me.StudentDatabaseDataSet)
                Me.Table1TableAdapter.Fill(Me.StudentDatabaseDataSet.Table1)
                Me.AmzaTableAdapter.Fill(Me.AmzaDataSet.amza)

there are and many other lines of code to import people but are for SQL server

This error message means you are trying to insert or update data which is too long.

Eg trying to enter "Dave" into a database column defined as only being 3 characters in length.

Decrease your data or increase your column width.

I changed nothing and somehow this work. Im scared now!
it working well now.. Im so confused
but thanks Dave for all the help you give me all this time

Did you change the data being insrted/updated?

I change the column data type on access database from short text to long text. still got nothing. the some error

Sorry I thought you said it was working now? Is it working or not?

I thought the problem was something else. I was just selfish. My mistake

when enter a word with more than 10 characters
exammple: AltjenBerberi it doesnt upload. show that error
if import AltjenBerb it upload it (have 10)

any way how to fix this?

Show me the design of the table in the GUI please.

I did not understand for what database you told me.
I said for microsoft access because I thought the problem was there
but you meant for SQL. I changed the Data type from nchar(10) to nvchar(50) now it allows me to add data. problem fixed now I guess. :)

Ok cool, this is what I said right from the start!

yea. looks like it was my bad. I misunderstood it