Sunday, February 26, 2012

error 3073 problem

Hi I have a problem with inserting new data for a newly connected database. What i do is i have a current connection open and running. When the user picks another database source from an OpenFileDialog, I create a temporary variable to test the database connection (from the openfiledialog) and if it can connect then i close the previous connected database and connect to the new database. I close the previous database and set the new database into one and the same variable.

The problem is when i connect to the new database, and am going to insert some new values to a certain table. It shows the error something like:

error 3073. An updatable query is necessary.

I have checked the data source of the database and it contains the path where the new connection is. The sql query is also valid because i have checked it in the ms access query builder. The permission is also valid since it is in write permission.

Hope anyone has an idea for my problem. Thanks in advance!

Please post the query.

SQL Server and Access have syntax differences in updating.

For example:

Access

--

Update table1 t1, table2 t2

SET t1.ID = t2.ID

...this will not work in SQL

SQL Server

--

Update t1

SET t1.ID = t2.ID

FROM Table1 t1

LEFT JOIN Table2 t2 on t1.ID = t2.ID

So testing the query in Access might fail in SQL Server.

Adamus

|||Here is the sample sql:

INSERT INTO [table name](ID, DIVISION, USER_NAME, EXEC_TIME, [CONTENTS]) VALUES (1, 'Division', 'user', '2005/05/19 10:45:01', 'Comments.');

After I call the OleDbCommand to ExecuteNonQuery, this error occurs. I am using MS Access by the way. Thanks!
|||Could you please the code part which is relevant (including initialization for the command) ?

Jens K. Suessmeyer.

http://www.sqlserver2005.de

|||

Technically this is not a SQL Server issue (since you're using Access), but please post the full ADO coding.

Adamus

|||Sorry for the confusion I was also hoping someone in this forum could also help me in my problem. I was thinking that this error is not dependent on what type database you use. But thanks still for the effort. This is another thread I created that has the necessary codes involved.

-> http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1833561&SiteID=1

Please feel free to take a look. If you are going to reply kindly reply to this thread (SQL Server) instead so the threads will be more organized (opinions of the people in a particular expertise) and i won't get more confused Smile Thanks a lot!

No comments:

Post a Comment