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.
Related
Creating a new ACCESS application. When I first open ACCESS and create new database it works fine, but is saved on the PC as Database71. If I save it as with a new name to the desk top, or try to rename it it won't open with the following message: WARNING: It is impossible to determine that this content came from a reliable source. I have swept the web and tried several of the solutions, involving the ACCESS Options and the trust center. but none of them work.
Using OFFICE 365 and Windows 10.
jpl458
Sometimes if you get an executable file from the Internet - and I assume that's where your first database is created using Office 365 - then when you copy to your PC it will mark it as unsafe.
If I remember right, you can right-click on the PC database, select properties and then there used to be a button that said "UnBlock" in the bottom right hand corner - or possibly under Advanced.
If that doesn't work, there's a Microsoft Powershell script that will do the same thing.
After you move or rename the file, when you next try to open it, go to the folder where the file is and right click the file and select Open With. In my case there were two ACCESS 2016s. The lower one opened just fine. I have Office 365 so I can't say why there are two entries for 2016. This just works.
Does anyone know if there's a way to set the default font size for the Access 2016 Query Zoom window?
I often use the Zoom window when editing lengthy/complex expressions. I can set the zoom window font size but it only "sticks" for the current session. Next time I start Access, it's back to Tahoma 8pt.
I have no issue with the "Query Design Font" (File → Options → Object Designers → Query Design Font) as it [properly] stays where I set it (Sergoe UI 11) between sessions, but the Zoom window seems to insist upon a smaller font than the query designer.
Maybe I'm missing something but I couldn't find anything applicable online, nor in/around registry keys:
HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Access
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Office\16.0\Access
It's a minor issue but years of frustration with it is starting to add up! Surely there's a setting somewhere so I don't have to change it every time I use Access... Any ideas? Thanks!
[I'm running Access 2016 (local install Version 1711 via Office 365 ProPlus subscription) on Windows 7 Home Premium SP1 64-bit.]
The Zoom box is part of (Office installation path)\ACCWIZ\UTILITY.ACCDA. You can open this file and see the form ZoomForm, but you can't edit it.
Note that the Zoom box is not restricted (or specific) to the query designer - you can use Shift+F2 wherever you can edit (or see) a value.
With help from https://access-programmers.co.uk/forums/showthread.php?t=238660 and https://bytes.com/topic/access/answers/739912-change-default-font-zoom-box :
Set a reference to UTILITY.ACCDA.
In your startup code (called from an AutoExec macro), call this function:
Public Function ZoomBoxSetParams()
' adapt to your preferences
utility.zoom_stFontName = "Consolas"
utility.zoom_iFontSize = 16
End Function
It is not necessary to overwrite the Shift+F2 action with an AutoKeys macro as proposed in the linked threads. You only need to set these variables, and the Zoom box will always use this font.
Note:
This is mainly useful for your development computer. If any of your users use a different version of Access, or the runtime version, the reference to UTILITY.ACCDA will break.
If you are in this situation, you will either have to remove the reference and code before distribution, or perhaps set the reference at runtime if UTILITY.ACCDA is available.
Edit:
An alternative Zoom box is here: http://www.accessmvp.com/TomVanStiphout/ZoomBox.htm
(I haven't tried it)
I'm using an expression for a report connection string but when I upload the report to the report manager (2017 June) and save the credentials in the data source setting the text box that contains the expression gets cleared out.
The same report works fine in SSRS 2014.
I've tried using IE, Chrome and Edge and get the same behaviour.
before save
after save
I had a similar issue in ReportServer 2017; however, if you click the button 'Revert to Default' (a button displayed in the same screen) the Expression based connection string will magically reappear!
Nice feature - if you find it ;-)
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.
I currently have a functioning form that searches through my database by calling a query. What I'm trying to do is turn this into a standalone application where I can simply open a file and only the form opens, running the database on the back-end. I have tried running a macro that opens the form, and I have tried creating a shortcut to my desktop, but nothing has worked.
Does anyone have any suggestions? Anything that will only show the form and the search results would be good (desktop shortcut, HTML file, etc.).
Thanks!
You will need to split your database so that the tables are located in a separate back-end file (which can be kept on a server). These instructions apply to Access 2007 and 2010 but the process is very similar for 2013.
Once this is done, your tables will become linked tables (stored in a separate file) and your front-end .addcb file will only contain queries, forms and reports.
You can control which form opens when the application loads through File -> Options -> Current Database. There are also several other useful controls here for limiting what the user can do; ie.
Hiding the list of database
Hiding the tabs (you will therefore need to create buttons to move between forms)
Hiding the Ribbon and/or status bar
Disabling Layout View
It's safest to change these settings on a copy, so you don't inadvertently lock yourself out; however, by holding down shift when opening the file from within Access, most of these options will be bypassed and you will be able to edit the database / revert these settings should you need to.
In terms of making it a "stand-alone application", it is possible to create a copy that will open without requiring the full version of MS Access on the user's PC (instead using Access Runtime).
I always distribute my front-ends as .accde format (File -> Export ACCDE). The benefits are as follows:
Smaller file size
Optimise memory usage / improves performance
VBA code runs but cannot be viewed or edited
I think what you're looking for is here:
http://office.microsoft.com/en-us/access-help/command-line-switches-for-access-HA010166605.aspx
and
http://office.microsoft.com/en-us/access-help/command-function-HA001228801.aspx
Basic idea, create a macro called AutoExec that checks for a command line argument when opening the database. Setup a shortcut with a command line argument (whatever you decide to name it, I'll use 'lookuponly' as the example.) like this:
"C:\Users\%Username%\Desktop\MyDatabase.mdb" /cmd "lookuponly"
when you double click the shortcut it should auto-run the macro and open your lookup form. Of course under newer versions of access you'll have to set the location of the database as a trusted location or access will attempt to block the database.
http://office.microsoft.com/en-us/access-help/decide-whether-to-trust-a-database-HA010256412.aspx