Our office is having a very strange issue with Access 2007.
Long story short - over the past few weeks, half the computers were upgraded to Windows 10, and all of them were upgraded to Office 2013 - except for Access, which we kept at 2007 to keep legacy databases working a little while longer.
All the computers in the office are working perfectly fine under this setup.
Two of them, however, are not displaying some of the Access reports properly. Fields that are not directly linked to a table field and generated on the fly (for example, ControlSource property of the text field something like '=[ThisField] + " and " + [ThatField]') do not show up, and instead display "#Name?" as if it can't connect to the data. However, on the exact same report, there will be fields with the control source directly linked to a field (for example, "MyField" in the query in the report's record source) that will work just fine!
Only two computers in our office are having this problem; the rest display all fields as expected.
Does anyone have any idea why this would be happening? Is it some weird side effect of having Office 2013 and Access 2007 side by side? We do not have Access 2013 installed. It might be worth mentioning that these two computers were purchased around the same time; however, so were two others that are working fine, one of which is on Windows 10 and the other on 7.
Any thoughts or suggestions would be appreciated. Thanks!
Related
I have an old MS Access 2013 .adp project connected to SQL2019 database.
In project I have the forms based on queries from SQL Server. On this forms user can choose an employee ID from the combobox "EmpId" and get rows related to choosed employee .
The code is very simple :
Me.Filter = "[empid]=" & Me.EmpId
Me.FilterOn = True
The problem is that it works fine on 2 computers in the office and doesn't works on third one.
The problem is not in specific form, but on all forms that uses filters.
There is no error messages on that computer, but the filter simply doesn't applied. I see it on
the bottom panel of the form 1 of 8500 rows.
The 3 computers has the same OS WIndows 10 Hebrew and a project is in Hebrew too.
The security setting in all computers is the same "Allow all Macros".
What it can be ? Maybe some Access string settings ? Maybe Windows settings ?
Any help will be very appreciated
Am using MS Access 2016 to develop an application managing images. But some of my users are still using MS Access 2007 on their computers. And the receive the error "unrecognized database format".
So I would like to know if there is any solution for this. Like making my application compatible for previous versions.
I did some researches for days but not satisfied yet.
Need any help, solution or advice please. Thanks
Develop using the lowest version that your application will address, here 2007.
A newer version - 2010 and onwards - will run an older with no problems. However, 2007 is 32-bit only, thus - if you use API calls and some users run Access 64-bit - you must take care of that.
We’ve run into a strange situation migrating our workstations from Windows 7 to Windows 10. One of our migrated apps is based on MS-Access 2010. Via the app’s user interface, users can open various criteria-driven forms & reports. These forms & reports have all worked fine for years. They also work fine on most of our new Windows 10 workstations (some of which are brand new PCs, while others are older PCs upgraded from Windows 7 to Windows 10). But, on 2 of our Windows 10 workstations, one of the criteria-driven reports produces very different results than are produced when the same report is run with the same criteria on any of the other Windows 7 or Windows 10 workstations. This particular report is opened when the user clicks a button on a form, after typing in the desired report criteria. Clicking the button executes a Docmd.openreport reportname, acPreview,, criteria action. The problem is that on these 2 problematic Windows 10 workstations the report returns every record from the database—not just the few records corresponding to the criteria input by the user. It’s as though the report’s query isn’t receiving the criteria, or is receiving them but is ignoring them. We’ve done a lot of unsuccessful experimenting trying to figure out why we get different results on these 2 machines. Can anyone suggest a troubleshooting approach?
I have run into an error with an Access Database created in MS-Access 2003. It's known the Calendar Control was deprecated in Access 2010 but unfortunately we need to keep using it. As a temp fix (until we can change to the date picker) we restored the MSCAL.OCX file on all 2010 users.
The issue:
We have a form to print schedules from a date range (using the calendar control). There is some VBA code to check to dates etc to make sure the range is accurate etc.
Everything works fine in 2003 but in 2010 the dates get selected fine on the form, is passed to the report (a print preview) fine as it displays in the footer BUT the query ignores the date range and prints ALL records (not just the records in the date range).
Is there any way I can step into Print Preview button when clicked to see what's being passed?
Any other ideas?
The issue with the filter not being applied to the report is a known Microsoft issue with certain set ups of Windows 7 and Access 2010. The hotfix found here: http://support.microsoft.com/kb/2596496 solved my problem.
I run Windows 7 64 bit and Office 2010 32 bit, when downloading the hotfix I selected the "x86" platform as that's the 32 bit. If you are using Office 2010 64 bit you should download the "x64" platform.
To find out your office version, open any office product, click File Tab, click Help and it will be on the right under "About Microsoft ".
The only way you can really do that is if your report/query is running some VBA code and put a Stop on the the VBA.
If your query is referencing the fields directly (IMNSHO a bad practice, but I'll work with what we've got) you could change them so they instead reference a VBA function that returns the results of those fields instead. Then you know what it is getting for sure.
There is one more trick that surely worked out for me as a solution, before I came across the accepted answer about hotfix on this thread. Also, because, the hotfix link leads to a valid thread, but there are not downloadable files.
The workaround:
Make a copy of the report file. Use that name in VBA under DoCmd call. Strange how it works, though. Such is the nature of bugs, I guess.
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