Recent content by isladogs

No. The crucial system tables including MSysObjects/MSysQueries/MSysRelationships & MSysACEs have been read only in all versions since 1.0 You can update certain 'non-crucial' system tables such as MSysIMEXSpecs/MSysIMEXColumns but doing so will not render your database unusable.

The (now deleted) post #18 appeared to be from a spammer who has copied the first line of post #8. If I'm wrong, please justify your action

Most system tables, including MSysObjects are read only. You CANNOT mess them up by using them Actually neither method is completely accurate

Back in post #12, the OP stated Despite this, most of the responses appear to be dealing with eliminating the duplicate horses. That's not what the OP is asking for. He wants to exclude all races where there are duplicate records In post #13, @gemma-the-husky wrote: I agree with that approach

This limit is stated in Access specifications: However, in many cases other limits may be reached before this point In any case, I would never advise anyone creating union queries with so many union clauses. It often indicates design issues

Your original quote suggested there was a limit of 16 or 32 external databases that could be used for linked tables. As previously stated, I do not believe any such limit exists or existed in the past. Happy to be proved wrong if anyone can supply evidence to the contrary. As for the above...

I've only skimmed this thread and I apologise if I'm taking this out of context Access has many specific limits including the number of 'open tables' (4096 / 2048 depending on version), but I don't believe there is (or ever has been) a limit on the number of databases you can connect to. Its...

This article includes links to the download direct from MS https://www.winhelponline.com/blog/how-to-install-office-picture-manager-in-windows-10/?expand_article=1

Just for info, the maximum width of an Access form is 22.75 inches so if you use one large form it won't (quite) fill the screen

The build info on that page is often incorrect. You should use the info next to About Access and add the bitness. No need this time but please do so when you next have a problem

How / why have you managed to stay on v2304? If/when they do fix this you won't get any benefit unless you do update! I don't like the title bar height either but not enough to turn off all updates Please can you state the version number, build and update channel when you do report problems...

That was added to Access 365 plus 2016/2019/2021 in version 2311. Assuming that applies to you, it may be blocked by a custom command bar setting. The fix is to delete the command bar keys as mentioned in post #3 See my article: https://www.isladogs.co.uk/query-sql-view/index.html

I very much doubt it will work as it didn't for me. However, its worth a try. I now know this has been an issue since A2010. It was OK in both A2003 & A2007 I will report it to the Access team

EDITED: Just checked this as it didn't seem right to me. Its still visible in the query context menu from the navigation pane after disabling full menus However, (after rechecking), I agree SQLView in missing from the context menu when a query is open in design view or datasheet view. Suggest...

The video of Adolph's presentation to Access Europe on Wed 1 May is now available on YouTube. Hope others find it useful A significant part of the session explained how and why class modules can be very useful and showed how class module code can be generated automatically using VBA i.e. code...