isladogs
Access MVP / VIP
- Local time
- Today, 12:43
- Joined
- Jan 14, 2017
- Messages
- 19,383
@Pat Hartman
I never use the MS templates for all the same reasons.
Apart from poor naming & embedded/saved macros, they also use MVFs / attachment fields, table level lookups etc...etc.
Apart from all that I suppose, it could be said they aren't too bad
The built-in application parts are equally poor. Also, personally I dislike layout guides
So all of the above has given both features a bad name.
However, the point of the article is that you can use them for your own purposes and save a lot of time.
Sure, you can import objects from one db to another . . . I've been doing that for years ... but as I re-use certain code, tables, forms & reports in many if not all of my apps, these two features can be a much more powerful alternative
You mentioned A2007.
I've just re-checked: although that had a limited set of table templates, Application Parts weren't added until A2010 and Templates were made easier to utilise in the same version
I never use the MS templates for all the same reasons.
Apart from poor naming & embedded/saved macros, they also use MVFs / attachment fields, table level lookups etc...etc.
Apart from all that I suppose, it could be said they aren't too bad
The built-in application parts are equally poor. Also, personally I dislike layout guides
So all of the above has given both features a bad name.
However, the point of the article is that you can use them for your own purposes and save a lot of time.
Sure, you can import objects from one db to another . . . I've been doing that for years ... but as I re-use certain code, tables, forms & reports in many if not all of my apps, these two features can be a much more powerful alternative
You mentioned A2007.
I've just re-checked: although that had a limited set of table templates, Application Parts weren't added until A2010 and Templates were made easier to utilise in the same version
Last edited: