102 votes5 comments · Access (Desktop Application) » External Data Connectivity · Flag idea as inappropriate… · Admin →
PowerApps and Flow are the future. We seriously need this.
We are designing on a new Linked Table Manager dialog, incorporating suggestions and requests made in UserVoice and other forums.
Guessing ... not specific to Runtime.
On your development system, you are linked to a back end Path say in C:<SomeFolderPath>
On your client's system ... the (server for example) Path is \\<SomeWorkGroup>\<SomeFolderPath>\
Currently with the LTM or otherwise, you cannot link to backend/tables in a non-existent path. So, when deployed at a client's site ... some sort of relinking code or manual relinking code is required.
(most all developers have some sort of auto relinking code)
With this suggestion, prior to deployment at a client's site ...you would be able to link to a non-existent folder path, such that when the front end is deployed at the client site, no relinking is necessary and the app is plug n play.
I think that is the idea of the suggestion.
I'm sure there are numerous ways this could be implemented. And overall ... it fits into the need to seriously revamp the Linked Table Manager in general.
Access is far from dying. Not sure what your concern is in this regard?
No sadly. There are data macros available in Access tables ... to use within Access tables.
So for example, you can easily create an Audit Trail scenario now by just using Data Macros. However, there is no connection to SQL Server per se in that regard :-(
re #1 ... I assume you mean data macros different than the Data Macros at the Table level that started in A2010 ?
So ... you don't feel 22" wide is wide enough ?
You can trap for this error (and similar errors) in the Form Error Event - which this particular error is rendered.
I suggest using Datasheet Views - which are significantly more flexible than Continuous Forms .. which I quit using at least 12 years ago.
Maybe just go back to MS DOS ?
"bit Intellisense" >> but Intellisense
I get it for sure, bit Intellisense is a relatively new feature in the Query Designer ... and the Intellisense goes several levels deep - amazing - like reference a control on a subform of a main form.
If I had to choose between the two, I would definitely choose Intellisense.
Definitely a good idea.
This would be a great enhancement.
It might be wise to ask 'why' that change was made?
And sorry, but the Nav Pane is one of the best feature enhancements of all time in Access. Starting with the Search bar, not to mention being able to select multiple objects even across different object types (Forms, Tables, etc) to delete or what not. Did I mention that Groups are actually useful now. And a couple 100 other things. Long live the Nav Pane. I think that most people (Pat?) have not bothered to investigate the new features. The only thing I find annoying is the Description column disappeared.
And BTW .. the Access Product Team IS listening, trust me. But there are limited resources and not everything can be implemented. Not to mention the code base is 24 years old ... so making certain changes would be very risky. And there is virtually no one left from the early days of Access.
Attention Access Team. Respectfully, it's absolutely maddening to have fixed size dialog boxes - still - in the year 2016. Almost ALL other professional applications have sizable dialog boxes. And of course, it's not just Access .. but across the Microsoft platforms. This is sooooooo antiquated.
Non sizable dialog boxes are absolutely maddening . All other professional applications have sizable dialog boxes. This is 2015 not 1994.
Seems like a cool idea. Just an FYI only ... note that you can Right Click over any table in the Relationship Window and immediately open the Table in Design View. Not a replacement for your idea, but just so you are aware in case you are not.
"You can add control dynamically through VBA using the CreateControl Method"
Just an FYI ... whereas this does work in 'live mode' (per the one comment), it will NOT work in and MDE or ACCDE ... since you cannot make design changes to a Form in a 'DE'. Keep this in mind.
I'm not sure Anchoring does everything a full blown resizing function would (or should) do.
For example ... Peters Shrinker Stretcher does it all ... and I've used it several times. AMAZING. Forms, subforms, subforms with subforms ... all controls ... everything.
Download the free, 100% functional demo and check it out, as well his other tools.