Heads up
I am very new to open office base so I suspect I am just missing some ui nuance.
Setup
I have a mysql connection to a simple database. I update the structure in sequalpro then create forms and reports in open office base to same myself all the php code.
Problem
I found that after working with base a little bit that some of my forms suddenly disappeared. The first time it happened I assumed I had forgotten to save or something like that. But after creating another form all the forms suddenly came back. I don't know what triggers the forms disappearing/reappearing but I really need this to be consistent.
Versions
Using open office 4.1.2 on Mac OSX Yosemite 10.10.5
Question
Why are my forms disappearing and reappearing?
Related
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...
I built and successfully split an Access 2013 db. The front end worked fine for months up until I last used it a few months ago. I recently went to open the front end but the Access window was frozen whereby everything (e.g., navigation pane, menus, controls, right click, etc.) was disabled, including the window control buttons to minimize, expand and close. The only way to close the view was to right click the Access icon in the task bar or 'ctrl-alt-delete' to open task manager and force close the application. I was met w/ similar results when attempting to open other versions of the linked front end; however, I can successfully open the back end and other Access db files that don't contain linked tables. When I get the 'frozen' screen I can see my linked tables and other db objects in the navigation pane, but the pop-up login form does not display and the entire window behaves like it is inactive, similar to how it behaves when selecting items behind the active login form.
To confuse matters even worse, I have one user (User 1) who has the same user permissions as me who does not experience any of the problems I described above and can work within the front end as expected; in fact, he and I are the only active users as we are still in the developmental phase of our project. One other layer of complexity, he tried to open the file w/ his network profile from my computer and ran into the same problems. We have one other user who we've since tested this problem with and she experiences the same issues as me on both her laptop and PC.
So, I thought maybe it had to do with the 32-bit version I unknowingly had installed when my OS was re-installed last month since User 1 had the 64-bit version which could explain why he couldn't open from my computer. BUT, I still experienced the same issues after re-installing the 64-bit version on my computer. I'm at a loss on where/how to proceed from here and my IT guys have done all they can to troubleshoot my problem as they are not familiar w/ Access and aren't much help at this point.
Anyone run into this problem before? Thoughts or possible solutions? Any and all help would be greatly appreciated, thank you.
So, I disabled the code that prompted the login form and I was able to open the file. Based on User 1's experience, we determined that he hadn't installed updates since I was last able to open the file. As a result, we determined that an update I installed was not compatible w/ the aforementioned code resulting in the problems I described in my original post. I will re-create the code that drives the form's login and keep an uncoded version as back-up in case we experience similar issues in future updates so that we can troubleshoot from within the db rather than be locked out as we were.
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.
I have an Access 2003 application that users recently started having issues with the day I put out a new version, one of the screens has a field that has a default value of 'date()', instead of showing the date it shows '#name?'. I'm sure this if some out of synch dll or ocx but not sure which one. Anybody know? I rolled back to a previous version of the application on the users machine and they are fine now (but I'll need to keep pushing out new versions with new functionality soon). So I think some file on my development box got updated just not sure which one.
Thanks
Don
This is typical of a missing reference. If your are using ActiveX controls, you could easily be missing something on the other PCs. Another common cause is using early binding and library references.
Missing references often affect the VBA core functions such as Date.