So I was trying to create a user and password for a particular database in Mysql Workbench, but the Schema Privileges does not seem to display completely for me to work on. Any reasons as to why?
It is a bug (glitch), and already reported to MySql team. I had the same problem, by the time it get fixed; Please use it by "restore down" window mode.
When defining a user the "Schema Privileges" tab is non-functional when the Workbench window is in fullscreen mode (which is the default mode on start-up). Only the "Schema" column is shown in the embedded window and the "revoke all privileges", "delete entry", and "add entry" buttons are missing.
The problem goes away when the "restore down" window button is clicked and does NOT re-appear when the Workbench window is returned to fullscreen.
Glitch
Without Glitch
So on the Mac, and this may be different on Windows, the devs have gone minimalist with the interface in Workbench. So there are hidden controls where you have to move your mouse around until the cursor changes, only then can you see the control. Here you can see that the Schema Privileges section on the Mac doesn't show at all until you drag it up. Likely in Windows you would need to drag that right side to the right to increase the viewing area.
Here they are collapsed:
When I drag up on the hidden control they show up again:
I have found the solution :
In C:\Users[you]\AppData\Roaming\MySQL\Workbench\cache, delete the XXX.columns_widths file where XXX is your connection name.
J-Luc
I had this same problem after my Windows 10 crashed due to a power outage during a Windows update. Win10 basically installed a fresh copy of itself but kept my user directory, which included my original %AppData% settings from mysql. I basically blew away the entire contents of C:\Users{my user name}\AppData\Roaming\MySQL\Workbench ... after which things started working properly again.
Clearing AppData didn't work for me. It was bugging me on Windows 10 Workbench 6.3.x.
Solution was to uninstall it and re-install 6.2.5, by clicking "Previous GA version" from download page. It was back to the old, black Home screen, my connections were still there from 6.3.x and the UI glitch is gone.
Related
we are using Microsfot Access 2013 on Windows 10 system and when we open the application to run a query which outputs data to a table, the button which creates the popup form / window to enter the date range somehow just disappears.
Other systems using the same tool do not have this problem, and the tool was working just fine yesterday.
Any one have an ideas?
If the database was used on a multi-monitor setup it's possible the forms position has been stored "off screen".
Open the pop up in design view (It should appear!), and set AutoCentre property to true, and resave the pop up. It then should always appear in the middle of the current screen.
I think I may have completely messed up my application here! I was foolishly playing around with some settings in the File > Options menu for Access and turned a couple of things off. It said I needed to close and re-open, so I did, and now I can't do or edit anything. How do I revert back?
Right clicking the window doesn't help, I tried using Alt+F11 to switch to VBA but that doesn't help. I disabled the close button on the form already, so can't click the X.
I have spent hours working on this, and feel like I may have to start again.
Any ideas how I can get back into my file?
When you double click on the file; hold down SHIFT key.
When you open a database while holding down the SHIFT key, many of the options that you set on the Current Database page of the Access Options dialog box are bypassed.
Once you have bypassed these settings you can access your ribbons and options to reset your settings.
I decided to try Windows 10, but having problem to make terminal works inside WebStorm/PhpStorm.
When I open terminal, sometimes it's completely black, sometimes it loads the project folder but I cannot type there. There is a way to run it in the external window, but I just got accustomed to work with console like internal window inside WebStorm/PhpStorm...
I tried cmd, Power Shell - same results.
Any ideas?
Workaround: Terminal works fine in Windows 10 if you use legacy console.
To do so, open a command prompt window, right click on the title, then select Properties. At the bottom, check "Use legacy console". Confirm the dialog window and go back to WebStorm to launch a new terminal. It should work.
In any case, this is the ticket to watch after:
https://youtrack.jetbrains.com/issue/IDEA-143300 -- star/vote/comment to get notified on progress.
UPDATE:
This issue has now been resolved -- the fix will arrive in next major version -- PhpStorm v10/WebStorm v11 (or whatever that version will be as long as it's based on 142.xx branch or newer).
UPDATE:
For those who have problems with right clicking and finding "Properties" menu entry:
Just for the record: I have confirmation from JetBrains that it will be fixed (i.e. work with non-legacy mode) in WebStorm 11 which is scheduled for the beginning of November. In the EAP version it should already work.
I suspect this is a simple/silly/trivial problem - but I've spent ages without finding a solution.
I have a vanilla MediaWiki instance - a few months old - on an Ubuntu server recently upgraded to 14.04. There is a single "user" - this user is in the "administrator" and "bureaucrat" groups when I look at the "User rights management" special page.
I need to rename some pages... I understand, from the FAQ, that I need to use the "Move" tab - and know that this tab is only shown for logged-in users. (The wiki is configured not to require users to be logged in to do edits.... I don't really need/want any access control.)
Even when logged in, I don't see a "Move" tab... Please can someone give me a hint - What am I doing wrong?
In the Vector skin, the Move tab is by default collapsed into a More tab. Depending on the version of your installation, that might only be an easy-to-overlook triangle:
^^^^
We have an error that we can't seem to find and don't have the need/resources to try and track it down. What we do need to do is just keep the freaking "Please tell Microsoft about this problem" dialog boxes from cluttering up the server.
It is from an MS-Access error (we think) but I can't find where Access is installed (I don't think it is); there is no MS Office directory on any of the drives.
If we could just stop the dialog boxes from appearing that would be great.
Thanks.
Spec: Window Server 2003 sp2
From http://www.codeproject.com/KB/exception/UnhandledExceptionClass.aspx:
If you also want to disable the Windows “Send Error Report” dialog on your computer, right-click on the “My Computer” icon, select “Properties”, switch to the “Advanced” tab, and click on the “Error Reporting” button. In the Options dialog, select the “Disable error reporting” radio button:
Compare also http://www.codeproject.com/KB/exception/ExceptionHandling.aspx for general .NET Exception Handling sanity.
I don't think you realize jusy how serious this error might be. These errors pop up under severe conditions like buffer overflows, null pointer dereferences, division by zero errors, etc. Given that you mentioned that this runs on a server, you potentially (depending on your situation) have a network facing, easily exploitable program!
As others have suggested, you can turn off error-reporting system wide, or you can use the SetErrorMode API to disable it for just your application, but again I would strongly advise to investigate and fix the problem at its root!
Well, I would try and figure out what application is using Access. Not knowing what is running is a real issue, especially when it is having unhandled exceptions!
As far as just disabling?
Try:
Right click 'My Computer'
left click 'Properties'
left click 'Advanced' tab
left click 'Error Reporting' (near bottom)
left click 'Disable error reporting'
It's called the Windows Error Reporting Dialog. You can disable it by following these instructions:
http://www.windowsnetworking.com/articles_tutorials/Disable-Error-Reporting-Windows-XP-Server-2003.html
However, I would be concerned with why you are getting those error messages. You are just concealing a problem which could be very bad.
Since I see three different people posted instructions on how to disable the dialog on their own machine, I'll post this again as an answer instead of just a comment:
They don't want to do that on their customer's machines, because that will disable any application from using the dialog. They just want to prevent it from coming up for their application.
It's not concealing anything, if a program crashes windows will still tell you. The difference is that it won't compile a core dump and try to send it to microsoft for you. It's very useful to disable this garbage.
When working in .net, you can catch all unhandled exceptions (which is what causes this message). But I'm not aware of a way to do the same in Access.
http://devcity.net/Articles/60/1/unhandled_exceptions.aspx