I use an Oracle Spatial database with an MS Access front end and recently data fields have started to disappear. When I output a summary of the records names have been disappearing that were in the previous summary. It is an older system that I did not build so I don't know what is going on in the back end. What could be the reason for this? The system is about 8 years old and this problem has only popped up recently.
I haven't done any testing or playing about in the background as I am unfamiliar with MS Access and I don't want to risk doing more damage.
Related
I am developing an Access application on Access 2019. I have split my project into a frontend and backend. I am trying to deploy the application to a user that is using Access 2016. When linking the backend tables in the frontend file, I run into this error:
The Microsoft Access database engine cannot read the data in Receiving.
The minimum required version to read the data is 16.0.7124.1000.
This only happens for two of my tables however, Customer and Receiving. These are the only 2 tables to use an AutoNumber field with the Field Size set to Long Integer.
Is this an issue with the AutoNumber? Or is the Long Integer field size not supported in Access 2016? Wondering what the best option is for me to link this table to a 2016 version from a 2019 version.
Edit:
Here is the output of the Database Documenter tool for the Receiving table:
This specific error is caused by the Large Number data type, or BigInt.
You can read the documentation on that here
Note that support has been added to Access 2016 in later updates, that's why the minimum required version starts with 16 which corresponds to Access 2016, so just updating Access 2016 might solve your issue.
Else, remove all large number fields.
Note that Large Number and a number set to Long Integer are entirely different things, a long integer is 32-bit long and supported by all versions of Access, a Large Number is 64-bit long and only supported since Q2 2017, and has certain issues when working with it in VBA.
Access tends to sneak in the Large Number datatype when importing from Excel. I strongly recommend you avoid it unless you really need it, both for compatibility reasons, and to make using your tables in VBA a lot easier.
The rule tends to be simple:
You can near always go forward. That includes word, excel, or Access.
In other words?
You have to develop with and use the lowest common version of Access. So, say you can work with Access 2010. Then 2013, 2016 and 2019 users will have no problems.
But, going "back in time" or "back in versions"?
That tends to be a problem.
So, if you still going to have some users of 2016? Then that has to be what you use for development. This issue often applies to Excel or word. You use the v-next great version and some new feature (or new format)? Then previous versions can experience trouble.
I have an MS Access 2007 split database. The Back End database contains 1 table. It is on a shared drive and front end has a data entry form with Macros, also a linked table from back end. Everyone in the organization has same version of Access (2007), same operating system etc.
Problem is I am able to open and add records to the front end but when anyone else try to open the front end it comes up with "Unrecognized database format" and they couldn't open it.
So far tried changing New database sort order to general - Legacy/ Compact and repair database from database tools but still not working for other users. Almost spent half a day searching and trying various solutions without success. Any help into right direction will be highly appreciated.
The lock file got corrupted. Delete it and re-open the application.
Using Access 2013, Sharepoint 2010 OnPremise
I have an Access database that uses Sharepoint 2010 for a back end using Linked Tables.
A few months ago there was a request to have a field contain multiple values, and I stupidly implemented that change, not fully understanding all the issues behind that. Initial research lead to it being "ok" for Sharepoint Lists.
Due to the company architecture, this application needs to be accessible on a Kiosk machine that doesn't have access to the Sharepoint site, but still is connected to the internet.
If the computer runs the application while connected to the internet it will hangup/stall when opening because it's trying to resolve the connection of the linked tables or trying authenticate.
But if the computer runs the application while not connected to the internet it will operate as it should in an offline mode. All data is accessible.
Since we can't/don't want to disable the internet of the Kiosk machine the solution was to convert all the Linked Tables to local tables and issue it to the machine that way.
But now a few months later when trying to make the offline mode application we get the following error:
You cannot enter that value because it duplicates an existing value in the multi-valued lookup or attachment field
I think it has to do with that multivalue field, which has turned into a huge headache, but can't be undone for at least a couple more months.
The Offline mode functionality was created long before the multivalue change, unfortunately that part of the application wasn't tested against this changed field.
So I need to know if there's a way I can convert the table, or if there's another way to Force Access 2013 into an offline mode.
Thanks,
Dennis
I have a problem with a DB I started work on a couple of years ago in Access 2010. I fired it up last week and now I'm getting an "unrecognized database format" error when I try and open the front end.
I left this project sat after the company lost interest in finishing it. Since then I worked on another project on the same dev machine which required me to install Access 2007. I had both 2010 and 2007 installed at the same time and I remember opening the now problematic db to take some snippets from some code in there for use in the other project. Im pretty sure I only opened it in 2010 at that time.
Now the company has shown interest again I need to finish the project.
Ive tried uninstalling all instances of Office and the Access Database Engine (I needed this to test the 2007 project) running a clean up and putting a fresh install of 2010 back, but Im still getting the same error. Ive tried importing the objects from the accdb file into a new db but access still throws the unrecognized database format error. The same error is given if I try to decompile as well.
Today Ive tried uninstalling office 2010 and putting a clean 2007 install to see if I can open/decompile/import from the older db under that version of access but Im faced with the same error.
The file server where I backed up to has been rebuilt since I worked on the original project and I thought that the accdb file might have been corrupted during this process as Im pulling it from the old vhd. I've also pulled backups from several locations and all the files give me the same error. Ive even tried running them on one of the clients where I know it used to work and has not been had office tampered with since I was last looking at this and still I get the same error. I know that I had compact and repair on exit set on the front end and Im wondering if I managed to inadvertently use 2007 and the last time I opened it and royally screwed it up unknowingly creating a little surprise for me here two years down the track!
I have even tried installing an "Access Recovery Toolbox" util to see what that could make of the file, and it pulls absolutely nothing back in the report.
I have a much older version of the db which works on my dev machine but Im at a massive loss if I have to start work from this version as I made some very significant changes between these versions including changes to the back end table structure.
Any light anyone can shine, even if it just means getting the VBA out into a text file would be really helpful!!
TIA
Have you tried creating a new DB and pulling in the tables, forms, etc from the bad DB? I would recommend doing it incrementally and checking the new DB after each import. IE just bring in the tables and then see if they are healthy before moving on.
Does anyone know of a way to make Excel 2003 push changes to a MySQL database?
Currently, we're using Excel 2003 for keeping track of a big bunch of interconnected equipment (actually, an entire electric power distribution system with all the hoo-ha's that hang off it.) Quite frankly, using a spreadsheet for this sucks and I'm sick of it, so I want to convert it over to a Real Database like MySQL.
The gotchas are:
The people who are using it aren't overly computer savvy. Using Excel to edit the MySQL database saves them the pain of learning something new.
We don't have a license for MS Access, or I'd use that instead.
I don't have the time to roll my own custom app.
I've already grabbed the MySQL ODBC driver and installed it, and importing data from MySQL to Excel is a breeze; but there's no obvious way to to the reverse, and push changes in Excel back to MySQL.
There are (at least) two possible approaches here.
Use a MySQL database and, as you suggested, use the ODBC driver to update the database. Using ActiveX Data Objects (ADO) can let you accomplish this. See here for details
Alternatively, you can create a Microsoft JET database and use that instead of MySQL. This can be done using ADOX to create the database - see here - and then ADO to update it.
Both ADO and ADOX are available on my standard Office 2003 install (which does not include Access) so hopefully your system will have them too.
As a fallback if these aren't available, you could look at Data Access Objects (DAO) - the predecessor to ADO - but ADO seems a lot easier to use to me. DAO details are here
#Roland Bourman's comment (which would deserve to be an answer in itself) is a very interesting approach. If you're not a VB expert, you could mabye even do the pull/push outside of Excel on script level, pulling the data from mySQL into an excel sheet before opening Excel (easy) and writing it back after closing it. This could be done using a variety of tools.