david savage
My feedback
-
1 votedavid savage
shared this idea
·
-
25 votesdavid savage
supported this idea
·
-
1 votedavid savage
shared this idea
·
-
1 votedavid savage
shared this idea
·
-
6 votesdavid savage
supported this idea
·
-
4 votesdavid savage
supported this idea
·
-
2 votesdavid savage
shared this idea
·
-
8 votesdavid savage
shared this idea
·
-
4 votesdavid savage
shared this idea
·
-
49 votesdavid savage
supported this idea
·
-
14 votesdavid savage
supported this idea
·
-
34 votes
An error occurred while saving the comment david savage
supported this idea
·
-
50 votes4 comments · Access (Desktop Application) » External Data Connectivity · Flag idea as inappropriate… · Admin →david savage
supported this idea
·
-
1 vote
An error occurred while saving the comment david savage
commented
As an addition to what I just posted, I update the 'Application Title' using VBA code under a With statement:
db.Properties!AppTitle = "<name> " & !Ver & "." & !Release & "." & !Mod
.Update
Application.RefreshTitleBarAn error occurred while saving the comment david savage
commented
If you are referring to a version number of a front-end, I had implemented a billing software where I created a table specifically for the version number (Version.Release.Mod), where each is a four digit number, and Mod gets incremented by 1 every time I click a certain button on a form. I have it set to increment the Release by 1 once the Mod reaches 9999. When Release eventually reaches 9999, the Version gets incremented by 1. Anyway, after I update the version number (V.R.M), I update the "Application Title" portion of the Current Database tab after clicking on File-->Options. I hope this helps. This makes it easy for me to know when my users have the most update version of the Front-End.
-
5 votesdavid savage
supported this idea
·
-
32 votesdavid savage
supported this idea
·
If an accde is ran from a system that has Access software installed, then ALL tables. queries, reports, and their designs in the databases should be hidden from all view. It would not be a good thing for end-users to see a list of these tables/queries/reports. If they do, then they'll be curious to what they do by double-clicking on them, which could lead to other issues.