I have an accdb database that is used by multiple individuals and stored on a network share. When opened in Acccess 2007 the following message appears:
Cannot open database "\\databasepath\filename.accdb". It may not be a database that your application recognizes or the file may be corrupt
Access 2010 opens the database with no problems.
What is the most common cause of this issue? I searched for database repair tools and can't find any Microsoft tools for accdb files (JetCompact didn't do it). I ran a compact and repair via Access 2010, did a save as locally and then copied it over to the share - no effect.
Other than magically upgrading all my users to Access 2010 (which won't happen) I'm in the dark here.
You may have some features you're using in 2010 that aren't supported in 2007.
Look here for more info.
Most likely someone opened it in 2010, edited your report and saved the change. This will break 2007 every time. 2010 is NOT backwards compatible with 2007
I would make a back-up, make another back-up and then first try importing all but the tables that contain attachments into a new database.
you can also check this: https://dba.stackexchange.com/questions/71906/ms-access-mdb-ldb-database-corrupted
Related
In order to create an indipendent runtime file.accdr out of a file.accdb, I've downloaded AccessDeveloperExtensions.exe and AccessRuntime.exe and installed them.
Update:
See article Here is the Google Translater .
Update end.
Opening Access 2007 I could create the install package for creating the file.accdr out of the file.accdb.
The problem I get is that an important function does not work anymore. It's the export of a report, wherelse the export of a table still works.
Opening Access I get the following message:
you don't have a source code control program (such as Microsoft Visual Source Safe) installed on
your machine. The source code control commands are therefore not available
I click on OK and Access opens my db.
My db is based on a table, a form, a report and a query. Exporting the report worked in the past, but doesn't work anymore. The message shown is the following:
Impossible to complete output operation. Assure that there are no syntax errors. If the syntax is
correct, reinstall Microsoft Office Accept...
(I've translated the text from Italian).
Now is there another, easier way from reinstalling the hole thing? Because after reinstalling Access I will also have the need of creating databases.accdr and so I have reinstall runtime.exe and DeveloperExtensions again, what would result in the same problems I had before.
Somebody could help?
I'm very new to visual studio and visual basic.
I already studied the basics of visual basic so I tried stepping up a little and play with database in visual basic. I'm using visual studio 2010.
I first made an access database. I followed the instructions that I searched on the net on how to connect it to your visual basic program. Data>Show Data Source>Add Data Source> ...
But when I search on how to do it, I became really confuse because of these things:
Is vba and vb the same?
all the tutorials are for access but why do they still need to have a stringconnection when they already connect it using what I did?
they are searching for .mdb but the extension of my access database is .accdb?
they have an sql query for inserting the datas from the csv file but the pc that will be using the program don't have sql installed but mysql. Will it still work?
I'm still noob in these things so please if anyone can shed some light in these questions, thank you very much. >.<
VBA and VB 6.0 are almost the same. Main difference is that VBA is intended to be host in application like Excel, Word ....
BUT language you probably use with VS 2010 is VB.NET and that is something different. VB.NET is object oriented language which target .NET Runtime and Framewor. See Difference between Visual Basic 6.0 and VBA
Connection string is a string that specifies information about a data source and the means of connecting to it.
In .NET this describe (or can) path or location, provider, credentials and other informations. See MSDN Connection string in .NET
If I'm correct MDB is older format and ACCDB is format used by Microsoft Office Access 2007 and newer. Here is post how to connect to access db file: SQL connection string for microsoft access 2010 .accdb
But do you realy need to use acess database? There are better alternatives.
There is no need of real database engine for your scenario. You wanna to use standalone file as a datasource, dataprovider will be responsible for interaction with datasource. E.g. OleDB provider
I have a 2007 database that was opened by someone running Access 2010.
They deleted some tables and saved the database but now the database doesn't open on any pc running Access 2007.
I believed that there was compatibility between 2007 and 2010 - I assume I'm wrong?
Thanks for reading.
The issue is that even when saving the file in Access 2007 format it does not actually save it with only 2007 compatible syntax. The idiots at Microsoft chose to break backwards compatibility in their rush to release on schedule. Other than recreating your forms and reports you are out of luck.... Hope you kept a copy of your original code.
I am about to release some reports in Access 2007 and I need to lock down the Queries so that no one can change the queries does any one know how I can do this in Access 2007?
Please Note: Simply adding a GUI and hiding the "database window" is not enough as people can still get in with the right key stroke etc.
You could Make an .ACCDE, and give that to your users to execute.
You can create an .accde file from an
.accdb file by clicking Database Tools
on the Office Fluent Ribbon, and then
clicking Make ACCDE. When you create
an .accde file, Access compiles all
the code in the database and strips
the editable version of the code from
the new .accde file. This process both
reduces the size of the resulting
database and guarantees that no one
can change the original source code.
When you open an .accde file in
Access, the form and report designers
and the Visual Basic Editor are not
available. In addition, you cannot
transfer forms, reports, and modules
to another database by export or
import.
However, since an ACCDE is apparently less secure than its predecessor the MDE, your best bet might be to convert the database to Access 2003 format by using the Save As command, and making an MDE from that. If you open an older .mdb file in Access 2007, a Make MDE command appears on the Database Tools tab instead of the Make ACCDE command that appears when you are working in an Access 2007 database.
In Access, if you click the Windows button and then Access Options, then Current Database, you will see options to disable navigation and keyboard shortcuts.
My application is built to scan MS Access database in vb.net 2005.
Problem:
MS Access DB is opening when Access Run-Time (But no Full version of MS Access) is installed in the system as well. But showing error while scanning through our Tool.
Solution:
Need only Full version of MS Access.
Suggestion:
To Identify, whether the required application (like here we need MS Access Full version) is installed or not at the time of installing our Tool(Through MSI).
Is it possible to identify MS Access Full version with Run-Time while installing the Tool?
As per my knowledge it is possible to identify the application along with its version while installing.
Could anyone suggest me is it possible or not, if yes then please provide me some useful reference or links.
Thank you.
Since you are asking for an answer that tests during your install process, the simplest answer is to query the registry. Prior to Access 2007 there was a specific key for Access Run Time, but it seems that with 2007 you need to check the Installed Packages path of the Office registry hierarchy.
Here's the key for Access 2007 Runtime:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\12.0\Common
\InstalledPackages\90120000-001C-0409-0000-0000000FF1CE
And here's the key for Access 2007:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\12.0\Common\
InstalledPackages\90120000-0015-0409-0000-0000000FF1CE
If you later want to re-verify that the setup remains as you want/need it, then try this:
IF SysCmd(acSysCmdRuntime) = true THEN
...
END IF