S
Steve Levine
If dbs is a database, what does the value of
dbs.properties("build") mean?
dbs.properties("build") mean?
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.
You should upgrade or use an alternative browser.
A
Albert D. Kallal
In the debug window, you can go:
? application.Build
So, build is a propeirty of the applction object.
Tehre is not a properify of currentdb.Properties("build").
However, the user could likey added a custom property. Often, a developer
can add all kinds of properites.
So, likey, that developer added their own property.
You can go:
Dim prp As Property
Set dbs = CurrentDb
Set prp = dbs.CreateProperty(strPropName, varPropType, varPropValue)
dbs.Properties.Append prp
? application.Build
So, build is a propeirty of the applction object.
Tehre is not a properify of currentdb.Properties("build").
However, the user could likey added a custom property. Often, a developer
can add all kinds of properites.
So, likey, that developer added their own property.
You can go:
Dim prp As Property
Set dbs = CurrentDb
Set prp = dbs.CreateProperty(strPropName, varPropType, varPropValue)
dbs.Properties.Append prp
J
JSand42737
"Albert D. Kallal" said:In the debug window, you can go:
? application.Build
So, build is a propeirty of the applction object.
Tehre is not a properify of currentdb.Properties("build").
However, the user could likey added a custom property. Often, a developer
can add all kinds of properites.
So, likey, that developer added their own property.
You can go:
Dim prp As Property
Set dbs = CurrentDb
Set prp = dbs.CreateProperty(strPropName, varPropType, varPropValue)
dbs.Properties.Append prp
--
Albert D. Kallal (MVP)
Edmonton, Alberta Canada
(e-mail address removed)
http://www.attcanada.net/~kallal.msn
It appears that this is actually a standard property of an Access database.
I've checked in an A97 database, and get 4122, and in an A2K database I get
3822, and in both cases I haven't created this property.
On checking further, it appears that this is part of the version number for
MSAccess.exe. When you check the file peroperties in Windows Explorer, my
version of 97 is 8.0.0.4122, and my version of A2K is 9.0.0.3822.
S
Steve Levine
Albert
I am very appreciative of your taking time to answer my
question.
Based on your answer, I reinvestigated where the build
property to which I referred was located. I did confirm
that:
1. A property of the database and not the application.
To be sure, I verified my VBA subroutine that generated
the report with the information about this property on it.
2. It is not a custom property because I created the
database and it was not one of the custom properties I
added. I did add several custom properties, including my
own version properties (major version, minor version,
patch).
3. It is constant from version to version of my
software. Its value is 702. This is different from what
I thought when I first posted the question. Thus it
appears to be independent of how often one changes the
database (which answers one of my questions about using it
for tracking the application version).
I do need to look at the properties of the application as,
perhaps, I should have placed my versioning properties
there, if they are not already provided for. I shall do
this at my earliest possible convenience.
Again, thanks for your answer. It has been helpful.
sjl
I am very appreciative of your taking time to answer my
question.
Based on your answer, I reinvestigated where the build
property to which I referred was located. I did confirm
that:
1. A property of the database and not the application.
To be sure, I verified my VBA subroutine that generated
the report with the information about this property on it.
2. It is not a custom property because I created the
database and it was not one of the custom properties I
added. I did add several custom properties, including my
own version properties (major version, minor version,
patch).
3. It is constant from version to version of my
software. Its value is 702. This is different from what
I thought when I first posted the question. Thus it
appears to be independent of how often one changes the
database (which answers one of my questions about using it
for tracking the application version).
I do need to look at the properties of the application as,
perhaps, I should have placed my versioning properties
there, if they are not already provided for. I shall do
this at my earliest possible convenience.
Again, thanks for your answer. It has been helpful.
sjl
T
TC
"Build" is a well-known software development term. It means, a particular
working version of the application, produced by assembling files, compiling
& linking them, or doing whatever else is required to get a working version.
For example, I think that microsoft creates a new build of windows, every
night. Each of those would get a new build number. A person might say, "I
found a probklem in build #123".
When a product like Access is released, they would retain the build number
that the product had got up to. In the case of Access, they have stored that
value in a database property. That is the thing you are seeing. An Access
software developer could, if he wanted, maintain his own build number(s),
and store them in a custom property.
HTH,
TC
working version of the application, produced by assembling files, compiling
& linking them, or doing whatever else is required to get a working version.
For example, I think that microsoft creates a new build of windows, every
night. Each of those would get a new build number. A person might say, "I
found a probklem in build #123".
When a product like Access is released, they would retain the build number
that the product had got up to. In the case of Access, they have stored that
value in a database property. That is the thing you are seeing. An Access
software developer could, if he wanted, maintain his own build number(s),
and store them in a custom property.
HTH,
TC
S
Steve Levine
Now for my next question:
Should I be tracking the build of my own application, or is it sufficient to just track what I call, for lack of a better term, the patch number. I would presume the build would iterate each time you change the software whereas the patch would only change when you release the software, e.g. for validation.
The reason why I am asking this is to get a feel for good industry practice in this area. What concerns me about using the build is that, in our regulated environment, where the build number of those versions released to validation would not be sequential, due to my development process, I would be asked to produce or account for the intermediate builds.
What are your thoughts?
sjl
Should I be tracking the build of my own application, or is it sufficient to just track what I call, for lack of a better term, the patch number. I would presume the build would iterate each time you change the software whereas the patch would only change when you release the software, e.g. for validation.
The reason why I am asking this is to get a feel for good industry practice in this area. What concerns me about using the build is that, in our regulated environment, where the build number of those versions released to validation would not be sequential, due to my development process, I would be asked to produce or account for the intermediate builds.
What are your thoughts?
sjl
T
TC
Hi Steve
Hope you're still reading, I've been off the web for a few days.
I can't see any problem releasing a product with non-sequential build
numbers. The build, revision, patch or other numbers are up to you, as
the developer. You give them whatever values you want. One scheme is
the good ol' "major/minor" revision scheme. Revision 2.01, 2.02, 2.03
etc. are minor changes or fixes to Revision 2. Revision 3.01 is the
first version of a new Revision. You would create a new Revision if,
for example, you added a big new feature to your product.
As for having to "account for" any missing numbers, that is easy to
do; not that you would ever be asked to, IMO. You would simply
describe your development methodology, to explain any gaps.
HTH,
TC
Hope you're still reading, I've been off the web for a few days.
I can't see any problem releasing a product with non-sequential build
numbers. The build, revision, patch or other numbers are up to you, as
the developer. You give them whatever values you want. One scheme is
the good ol' "major/minor" revision scheme. Revision 2.01, 2.02, 2.03
etc. are minor changes or fixes to Revision 2. Revision 3.01 is the
first version of a new Revision. You would create a new Revision if,
for example, you added a big new feature to your product.
As for having to "account for" any missing numbers, that is easy to
do; not that you would ever be asked to, IMO. You would simply
describe your development methodology, to explain any gaps.
HTH,
TC
Ask a Question
Want to reply to this thread or ask your own question?
You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.