Okay, this is kind of odd and it is driving us nuts. I'll outline what is going on as best I can, then I can provide specific details and/or code as folks request it, because I'm not sure what will be needed to suss this out.
I have an access database I have built so our analysts can work within a queue, select records, do whatever research is needed, then either mark the record in question as okay, or fill in some blanks and mark it as needing a dispute (we work in billing).
Basically, the database opens and a hidden form pulls the NT User Name from the local machine, then opens a visible form that queries the database via SQL ODBC to display a list of records with that NT User Name attached to them.
The user can then scroll through the records, select them to get more information, and click a button to mark them as okay, or another to mark them as needing a dispute.
If they click the okay button, it fires off an update query to mark the record as okay. If they click the dispute button, then it opens a third form to show them the line item they are disputing with values from all of the other text fields on the form that they can select from/fill in. On that form there is a button to commit the dispute, which fires off another query to update the values into the same table as the 'okay' button.
So, the issue is, that this all works perfectly on my workhorse machine, and an essentially naked test machine. It also works on another co-worker's machine. However, whenever we try to run it on two other coworkers' machines, everything works just fine, except for any of the queries that attempt to write back to the ODBC connection. All of the read-only stuff works just fine, just not the updates. But the updates work perfectly, and super-fast on my machine, my test rig, and my other co-worker's machine.
We've tried reinstalling the ODBC connection, and the ODBC SQL Drivers.
No go.
We've tried just opening the table in question on the affected machines and making direct edits to the table.
This works if no forms are open in the database, but as soon as we open a form, no update query will run against the table.
So, we tried commenting out all code on all open forms except the docmd.openquery code for the single button we used to test the update query.
No go.
We even built a new form with just a button on it that triggers a new update query that makes only one simple update (Now()) to the table in question.
This runs fine on its own, but times out when run off the button click from the form.
We tried changing the MS Office install on one machine to 'run all from computer' to make sure all necessary components are installed/present.
No go.
We tried installing the ODBC connection both via the normal windows interface, and through the access linked table manager interface.
No go.
We tried installing both 64-bit and 32-bit ODBC connections, both under USER DSN and SYSTEM DSN, and all permutations of one and not the other that we could think of.
No go.
It seems that no update query will write to that table while any form is open, but works just fine with no forms open. But only on these other two machines. Everything works fine on the other three machines we've tested on, whether forms are open or not.
We're kind of at wit's end here and don't know where to go. Google is proving unhelpful, possibly because we just don't know exactly how to search the problem out.
Here's basic technical stuff and I am happy to provide whatever other details, code, queries, etc. that are needed to troubleshoot upon request:
OS: Windows 7 Enterprise 64-bit
Software: MS Office Enterprise 2013 32-bit
ODBC: SQL Server
All users have admin access to their respective machines.
Turns out that the issue here seems to have been an intermittent issue with Access being unable to determine which record to update due to the way we were calling details from a continuous form.
We went back to formula on our UI and built it so there is only ever one record on a form when we try to make changes to records, so there can be no system confusion about what record to update.
Still no clue as to why it was working intermittently, but the new iteration is working now.
Thank you all for your questions and suggestions. :)
Related
I've just run a couple of queries where I forgot to click on the blue 'refresh' button when I launched Oracle SQL Developer.
But I was wondering whether it actually refreshes anyway, when you actually launch it?
Short answer: 'no.'
But first, let's share with folks with the 'blue refresh button' you mention in your question.
What does this button do?
It re-executes the query that the resultset is tied to, in this case
select * from employees
When you restart/re-open SQL Developer it does not even connect to any databases, much less re-execute any queries automatically.
What you might see is a .SQL file re-opened as you had it open when you closed the application from your last session. But no database work will happen until you hit the 'Connect' button.
Disclaimer: I work for Oracle and am the product manager for SQL Developer.
Those are actually two different questions but still they are connected. I am trying to make a script to automate the installation of company PCs for new employees.
An old script used to work fine but as of the 1703 update (or some time prior. No-one really knows), the changes no longer do their job and I cannot seem to find a fix.
The task:
Change the default browser from Edge to Internet Explorer
Set the IE homepage to "https://www.google.com"
Concerning the first problem: I have tried changing the Registry entries at
HKCU:\Software\Microsoft\Shell\Associations\UrlAssociations\http(s)\UserChoice\ No luck there. I have also tried exporting and the setting using DISM but importing them back has proven to be beyond my capabilities (Basically, I ran into this problem: https://social.technet.microsoft.com/Forums/en-US/d5fad871-8f5e-4c74-abaf-627809f8844b/ I cannot programatically change the settings for an existing user)
When facing the second problem, I tried searching the registry for the default site "go.microsoft.com/fwlink/p?LinkId=..." and changing the values. At one startup (After I modiffied the registry key
HKEY_CURRENT_USER\Software\Microsoft\Internet Explorer\Main value "Start Page"), IE displayed a prompt to the user informing them that an external appliation wishes to change the homepage but no change actually occured. And this only happened once (even after I changed the value again to a different site)
A preferred method would be using Powershell but after googling and ripping my hair out for two days straight, I am open to any suggestions. If it makes any difference, it's a 64-bit Windows 10 Pro
I have a very weird situation. Since a few days, the following actions will crash my Windows 10 PC (using Notes R9.01FP8):
I open my Prefs page in the Domino Designer
click on the Source tab
move to a specific location in a table
then I add a Repeat control
I then open the Properties of the Repeat control
to set the data to JavaScript...
and nothing happens, until after a few seconds: BSOD - Unexpected Kernel Mode Trap in either win32kfull.sys or ntoskrnl.exe.
Sometimes, the JavaScipt box is displayed, so I can paste my code, but a short while later the PC still crashes.
I have to say that my PC crashed a lot lately, so I reinstalled Windows and all drivers, so there might be a rotten one that causes all this. According to DriverEasy, all drivers are now up to date. The Event viewer displays a BugCheck event, but nothing relevant (to me anyway).
What I did for further analysis:
I removed Cache.ndk, it didn't help (of course)
in a copy of the XPage, the system crashes when I add the Repeat
ditto, in a different XPage
it seems to work in a different Notes database, on a different XPage
so I created a new database, copied all elements from the original database over, and still the system crashes when I add the Repeat
I'll be doing so more tests, e.g. with an empty database and just one XPage, then adding my Prefs page, or with the same database but then on a server. Actually, one could say I'm kind of lost, and stumbling around in the dark.
My questions to the XPages/Eclipse gurus:
could it be the workspace, and is there any way to reset it?
do you have any suggestions how to get this solved?
Thanks!
The Windows Creator update that MS posted does not seem to fix the Designer crash.
https://grahamacres.wordpress.com/2017/07/10/domino-designer-still-crashes-after-windows-10-creators-update/
In my *.mdb file I have a macro with an action that runs TransferText and gives me an Error Number of 2950 which according to Microsoft means that the document is not trusted, as far as I know it is trusted! It's located in the Trust Center Trusted Locations.
Is there an explanation point next to the Action causing this in the macro whose tooltip reads This action will not be allowed if the database is not Trusted.
I already tried running a compact and repair on it, what could be causing this?
Method 1: Enable the database for the current session
When you use this method, Access 2007 enables the database until you close the database. To enable the database for the current session, follow these steps:
On the Message Bar, click Options.
In the Microsoft Office Security Options dialog box, click Enable this content, and then click OK.
Note You must repeat these steps every time that you open the database.
Check here: https://support.microsoft.com/en-us/kb/931407
The problem can be as simple as not having first established an ODBC connection. I was getting this macro error (2950), and I ended up reading all the support threads, getting nowhere.
Then it struck me to install our ERP client first --which is the front-end for the database I was trying to access ...with Access.
Doing this established an ODBC configuration, so now when I opened my Access file, an ODBC prompt opened up before I even got to any of the functions that were triggering the error. In hindsight, I could have passed on installing the ERP client, and just went to the ODBC settings in Windows, and pointed a connection to the SQL table.
In my case there was a naming conflict. The macro in turn called a VBA function, and I had inadvertently named the function with the same name as the module it was in. They were both named "RobertsReport". Once I changed the name, everything worked as expected.
Tip: As troubleshooting steps, try running the macro solo by double-clicking on it. If you can, copy only the line that generates the error to a new macro to test it by itself, and of course include any preceding commands it may need to run properly. Once I did this it greatly narrowed down the problem until the lightbulb came on over my head.
I am new to SSRS, but have begun migrating our reports to that for my organization. I have 3 reports set up at this time, but have run into a problem. Viewing any of the reports in Report Builder works just fine, but viewing 2 of the 3 in IE (also tried Chrome, Firefox, Opera) is only sporadically successful. Report server is set up on database server, and nothing in the queries being run would tax the system.
I know the security settings are correct, as I can access everything without permissions errors; I know the reports work, as I can freely use them in Report Builder and sometimes from the browser; and I am able to always access one of my three reports through the browser. All have the same security, are in the same folder, and I have gone through the same steps to load each of them. The only difference is that the one that always loads is much simpler than the other two as far as volume of data.
Now, to explain what I actually see when this happens. I set my parameters, and click View Report, and the loading icon pops up for about 1/10th of a second, then disappears. The toolbar does not appear, no data appears, and no error message is present. Every once in a while, it all works perfectly. Most of the time, only 1 of the 3 reports works. I've tried without success to find this issue raised elsewhere -- my apologies if I missed it. Any help on this would be greatly appreciated, thanks in advance.
edit details: SQL Server 2008 R2, on Windows Server 2008 R2, IE9 from a Windows 7 desktop.
If you inspect the SSRS error log it may reveal more of the issue. Sounds like a processing error that was not gracefully handled. Inspect the file \SERVER\\MSRSXX.MSSQLSERVER\Reporting Services\LogFiles and find the current log file to view the exception. Depending on how the client is set up some errors may not show.