But there are many legitimate uses for your application to use VBA to import/export data. You would also be blocking all of these legitimate uses.
If you truly require that degree of security, you should use SQL server as a backend, and apply security there.
This has been one of the really strong features of access, that when you do imports, you get the import errors table, and when you try to copy-paste records, you get a paste error table.
This works soooo much better than when you try to do imports through e.g. SSMS, and just get a simple message saying "the import has failed".
It would be nice if this feature could be extended to action querys.
I agree. This limitation really needs to be lifted.
102 votes5 comments · Access (Desktop Application) » External Data Connectivity · Flag idea as inappropriate… · Admin →
I'm not sure. Are you asking for a way to connect your Access desktop app to a PA or flow webservice? Or for a way to connect your Power App to a desktop database file?
You can create an AutoKeys macro that listens for F1, and then provides your custom message instead of the Access help. Works like a charm
This is an ODBC driver issue, not limited to Access, in other words it is the ODBC driver using Identity instead of Scope_identity.
As part of us designing on a new Linked Table Manager dialog, we are incorporating related suggestions and requests made in UserVoice and other forums.
Looking forward to it!
Split returns an array, it doesn't make sense to me, to expect the query to be able to handle an array.
If you open a new Access instance, you can open a new access database with that instance.
Also if you open a new database from e.g. the explorer window it will also open a new window.
While I might argue that it could be nice to OPTIONALLY turn of whether a user can interfere with it, I've done both table and querie modifications "on-the-fly" in access compiled files running code. I would hate to see that ability go away.
Ah sorry. I use that button to default to use event code, but not, it doesn't use the wizard to create the code for me. When I press the button (in 2010) it takes me to the code window, instead of opening the macro window.
Your in luck!
This feature is already there. I can tell you where to find it in Access 2010.
Select Object Designers
Scroll down a bit to Form/Report Design view
Check the box "Always Use Event Procedures"
Hope that helps
Anders Ebro // TheSmileyCoder
OK, I see your point more clearly now.
I still choose to disagree. I think its a good way of discovering new items being added. Yes, it can also be really annoying, e.g. when forms started to open in layout view as default. I am not arguing that. However they DID leave in the old design view, and the choice to have windowed forms.
But in most cases it make sense (to me anyways), to change the default to the new feature. If they hadn't changed the default form design, I would probably still be making forms with the Access 2000 look.
I don't write this just for arguments sake, but more to give another perspective
I LOVE tabbed documents. Use it all the time. And you have the option of turning it off. I believe that existing databases brought forward are windowed (i.e. original style) by default.