zufuliu
MSAccess SQL
Since dialects came up recently, MSAccess SQL differs among other things in that #....# represents a date (not a comment) and the \ symbol is not an escape character in strings. These two issues severely affect the syntax colouring. Perhaps we can think of other aspects.
I'm thinking it would be good to have a highlighting logic available for this dialect, unless I've missed it.
(I've not tried calling a dialect from the commandline, I think actually it would be good if the /s switch could accept the dialect too, e.g. sql for standard and sql:msaccess for dialect, or something similar.)
Cheers, David
Current lexer highlighting is only implemented for MySQL/MariaDB, there would be menu to select SQL Dialects (issue #31) in the future.
MSAccess has very recently - after decades!! - added in colourised SQL but it is horrendous. It seems to use an html-type instance, which is slow to load and as usual lacks things like ctrl-mouse zoom, and it mangles anything with backslashes in and breaks queries which it then saves broken. Despite a few valued improvements in the newest versions the last efficient, nippy and effective MSAccess was 2002 & 2003 (almost as fast as 2002), everything has descended into sluggishness since then. The nippiest of all was 97 but wasn't naturally unicode like the ones after. But I often generate SQL programmatically, for example dumping all queries to a single SQL file for reviewing, for which Notepad4 is fantastic, but has the shortcoming for the SQL dialect above mentioned. I also launch Notepad4 for viewing/editing SQL and other text and detect when the process has closed, then reading back the edited file (if file's A attribute become set), which is what makes single-file multi-instanced Notepad4 so useful.