INSERT SQL

[GPGeorge]

That's for VBA. Are they using it for the query editor also?

I do believe that IS for SQL, yes.

 

[isladogs]

It isn't out. Currently slated for Dec 2022 but I expect that date will slip again.

 

[GPGeorge]

It isn't out. Currently slated for Dec 2022 but I expect that date will slip again.

Am I right in thinking it's a SQL editor? These days assumptions tend to betray me more often than not.

 

[isladogs]

I thought it was just for the VBE and not the QBE ...but I may be wrong

 

[GPGeorge]

I thought it was just for the VBE and not the QBE ...but I may be wrong

No both you and Pat think the same. That makes me odd man out.

 

[GPGeorge]

OK, we're back to my "next year in Jerusalem" remark. Promises, promises. instead we'll get some stupid "feature" like mult-value fields so they can push off actually useful improvements.

We have a Dataverse connector in beta testing!

 

[isladogs]

We have a Dataverse connector in beta testing!

Now I know you're winding up Pat!

 

[isladogs]

Pat
We can all agree about that point. You may possibly be interested in my Web article

A Complex Deep Hidden Attachment Mystery

This is the fifth in a series of security challenges. In this case, a problem occurs when deep hiding attachment fields and a solution is provided. But why does the solution work?

www.isladogs.co.uk

 

[GPGeorge]

You're all very funny But the way MS treats Access is very sad

You misspelled "special".

 

[isladogs]

@isladogs - great detective work. You even have the ear of MS being a current MVP. Any chance they're going to fix the problem?

Ha!
The bug has existed ever since the complex field types were added with Access 2007 so only 15 years so far!
That even exceeds issues such as the much more important 'monster bug' which is only 4 years old so far (and on the roadmap to fix) ....

I contacted the Access team about this particular bug last year and they were able to replicate it but stated it was low priority(!) for fixing.
I reminded them in January & got the same response.
To be fair, I agree that its an issue that is very obscure and has probably rarely arisen in all that time.
I suspect it will never be fixed whilst other much more pressing issues still need attention.

However, I've recently been in discussion with ex-MVP Ben Clothier about this issue
As I'm sure you're aware, Ben is far more knowledgeable than almost any other Access developer / MVP.
With some very helpful prompts from Ben, I believe I am very close to fully explaining the problem ... and I already have a solution!

 

[isladogs]

If that's the only typo you found, you need to clean your glasses

Perhaps George has 'special glasses' with rose tinted filters

 

[Minty]

My understanding of the Monaco update was that it was specifically a SQL query editor, that replicated the functionality of SSMS?
But I won't be holding my breath, it's been pushed back twice, as has the new web browser support.