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?
Related
Goal: don't display the popup when you remove/delete the SQL document in SQL Server.
Problem: before I downloaded the latest version of SQL Server, it didn't show any popup about status when I removed the SQL document.
When I downloaded the latest version of SQL Server, it suddenly started to display the popup.
It always displays when I remove/delete the SQL document in SQL Server.
How do I remove it?
Thank you!
Uninstalling third-party SQL software permanently removed the "Querying transaction count" popup for me. Details are below.
I downloaded Devart's "SQL Tools" pack. It was one installation file
that installed the 15 separate applications into SQL Server Management Studio. I didn't even open any of the applications yet or activate the free trial (not sure if it activates automatically or not), and ever since have been receiving the "Querying transaction count" popup every time a query window is closed.
This was reducing my productivity, so I spent a few hours researching how to remove this popup so I don't have to click the close button thousands of times. SSMS didn't update, there weren't any options within SSMS or Devart to remove this popup, and there weren't any solutions online other than to create a macro to replicate multiple keyboard strokes to disconnect the connection first and then close the query window.
I ended up uninstalling these 15 applications, and without even needing to restart my PC, the "Querying transaction count" stopped appearing. As an added bonus, the annoying "Buy Devart" PC ads with the too-tiny-to-click-to-close-X that were also popping up every few hours (15+ popup ads a day during Black Friday sale too) stopped appearing as well! Hallelujah! Maybe someone else experiencing this "Querying transaction count" SELECT ##trancount popup installed third-party software like Devart's and just needs to uninstall it.
The software below looks amazing and I'm still interested in trying them out if the free trial didn't automatically activate and expire, but will probably install them one at a time so I can figure out which of the 15 programs is causing this popup. SQL Complete was the only one that I kept and is not causing the popup, so it's 1 of the other 14.
Devart's SQL Tools
SQL Complete (Not Causing Popup)
Source Control
Unit Test
Schema Compare
Data Compare
Data Generator
Documenter
Data Pump
Index Manager
Query Builder
Search
Monitor
Event Profiler
SQL Decryptor
DevOps Automation
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
We are migrating Oracle Forms and Reports from 6i to 12c.
Migrated all .fmb, .rdf, .mmd, .pll from 6i to 12c.
Compiled them to .fmx, .rep, .mmx
Forms are working and being displayed when run via URL (http://localhost:8001/forms/frmservlet?config=form.fmx&userid=userid/pwd#dbname)
I can even view the standalone Reports using the URL in IE (http://hostname:port/reports/rwservlet?userid=userid=userid/pwd#dbname+destype=cache+desformat=html+report=reportname.rdf), but when a report is called in Forms Menu Item (i.e. from the Point 3 URL) won't work.
The error I get for all the reports is - FRM - 41219 - Cannot find report : invalid ID
When migrated the code the reports is changed from RUN_PRODUCT(REPORTS,'reportname',synchronous,runtime,filesystem,'',null); to rp2rro.rp2rro_run_product(REPORTS,'reportname',synchronous,runtime,filesystem,'',null);
Still no luck in displaying the Report in Forms Menu.
Please help. Thanks in advance.
The code you used to get the jobID in version 6 is slightly different in modern versions. You may need to change your code a bit. Check out the latest version of the Forms and Reports Integration Guide https://www.oracle.com/technetwork/developer-tools/forms/documentation/formsreportsintegration-12c-3014203.pdf
I have a report on CRM 2016 which runs perfectly when it is launched with admin user. However, when we launch it with a normal user, all the datasets are displayed perfectly, except for 1 dataset (which was added lately to the report). To note that all the stored procedures used by the datasets (including this new one) have the same security roles on the SQL database. In addition, when I run the report from the visual studio, all the datasets are displayed as well. Can someone please help?
Solved. It was a security role issue on the business unit level
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!