i have a problem with ms access, this the detail of my problem .
I have accdb 2010 file, and then i am tried to make this database online, so i tried split database.
The file_be, i am tried connect to sharepoint, and its success
The file_fe, i am delete the existing table, and get external data from sharepoint, and its success too
I am tried the application, its success, database on the sharepoint was update too, until this, i have no problem, but the problem is
I was copied File_fe to another computer, office 2010, and office 2013, and then when i am running the app, the application directly force close without information or warning, i have tried on 4 pc, and the problem was same, can you help me guys for my problem ?
i am tried many file, and the problem was same
this the link of samplehttps://drive.google.com/file/d/19821F6ID2jxrBqQRfb9hVhueGXeCfGDb/view?usp=sharing
Related
I have been trying since yesterday and beating my head against a wall trying to obtain data from an excel provider.
I have literally tried everything. I double checked so as to make sure whether my version of excel is 32 bit, it is 32 bit. I even installed the x64 version of Microsoft database engine it still did not change the slightest thing. I have changed Run64BitRuntime to false and delay validation to true. Nothing has changed in the slightest. I have tried using the work book from 2003-2007 and 2007+ to save and then use it still has not changed a single thing. It feels like i am banging my head against the wall after watching countless youtube videos tons of online articles and it still does not seem to work. I would really appreciate some help. The version of Visual Studio i am using is 2019.
SSIS transferring data from Excel could not retrieve table information is the error message i always get after tons of tries.
Have you tried all Excel versions in the Excel Connection Manager? Also, close the Excel workbook while working on the SSIS package.
I have an Access, 2007 – 2016, accdb database on my Toshiba Satellite Pro running Windows 7 32 bit. I am using MS Office 365.
The database that opens at its home page, but any attempt to open a table, form or module brings up this message:
“The database cannot be opened because the VBA project contained in it cannot be read…”
I have 2 backups of this database, but they do the same thing.
I have read several posts on the internet that indicate that the problem can be solved by decompiling the database.
I have tried the VBS Script solution contained in:
How does one decompile and recompile a database application?
However, it does not get to decompile as the same message displays when the .vbs file opens the database.
I have read some other posts that indicate a problem with a VBA7 file, but these refer to Access 2010, so I do not know if they also apply to me. I have VBA7.1 by the way.
Attempts to decompile through the Command Prompt has its own problems that seem to be associated with file names with spaces.
So, I’m stuck. Any help would be much appreciated
I ran into this same error at work, Have you tried shift-clicking and opening? I know that seems obvious, What I did, was I got the DB open in safe mode, and opened up a module in the vba editor, and tried to fight the problematic code, if anything you could delete all your modules after copying them into a notepad.
I also right clicked and restored previous versions from windows, I am not sure if you have tried this when you say you have to back ups, but i was unaware of this fix and i luckily had a version from last week that fixed my issue.
-------------UPDATE-------------
By coincidence I actually found an old post, posted a year ago, by myself with sort of the same problem (totally forgot about it). I suddenly remembered that there was a problem with a reference not being there. Back then I changed everything to late-binding. About a half year ago I created my own COM add-in in C# for my access application, I register this COM object with a script but at this specific user this didn't work. When turning off the specific reference, everything worked again. Conclusion: the bugs / errors were caused by the broken / missing reference...
----------------------------------------------
In the category of weird access problems I have another problem.
In my access 2013 application all the comboboxes don't autocomplete any longer on 1 specific computer. The items are in the list but autocomplete just doesn't work anymore. I have read several other related problems but all those solutions don't work. I have checked / tried the following:
Repaired the database
use the DISTINCT keyword in my rowsource (ANSI-92 issue related)
set the auto-expand property to yes
The weird thing is that other users use the exact same file (it is being copied to local) and at their computers it does work..
The file is of type accde. A week ago I had the same problem and I tried to open the same file but instead of opening the accde version I opened the accdb version at this specific users computer and that seemed to work (autocomplete was working again). This worked for about a week but now it is someway corrupted again (I did change the file however and deployed it again recently so that might have to do something with it). '
Besides the combobox autocomplete problem, the same user has also the problem that one specific form doesn't open any longer (again, at the other users it just opens fine), the error is 2467 and it errors on setting the alloweditions of the subform through code. Though it is just weird that this don't causes errors on the other computers so I suspect it is related to the same 'bug' as with the autocomplete.
Anyone experienced the same problems?
Some additional information:
the accdb file is coded /created in access 2013
the users are opening the accde file in access 2013 runtime, the user where the file seems to be corrupted opens the accdb file in the full version of access 2016 (the temporary solution up till now).
The access application uses SQL Server 2012 as back-end.
Fixed it!
By coincidence I actually found an old post, posted a year ago, by myself with sort of the same problem (totally forgot about it). I suddenly remembered that there was a problem with a reference not being there. Back then I changed everything to late-binding. About a half year ago I created my own COM add-in in C# for my access application, I register this COM object with a script but at this specific user this didn't work. When turning off the specific reference, everything worked again. Conclusion: the bugs / errors were caused by the broken / missing reference...
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.