Problem with query transferts

Anonymous
2025-03-13T17:07:50+00:00

Since the last Office update, when I try to transfer a query from one Access database to another, I get this error message.

It only happens with queries. Does anyone have the same problem and possibly a solution ?

I've never had any problems before and I haven't changed anything in the configuration...

Many thanks!

David

Microsoft 365 and Office | Access | For home | Other

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments
{count} votes
Accepted answer
  1. George Hepworth 21,805 Reputation points Volunteer Moderator
    2025-03-13T22:37:15+00:00

    After some digging and conferring with colleagues, it appears that this is indeed related to the Monaco SQL Editor.

    The MSysSQLComments table is created

    1. When the Monaco SQL editor is enabled in an accdb
      AND
    2. When you first save a query in that accdb, with or without comments in that query's SQL.

    Later, when you export a query from that Monaco-enabled accdb or copy/paste it into an accdb with Monaco SQL editor disabled, the MSysSQLComments table in the target accdb is not available and isn't created because it's not Monaco enabled.

    That's the source of the error message.

    On the plus side, the query is successfully exported and runs as expected inasmuch as the comments table is not relevant in that accdb.

    I think the error message should not be displayed in this scenario, although it is technically accurate.

    If an error message needs to be displayed to indicate that comments on SQL made in the Monaco SQL editor will be lost when exporting to a non-Monaco-enabled accdb, that would be appropriate.

    In short, it's an inappropriately worded warning IMO.

    0 comments No comments

6 additional answers

Sort by: Most helpful
  1. George Hepworth 21,805 Reputation points Volunteer Moderator
    2025-03-13T17:26:27+00:00

    Please indicate which version and build of Office you have installed. "...the last Office update..." is not exact enough.

    Does this happen with ALL queries in ANY accdb? Or just the one query named in the error message?

    That query name starts with "MSys", which indicates a System object. Does this problem impact any query or just queries with that "MSys" prefix?

    Thank you for providing details to help us help you.

    0 comments No comments
  2. George Hepworth 21,805 Reputation points Volunteer Moderator
    2025-03-13T17:29:43+00:00

    Uh, oh. I can replicate the error in M365 .

    "MSysSQLComments" is the name of a system table, not a query. Translating from French (badly) led me astray there. I missed that it's a table name.

    I need to do some more research before commenting, but it could be a bug from that update.

    0 comments No comments
  3. George Hepworth 21,805 Reputation points Volunteer Moderator
    2025-03-13T17:40:25+00:00

    The table in question appears in the source accdb.

    The table in question does not appear in the target accdb, when it fails.

    The table in questions does appear in the target accdb, when it succeeds.

    I'm thinking this might be related to the SQL Monaco Editor. I'll check further.

    Check your accdbs for the existence of this table, MSysSQLComments, in both the source and target where you are trying to copy/paste or export queries.

    0 comments No comments
  4. George Hepworth 21,805 Reputation points Volunteer Moderator
    2025-03-13T18:26:17+00:00

    You might also consider rolling back the Office update to confirm that it is the cause of this problem. https://www.accessforever.org/post/roll-back-to-previous-versions-of-office

    0 comments No comments