Some features would be good to developers:
1) Tabbed SQL Query Windows - allow user to create a query window without binding to a query object (like we do in SQL Server)

2) Format the query field with highlighting, identation, colors and make possible to even resize the font size. .

3) Allow intellisense to get [table].[field] list (in A2013 we have it in Query Designer but no in SQL mode)

4) Split the window in SQL Query and result pane - and make it possible to see result in table or text format (like we have in SQL Server). So, we can click on "execute/run" and see both panels.

Thanks!

SQL is something that I find particularly useful when I am running a database. However, the SQL user interface is very poor in my opinion. It should be more something like the Visual Basic interface, where when you start typing in a formula, then it has a dropdown with all your options and when you select the function from the dropdown, it will show you how to build the formula. For me it becomes very time consuming to have to go online to figure out how the function is built. Also it would be great if it can be colour coded. There should also be more SQL functions that should be made available to the user, like in Microsoft SQL.
Also, being unable to comment directly into the SQL code is something I am finding annoying because I would like to be able to explain to future users what certain pieces of SQL code are for. I would appreciate if you could implement these ideas in the next version of MS Office. Thanks!

On the off chance that your Outlook OST record has turned out to be broken or unparented due to a few reasons like infection assault, Trojan disease, awful server, Low system property, document assemble activity disappointment, equipment crash or bundle disappointment and you wish to ask back your OST record because of your OST document is in this way fundamental to you, at that point don't freeze you'll have the capacity to endeavor our OST record to PST document gadget bundle furthermore as OST to PST for working environment 2007. In the event that you wish to investigate the work strategy of our OST to PST gadget bundle for Outlook OST to PST for working environment 2007 change then you'll have the capacity to exchange free demo adaptation of OST record to PST document gadget bundle for thirty Email. With the help of ravishing OST specialist program you'll decidedly recapture undecipherable OST go into clear condition. OST to PST extractor program swimmingly convert relocate OST to PST with exact organization. PST, EML, enhancing and markup dialect square measure offered distinctive amid which you will reestablish recouped OST document. "Motivate OST to PST Recovery bundle that profoundly filter out of reach and damage OST messages data then you'll have the capacity to spare OST email into working MS standpoint with another configuration like as:- EML/MSG/EMLX/HTML/TXT/DOC/MBOX and viewpoint profile. This bundle has also capacity to help OST record as:- five.0/5.5/2000/2003/2007/2010/2013 related 2016 moreover in light of the fact that it gives you a development decision to separate noteworthy size of recouped PST document upto 5GB.

Read more information and download free demo version here:- https://www.inspiredatacare.com/convert-ost-to-pst.html

In Access I often use the criteria Intellisense/Builder to help me get the vba string to drill down to a deeply nested subform. But Intellisense/Builder gives up about 3 forms in. It would be nice to be able to drill down further with the help of this tool.
I am by no means an expert at Access but over time have created several useful tools over the years, with the help of many Access experts on line. I created a very comprehensive vacation calendar used by over 200 people (tied to an sql back end) for my employer prior to my retirement. So, any tools that help ease the burden are always appreciated.

It would be nice to have more choices than the named colors (Black, Blue, Green, Cyan, Red, Magenta, Yellow, White) in the format code for the Format property of a column in a query.

For instance, we can do this:
[Blue]$ #,##0.00;[Red]$ #,##0.00;-0-

so that positive numbers are blue, negative numbers are red, and zero is black ... but most of the named colors are too bright to show up well.

It would be nice if we could specify an RGB value instead of only the limited color names.

A bonus would be for the Format FUNCTION to also pay attention to color. This would be handy in columns of a combo box or listbox.

thank you

Add a way to refresh the columns listed in tables and queries being shown in the graphical layout of the Query Design View. A right-click, hotkey, or ribbon button would be nice.

This scenario takes place when you are designing a new query that is dependent on other tables and queries. As you are working in Design View, you realize you need to make a change to a dependent table/query such as adding or renaming a column. Without closing the current query, you go and update the dependent object and come back to the open query. Now you want to see the column changes reflected in the tables/queries displayed on your screen.

I am aware of two manual work-arounds to this situation:
1) Close and save the query and re-open it.
2) Switch to SQL View, add a carriage return, and return to Design View.

I don't expect to get flooded with votes on this, but it is a minor annoyance that would help if you could enable it.

The sub query, (SELECT Min(Year) FROM tblInsuredInformation AS i1 WHERE i1.RecordID = tblInsuredInformation.RecordID) AS [First Year], in the query below returns various year values that make sense for the data in the database.

The problem is that tblInsuredInformation doesn't have a Year field. It does have a FirstYear field.

tblPRFPolicies does have a Year field but I have verified that the calculated FirstYear column is not returning either tblInsuredInformation.Year or tblPRFPolicies.FirstYear. It could be returning Year in some records and FirstYear in other records.

If just SELECT Min(Year) FROM tblInsuredInformation is run, MS Access prompts for the value of Year, as it should.

Please fix. I hate it when I have to tell a client their database engine is inaccurate.

SELECT tblPRFPolicies.RecordID AS PolicyRecordID, tblInsuredInformation.RecordID AS InsuredsRecordID, tblPRFPolicies.PolicyNumber, tblPRFPolicies.AIP, tblPRFPolicies.Year, tblPRFPolicies.CancelationDate, tblInsuredInformation.AgentRecordID, tblInsuredInformation.Referral, tblPRFPolicies.StateOfPolicy, tblPRFPolicies.County, tblInsuredInformation.Territory, tblInsuredInformation.eDelivery, tblInsuredInformation.EmailAddress, tblInsuredInformation.Insured, tblInsuredInformation.Contact, tblPRFPolicies.TotalPastureAcres, tblPRFPolicies.TotalNonIrrigatedHayAcres, tblPRFPolicies.TotalIrrigatedHayAcres, tblPRFPolicies.TotalProducerPremium, tblPRFPolicies.TotalGrossPremium, tblPRFPolicies.CommissionRate, [TotalGrossPremium]*[CommissionRate] AS ExpectedComm, tblPRFPolicies.Category, tblPRFPolicies.Commission1, tblPRFPolicies.Commission2, (SELECT Min(Year) FROM tblInsuredInformation AS i1 WHERE i1.RecordID = tblInsuredInformation.RecordID) AS [First Year], p1.FirstPolicyYear, tblInsuredInformation.FirstYear AS ActualFirstYear
FROM (tblInsuredInformation INNER JOIN tblPRFPolicies ON tblInsuredInformation.RecordID = tblPRFPolicies.InsuredsRecordID) INNER JOIN (SELECT PolicyNumber, Min(Year) AS FirstPolicyYear FROM tblPRFPolicies GROUP BY PolicyNumber) AS p1 ON tblPRFPolicies.PolicyNumber = p1.PolicyNumber
WHERE (((tblPRFPolicies.CancelationDate) Is Null));

When a query opens in MS Access designer, quite often the window (query designer form) needs to be re-sized to be larger. When I drag the bottom of the window down, PLEASE keep the results fields selected "portion" (sub-form) the same size! This will result in the top area being enlarged, which gives me more room to view the contents lists of the objects selected (most often they are tables).
Wouldn't it be phenomenal if the table lists would also automatically extend vertically?
I spend a lot of time resizing my query designer windows. (e.g. please automatically enlarge the top while keeping the bottom the same size it was.)