I am getting an issue running a Microsot Access Database (.accdb).
The application was made by a German colleague (using Ms Access in German language of course), now after I copied into my machine (I am using Ms Access in English language) I am getting the following prompts: "Enter parameters values" (see screenshot).
It is clear that the program is looking for values like "Auswahl_MinDate" , in the query I replaced all the code from "Formulare" to "Forms" - it has worked however it is still looking for 2 more values starting with Formulare.
I tried to check all the Forms, Query 1 by 1 however could not find significant results.
For example the 'Auswahl_MinDate' is a date picker control, hence I deleted and recreated but still...
Where else this 'Forumulare' could be set ?
Thanks.
If you can't find it in query parameters or SQL, it may be hidden in control properties.
Your best bet is probably a global search tool.
Search For Text (Free, open source)
https://www.utteraccess.com/topics/1992076
The 2nd post has an .accdb for Access 2016 (the original is .mdb)
You need to register to download the file.
Still available for download, but unfortunately not for purchase is Find and Replace by Rick Fisher (Shareware)
http://www.rickworld.com/download.html
V 9.00k also works for Access 2016 / 365.
I don't remember if it stops working after 30 days or just keeps nagging.
Related
I linked a SharePoint list to an Access table to create a more functional UI. I created queries to show the information various groups would have to update, then forms for them to use to make updates. As far as I can tell, everything worked as expected while it was on my hard drive. When I uploaded it to SharePoint for general use, it started giving a "could not find field" error seemingly randomly when users would try to update certain records.
I use SharePoint 2016, Access 2016, and Windows 10.
What I've tried:
Comparing data types of Access/SharePoint fields
Refreshing the table link Recreating from scratch
Unchecking "Use the cache format that is compatible with Microsoft Access 2010 and later"
Making fields required in SharePoint also required in Access
Adding user info table due to created by/modified by fields (see below - not
sure if my relationships should be changed? Does the HistoricalData table need a relationship to UserInfo?)
Does anyone have any ideas as to what could be going wrong?
Relationships View
I also posted a variation on this question here.
Go To
File --> Options --> Current Database --> Caching Web Service and
SharePoint tables ........
Uncheck the box next to “Use the cache format that is compatible
with Microsoft Access ........”
When I run a report - using either a simple query, complex (query builder) or via DoCmd.OpenReport(.....) then the report populates fine.
However I wish to run the application with the forms etc as Pop-ups, and the application minimised, or hidden - otherwise users will just access the database that way - and miss the logic that is integrated etc.
So I am Minimising the application using apiShowWindow(hWndAccessApp, SW_SHOWMINIMIZED)
However in this case, when I run the same reports as before - there is no data, just a blank report - not even the header!
Any ideas?
Julie
Not sure why it works, or needs to be the case, but setting windows mode to Icon (via the macro and/or the doCmd.OpenForm () command in VBA) works.
Nor can I claim the credit - Thanks to Wayne G Dunn
Recently, not since three or four days, we have been facing an issue when trying to compare within visual studio 2013 on a database project. The compare screen loads up but I'm not able to select source or target. Nothing happens if I click the target combo and select "Select target...". Sa for source. I tried using the menu bar's "SQL" with the compare screen open and tries "Select Target" from there only to be presented with a error message: An item with the same key has already been added. Same behaviour on source.
We tried reading the logs of visual studio, searched all over internet and got suggestion to update SSDT but thats not really an option as the search results are from 2011/2012 and those update don't exists or apply to VS2013.
We did more testing:
A stand-alone new solution with new DB projects works fine
Loading our DB project directly into a new solution works fine
Our full solution 'A' fails.
Other of our solutions 'B' and 'C' also fails
Couldn't find anything in the solution file that could prevent comparing.
Anyone facing/had similar issues?
I had the same problem in VS2010. Solved after renaming projects with the same name which were located in different virtual solution folders.
Looks like "New Schema Comparison" form doesn't respect solution folders structure when fills "Project" combobox.
I made Access Form which was working fine in Access 2013 and Access 2007 until I add some new features(I don't remember what) to it.
After adding them, it keeps giving me error "Unrecognize file format" when I try to run it in Access 2007. Meanwhile it runs fine in Access 2013.
I want to ask if there exists some software to convert Access 2013 file to Access 2007? Or is there any way make it compatible to 2003? When I Save As 2003 file it don't because of some added features.
Please help!
You could try using Access' Application.SaveAsText in 2013 and Application.LoadFromText in 2003.
Even if this doesn't work directly, if you have an older version that does work, you could compare the differences between the text files the two versions of Access produce, as SaveAsText produces (for the most part) human readable output; the only unreadable parts are typically images.
I've had this happen to me during development on A2010 and deployment on A2007. The possibilities are explained on this page. It is likely that you added an Empty Cell control to a form that had a VBA module (or added a module to a form with an Empty Cell control). I did this unknowingly by inserting a row into the AutoHeader that is created in forms by the Form Wizard.
Follow the steps at the bottom row of Table 2 to rectify this.
MS Access 2010, Win 7 on a regular formI didn't intentionally place any ActiveX or OLE things.. not even sure what they are. But anyways, whenever I put something in the code of a particular form, it says "The Expression XXXXX you entered as the event property setting produced the following error: A problem occured while MyDB was communicating with the OLE server or Active X Control
Huh? No matter what I put in the form's code, this happens. I had an empty Form_Current() ONLY which still tripped this. There's a lot of formatting and work into the form, I'd rather not scrap it.. If I leave the code window completely empty (only Option Compare Database), it does not trip the error; however then my form is useless.
I've seen things about this being a language issue, but my other forms (running the same code techniques and most of the same code) are fine and it's an english Access with an english language PC. Ideas?
Code setting off the error:
Private Sub Form_Current()
End Sub
Seriously.
I faced the same problem and I tried many things, the only (and fastest) solution that worked is to do the following:
1) Close the form that is causing the error.
2) Rename this form.
3) Duplicate it: Copy, then Paste, you will be prompted to set a name for the new form. Give it the original name.
4) Delete the original form that was causing the error.
5) Open the pasted form and it will work OK.
This solution worked fine with my database...
Regards...
Check for missing references. Make a back-up, decompile, compact & repair and if that does not work, copy everything to a new db ( http://www.granite.ab.ca/access/corruptmdbs.htm ) You may have to skip copying the problem form. Sometimes it is worth creating a new form, selecting all the controls from the old form and pasting into the new form.
you can change the language setting to have a try, the steps are as follow:
1、Open window command ,run "intl.cpl"
2、choose the Administrative item ,change the system locale settings.
Hope that can help you.
I have run into this problem many times. The error statement is horrible as it provides basically no useful information. I have found that Abu Hassan's solution typically works best (duplicate the form and delete the original) but that did not work for me on one occasion, where I had to delete an import statement that I had recently added:
imports system.collections
Once I deleted that import statement everything worked again. So if duplicating the form doesn't work then try undoing something you recently did. It could be this import statement or one similar to it.
Very strange error, that sometimes occurs in my databases too.
It seems to go wrong mostly on UNBOUND FORMS (unbound forms have no RECORDSOURCE).
What I have done recently is :
temporarily define "some" table (e.g. a config table with just one record) as the RecordSource,
compile the program (Note that this usually goes OK, even before the fix!)
Save the form.
Open the form. This should work fine now!
Delete the RecordSource, recompile and save again.
Most of the time, my forms work fine again after that.
as my experience some of errors because you use your local language in VBA statement
so you must adjust your local language as language of system from control banal >> language or region>>administrative>>change system local then select your local languages
or find the word was not English in vba and retype it by English