-Jay<\/p>","upvoteCount":0,"datePublished":"2012-02-08T12:59:54.000Z","url":"https://community.spiceworks.com/t/ms-access-vba-runtime-error-214/125560/2","author":{"@type":"Person","name":"jay6111","url":"https://community.spiceworks.com/u/jay6111"}},{"@type":"Answer","text":"
\nSame PC but different user does it throw the same error?<\/p>\n
-Jay<\/p>\n<\/blockquote>\n
Yes same error. Logged in as admin too<\/p>","upvoteCount":0,"datePublished":"2012-02-08T13:16:49.000Z","url":"https://community.spiceworks.com/t/ms-access-vba-runtime-error-214/125560/3","author":{"@type":"Person","name":"alcyone92","url":"https://community.spiceworks.com/u/alcyone92"}},{"@type":"Answer","text":"
Not sure, hosted file? If so, does the behavior change if saved locally to machine? Or save a copy in the current version of running MS Access onto local machine and test that way as well.<\/p>\n
None of those work, try running a repair on office, but I’m not thinking that’s going to help, more of a last resort.<\/p>\n
-Jay<\/p>","upvoteCount":0,"datePublished":"2012-02-08T13:35:20.000Z","url":"https://community.spiceworks.com/t/ms-access-vba-runtime-error-214/125560/4","author":{"@type":"Person","name":"jay6111","url":"https://community.spiceworks.com/u/jay6111"}},{"@type":"Answer","text":"
It sounds like your linked table is read-only, open the table and try to manually edit / add data. If it is read-only you can probably rectify it either by refreshing the link or by deleting and re-linking it.<\/p>","upvoteCount":0,"datePublished":"2012-02-09T04:04:42.000Z","url":"https://community.spiceworks.com/t/ms-access-vba-runtime-error-214/125560/5","author":{"@type":"Person","name":"gerard-treacy","url":"https://community.spiceworks.com/u/gerard-treacy"}},{"@type":"Answer","text":"
Program structure, SQL back end and MS Access front end. FE does not work if I run as .accdb or .accde.<\/p>\n
@Gerard9944<\/span> - users can edit the table thru the form all day long with no problems, it is just when running that specific code does an error occurs. Tables have been relinked.<\/p>\n-Thing to try today,<\/p>\n
\n\nrun office repair<\/p>\n<\/li>\n
\nlink program to backup database and test<\/p>\n<\/li>\n<\/ol>","upvoteCount":0,"datePublished":"2012-02-09T05:07:56.000Z","url":"https://community.spiceworks.com/t/ms-access-vba-runtime-error-214/125560/6","author":{"@type":"Person","name":"alcyone92","url":"https://community.spiceworks.com/u/alcyone92"}},{"@type":"Answer","text":"
My initial thought was that it is a primary key conflict but as your other machines / users are working ok I ruled it out. I presume the code is identical to the other machines and has not been modified? My next step would be to check the sql string before it is executed - maybe one of the data values is incorrect or out of range.<\/p>","upvoteCount":0,"datePublished":"2012-02-09T05:29:42.000Z","url":"https://community.spiceworks.com/t/ms-access-vba-runtime-error-214/125560/7","author":{"@type":"Person","name":"gerard-treacy","url":"https://community.spiceworks.com/u/gerard-treacy"}},{"@type":"Answer","text":"
Ok so I went and made a new ODBC connection to the backup SQL database, still got the same result.<\/p>\n
I am using the SQL Server Native client version 10 for all my new machines. So I decided to try the older connection V6. It worked!? I was able to run the code with no error. I printed out a side by side of the two connection and found no difference between the two. I also double checked my ODBC connection and fount the issue.<\/p>\n
Version 10.00.1600 does not work.<\/p>\n
Version 10.50.2500 does work<\/p>\n
I will update the problem PC’s ODBC connection and try it again to verify that is the problem.<\/p>","upvoteCount":0,"datePublished":"2012-02-09T07:47:29.000Z","url":"https://community.spiceworks.com/t/ms-access-vba-runtime-error-214/125560/8","author":{"@type":"Person","name":"alcyone92","url":"https://community.spiceworks.com/u/alcyone92"}}]}}
alcyone92
February 8, 2012, 12:51pm
1
I have a problem and am not sure where to look next.
-Problem:
one of my computers, identical to 3 other except for video card, will not run part of the VBA code in MS Access 2010. It stops when executing a SQL string, highlited in attached PDF.
The error I get is - Runtime Error -2147467259(80004005) ODBC - Insert on a link ‘tblOrder’ Failed
Changing SQL longin
Gave admin permission on PC
Reconfigures ODBC connection - in admin mode
Not sure what else to try or were to look.
SQL_Error.pdf (34.5 KB)
2 Spice ups
jay6111
February 8, 2012, 12:59pm
2
Same PC but different user does it throw the same error?
-Jay
alcyone92
February 8, 2012, 1:16pm
3
Jay6111 wrote:
Same PC but different user does it throw the same error?
-Jay
Yes same error. Logged in as admin too
jay6111
February 8, 2012, 1:35pm
4
Not sure, hosted file? If so, does the behavior change if saved locally to machine? Or save a copy in the current version of running MS Access onto local machine and test that way as well.
None of those work, try running a repair on office, but I’m not thinking that’s going to help, more of a last resort.
-Jay
It sounds like your linked table is read-only, open the table and try to manually edit / add data. If it is read-only you can probably rectify it either by refreshing the link or by deleting and re-linking it.
alcyone92
February 9, 2012, 5:07am
6
Program structure, SQL back end and MS Access front end. FE does not work if I run as .accdb or .accde.
@Gerard9944 - users can edit the table thru the form all day long with no problems, it is just when running that specific code does an error occurs. Tables have been relinked.
-Thing to try today,
run office repair
link program to backup database and test
My initial thought was that it is a primary key conflict but as your other machines / users are working ok I ruled it out. I presume the code is identical to the other machines and has not been modified? My next step would be to check the sql string before it is executed - maybe one of the data values is incorrect or out of range.
alcyone92
February 9, 2012, 7:47am
8
Ok so I went and made a new ODBC connection to the backup SQL database, still got the same result.
I am using the SQL Server Native client version 10 for all my new machines. So I decided to try the older connection V6. It worked!? I was able to run the code with no error. I printed out a side by side of the two connection and found no difference between the two. I also double checked my ODBC connection and fount the issue.
Version 10.00.1600 does not work.
Version 10.50.2500 does work
I will update the problem PC’s ODBC connection and try it again to verify that is the problem.
alcyone92
February 15, 2012, 11:03am
9
The solution is to have version 10.50 for the native client and not 10.00.
Thanks for all the suggestion, it did help me to think a little deeper.
