Access error 3270 when running a query
I am running a newly installed MS Access (MS Office 2010) and when double clicking on a Select Query it will not run (when running from a Macro the error 3270 is reported). I went into the DB design mode for the query and then selected "RUN" and it ran fine. However, when the query is double-clicked this query did not run. In fact, ALL Select queries did not run. Double-clicking on Append, Update, Delete queries all ran fine. Only Select Queries are not running when double-click, only in the design mode.
I have checked other Access Db's and all Select queries are not running either...so it is not this one DB. This DB and all others run fine on other Office computers.
I have checked the Trust Center Macro settings and other settings with other Office computers and the DB Select queries all ran fine.
Can anyone assist or direct me how to resolve this issue.
I have checked other Access Db's and all Select queries are not running either...so it is not this one DB. This DB and all others run fine on other Office computers.
I have checked the Trust Center Macro settings and other settings with other Office computers and the DB Select queries all ran fine.
Can anyone assist or direct me how to resolve this issue.
To be sure,
Have you run the Compact\repair utility lately?
Try creating a blank new DB and importing all he objects...
Have you run the Compact\repair utility lately?
Try creating a blank new DB and importing all he objects...
<I have checked other Access Db's and all Select queries are not running eithe>
Since this is not confined to a single database, I'd assume that you have trouble with the installation of Access/Office on that machine, or with the installation of Windows.
First be sure that Windows is fully up to date, then be sure that Access/Office is fully up to date. If that doesn't resolve the issue, then try a Repair of Office. If that doesn't work, then an uninstall/reinstall might be in order.
Since this is not confined to a single database, I'd assume that you have trouble with the installation of Access/Office on that machine, or with the installation of Windows.
First be sure that Windows is fully up to date, then be sure that Access/Office is fully up to date. If that doesn't resolve the issue, then try a Repair of Office. If that doesn't work, then an uninstall/reinstall might be in order.
ASKER
@ BOAG2000: compact and repair is not the answer and creating a new DB isn't either. This problem occurs on previous DBs and newly created DBs in SELECT queries only.
I have been able to isolate this down a bit more. Logging as Administrator on the computer, Access runs fine with all queries. I performed a 'Repair' on Office and the problem remains. Previous versions of Access 2007, these DBs ran fine.... i.e. the queries. The problem manifested itself after MS Office 2010 was installed.
I may and most likely will have to fully uninstall MS Office 2010 and reinstall... however, should this error reoccur...this question will remain open. Preferably I would like to find a fix prior to the last step.
I have been able to isolate this down a bit more. Logging as Administrator on the computer, Access runs fine with all queries. I performed a 'Repair' on Office and the problem remains. Previous versions of Access 2007, these DBs ran fine.... i.e. the queries. The problem manifested itself after MS Office 2010 was installed.
I may and most likely will have to fully uninstall MS Office 2010 and reinstall... however, should this error reoccur...this question will remain open. Preferably I would like to find a fix prior to the last step.
,This problem occurs on previous DBs and newly created DBs in SELECT queries only.>
Sorry, I missed that in the earlier post...
Sorry, I missed that in the earlier post...
If you can reproduce the issue using a simple database, with one table and one select query, upload it.
I remeber a similar (probably) problem, where the doubleclick interval was very small.
It can be adjusted from Mouse control panel.
I remeber a similar (probably) problem, where the doubleclick interval was very small.
It can be adjusted from Mouse control panel.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
A solution was found about 2 hours prior to the last comment posted on this question. The solution was to create a new user profile, all security question were checked, test the database in question and all other databases to confirm the solution. It was determined that Access 2010 Trust Center option on the initial 'opening' of the first database is the 'bad' profile would not update corrections. To attempt to locate and manually change the Windows Registry would have been time consuming. The required Trust Center selections were made prior to opening any user databases. Once those options were properly selected all modified databases operated normally.
One note to all Administrators that may have legacy databases; if the database requires MSCalc.ocx / help or 'dll' files ensure those are copied to the respective Office or Windows folders. Also, a legacy db is NOT installed for MS Office 2010, that is the Utility.mda, this db should also be copied to the respect Office## folder to maintain integrity of the legacy database.
I will be closing this question. Thank you all for your inputs.
One note to all Administrators that may have legacy databases; if the database requires MSCalc.ocx / help or 'dll' files ensure those are copied to the respective Office or Windows folders. Also, a legacy db is NOT installed for MS Office 2010, that is the Utility.mda, this db should also be copied to the respect Office## folder to maintain integrity of the legacy database.
I will be closing this question. Thank you all for your inputs.
< The solution was to create a new user profile>
Then it would seem that my last comment would be your solution. We have no way of knowing if you've reached a solution outside of EE.
Then it would seem that my last comment would be your solution. We have no way of knowing if you've reached a solution outside of EE.
http://www.wiki-errors.com/err.php?wiki=3270