Gerrit Viehmann
My feedback
-
12 votesGerrit Viehmann
commented
Flickering on conditionally colored controls is very bad in lists (continuous forms) when viewed in an RDP-session if the form is opened whilst the mouse-pointer lingers on that control. Then Access can freeze for minutes if the pointer is not moved away from the conditional control.
This buggy behavior has existed since Windows NT 2000 together with MS Access 2000 and possibly earlier.
Gerrit Viehmann
supported this idea
·
-
1 voteGerrit Viehmann
commented
The import-feature exists for quite some time. I can confirm it for Access 2013 and 365. Them main problem are the error-prone field names the contact-assistant creates. Those should be changed to sensible defaults.
-
4 votesGerrit Viehmann
supported this idea
·
-
9 votesGerrit Viehmann
commented
Try this:
Sub myAccessPerUserSettings()
SetOption "Default Font Name", "Calibri" ' Default is Calibri
SetOption "Default Font Size", 12 ' Default is 9SetOption "Query Design CS Font Name", "Consolas" ' Segoe UI
SetOption "Query Design CS Font Size", 12 ' 9SetOption "Query Design Font Name", "Consolas" ' Segoe UI
SetOption "Query Design Font Size", 12 ' 9
End Sub -
5 votesGerrit Viehmann
supported this idea
·
-
3 votesGerrit Viehmann
commented
While I think the proposed behavior is reasonable, it would break a lot of my current code. So am against it.
-
28 votesGerrit Viehmann
supported this idea
·
-
4 votesGerrit Viehmann
commented
Yes, that's a good idea. The "database window" sidebar is my favorite place for selecting tables and queries too. I can filter there and use drag and drop.
Additionally, I would like an option to open a new query in SQL-text mode.Gerrit Viehmann
supported this idea
·
-
46 votesGerrit Viehmann
supported this idea
·
-
8 votesGerrit Viehmann
supported this idea
·
Gerrit Viehmann
commented
In QBE-mode (design mode) double click on the table/subquery-name rectangle to select all fields (but not *).
In SQL-text-mode try Ctrl-, Ctrl-. for a similar effect like Ctrl-A.
But I agree, the QBE-Editor and SQL-text editors are in need of a serious upgrade.
-
98 votes6 comments · Access (Desktop Application) » External Data Connectivity · Flag idea as inappropriate… · Admin →Gerrit Viehmann
supported this idea
·
-
1 vote0 comments · Access (Desktop Application) » External Data Connectivity · Flag idea as inappropriate… · Admin →Gerrit Viehmann
shared this idea
·
-
95 votes
Hi Piotr, and barcode supporters,
It would be good to hear more about what you’d expect from a native barcode control -
what formats are mostly used? what are other requirements for barcode support?Thanks,
Michal [MSFT]Gerrit Viehmann
commented
At the moment I use QR Code and Code 39. DataMatrix, Code 128 and UPC/EAN may be very useful too.
To create them I use:
1) In Word the (badly documented) DISPLAYBARCODE field (e.g. { DISPLAYBARCODE "1234" QR \s 50 \q 3 }).2) In Access reports I use a function that returns (and creates) a gif-file with the barcode (QR Codes mostly). It uses Zint (https://zint.github.io/) as the barcode generator. It is not reliably fast enough to create the files on the fly, so they have to be created before the report is opened. An inbuilt function or a barcode control that works with reports would be very nice to have.
3) For Code 39 I also use a free font (Code-39-hoch©by Logitogo 2008).
4) I have successfully used the Web control to create QR Codes with open source JavaScript code in an Access-Form. It is quite fast, but unfortunately not usable in reports.
Gerrit Viehmann
supported this idea
·
-
1 voteGerrit Viehmann
commented
Perhaps an "Import/Export Specification" (which can be used with DoCmd.TransferText and with the Import Assistant) is what you need.
Import/Export Specifications are stored in the system tables MSysIMEXSpecs and MSysIMEXColumns. These tables are somewhat obscure, so maybe use the Import Assistant to create one (External Data | Import text file).
In theory all field types from DAO.DatabaseTypeEnum can be imported (dbDate (MSysIMEXColumns.DataType = 8) really means date and time).
You can easily import date/time fields like these below (mix formats with reason):
2018-10-25 07:01:00
2018-10-25 17:03
01-AUG-18 (which evaluates with MSysIMEXSpecs.DateOrder = 5 to: day 18, month 08, year 2001, time 00:00)12h time strings are difficult (some systems won't read them at all):
10/25/18 7:00 PM
10/25/18 7:00 AMISO-Timestamps only work partially. You can change the date delimiter and the time delimiter but not the date/time delimiter. So:
2018-10-25 17:01:09.910 can be imported.
2018-10-25T17:01:00.000 cannot be imported (except as text). -
5 votesGerrit Viehmann
supported this idea
·
-
28 votesGerrit Viehmann
supported this idea
·
-
4 votesGerrit Viehmann
commented
Please consider a permanent Font- and Size- option for the ZOOM-Box (shortcut Shift-F2) too...
Gerrit Viehmann
supported this idea
·
-
6 votesGerrit Viehmann
commented
This will also happen when controls are moved between Header/Footer or Body.
E. g. if a table-layout is applied to controls with events, the event-properties containing "[Event Procedure]" may be cleared.I've also seen this happening without a corresponding action. In those cases all events in a form became unlinked.
Remedy: If you select the whole affected Module and press [Tab] and [Shift]+[Tab] (indent and unindent) the missing "[Event Procedure]"-properties will magically reappear.
Gerrit Viehmann
supported this idea
·
-
46 votesGerrit Viehmann
supported this idea
·
-
11 votesGerrit Viehmann
supported this idea
·
Edit 2020-01-17: No, it can still occur.
Flickering conditionally colored controls in continuous forms and remote desktop sessions seem to be fixed now (2020-01-15), after exactly 20 Years!
Can some confirm if that is the case?