Forum Discussion
NEW FEATURES
I agree completely that the VBE is very outdated and needs a significant revamp. Strangely you made no mention of the VBE in your first two posts. The VBE is a common feature across all Office apps and is therefore outside the remit of the Access team.
You misinterpreted my comments about the use of the Access Edge browser control. Although a significant part of its functionality is to provide Web functionality, that is far from all it can do. It can, as stated, display PDF files perfectly. It can also create numerous items such as a treeview, calendar, Kanban board etc by the use of HTML, CSS and Javascript within Access. No need to access the Web for these items.
Finally, as stated, dark themes are already fully available in Access.
During my research, I came across the "Access Explorer" extension, which claims to let you "Explore and edit Microsoft Access databases (.accdb / .mdb) directly from VS Code".
Before I risk running this on any live database, I wanted to ask the community:
How stable is it? Does it work well for daily development?
Is there any risk of database corruption when it saves and injects the edited code back into the .accdb file?
How does it handle form/report class modules (Form_FormName), or is it only reliable for standard modules (.bas)?
If you have used this extension or have a smooth alternative workflow to read/write code directly between VS Code and Access without manual copy-pasting, I would love to hear your thoughts!
Thanks in advance!