Possibly very difficult question *9102008

J

J.Alladien

Good day to all,

I was wondering if there exist code to do the following:
I have a table in my DB with 1 rec with 1 field named "version" with a value
of let's say 2.
Is it possible that everytime the DB gets modified that that field
automatically gets updated to"plus one" F.e. 3 ( 2+1) ,and the next time
4(3+1) etc etc !

The reason being as you can guess that the highest number is the latest
version of my DB in case I forget to input it myself,and I specificly need it
to be in the table because that value is used later on in combination with my
FE_UPDATER!

Hope that I have been clear in my question ,and thanking in advance for the
help!
 
D

Douglas J. Steele

There's no way that I can think of to do that at a table level. You can, of
course, easily put logic in the BeforeUpdate event of a form to do it.
 
T

Tony Toews [MVP]

J.Alladien said:
I was wondering if there exist code to do the following:
I have a table in my DB with 1 rec with 1 field named "version" with a value
of let's say 2.
Is it possible that everytime the DB gets modified that that field
automatically gets updated to"plus one" F.e. 3 ( 2+1) ,and the next time
4(3+1) etc etc !

The reason being as you can guess that the highest number is the latest
version of my DB in case I forget to input it myself,and I specificly need it
to be in the table because that value is used later on in combination with my
FE_UPDATER!
Click to expand...

There is no built in way of automatically updating that number. What
if you are taking two or three days to make a new version of your FE?
How can you figure out a means of updating that number?

I just do it manually.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/
 
L

Larry Linson

When I was distributing updated versions of a Access client application (to
a server DB back end) to nearly 200 users on a LAN, WAN, I used a version
number, but it was unlikely that I, or someone else doing the distribution,
would forget it... it was entered in one step of a multi-step process, which
included sending e-mails to all the users about the new version of the DB,
what errors had been corrected, what enhancements provided, and whether its
use was optional or mandatory. When we first documented the process, it had
Twelve Steps, and that did not trigger a reaction by most of us, until on of
the group called it our "Twelve Step Program" (as in addiction-treatment).
Not to worry, by the time we put it into production, it had gained several
more steps.

I would think that if you are distributing production versions even to a few
users, a defined, documented process would be in order and that would solve
your problem. As someone said, you could include it in event code for some
Control or Form -- if there is a particular Form you would invariably use
(and, perhaps only ever use) when preparing to distribute a new version.

Larry Linson
Microsoft Offfice Access MVP
 
P

pietlinden

12 steps? Hmm... mine has only 2...
1. open bottle.
2. drink.

Wait... that's a different process!
 
T

Tony Toews [MVP]

J

J.Alladien

Thanks a lot for the feedback guys,
Ofcourse I should not be forgetting to input the version# and yes I should
be working with some kind of plan, I just thought of asking it first because
this forum has saved me a lot of "manual" work in the past by doing things
automaticaly by code,which is the reason I always ask if there is a smarter
more efficient way to do things before I implement them myself!
 
J

J.Alladien

Just out of curiosity ,

Was your BE for these 200 users on SQL SERVER, or was the BE just in normal
ACCESS-FORMAT?
 
D

David W. Fenton

Was your BE for these 200 users on SQL SERVER, or was the BE just
in normal ACCESS-FORMAT?
Click to expand...

What's an ACCESS-FORMAT?

Do you mean Jet, isntead? If so, then that's what you should have
asked.
 
L

Larry Linson

J.Alladien said:
Just out of curiosity ,

Was your BE for these 200 users on SQL SERVER, or
was the BE just in normal ACCESS-FORMAT?
Click to expand...

The Access client was in Access 2.0 and the Server was (over the years,
various versions of) Informix, using a third-party ODBC driver. Informix was
the corporate standard database of the company for whose real estate
department this database application was created.

Since then, Informix has been purchased by IBM and I do not know what its
current status may be. The third-party ODBC driver's creator-company was
also bought out by another... and, I'd have to search to find even its "old"
name.

The application was begun earlier and was a "soup stirred by many cooks",
but I worked on it (off and on, as a subcontractor) from 1995 - 2000. As the
result of a merger of two large companies, it was replaced by a web
application that served the same purpose, sometime after 2000 -- though
there were no upgrades to the Access-Informix application after 2000, as far
as I know.

One of the appealing features of Access as a client is that it can work with
_any_ ODBC compliant server database (or, I suppose, if you wish, with any
ODBC-compliant database whether or not it is a "true server").

Larry Linson
Microsoft Office Access MVP
 
L

Larry Linson

David W. Fenton said:
What's an ACCESS-FORMAT?

Do you mean Jet, isntead? If so, then that's what you
should have asked.
Click to expand...

Possibly so, but (mellowed a bit over the years as I aged, I guess) I try to
cut a little slack for people who don't realize that, especially since a lot
of Microsoft documentation refers to "Access database" instead of Jet.
<SIGH>

Larry Linson
Microsoft Office Access MVP
 
D

David W. Fenton

Possibly so, but (mellowed a bit over the years as I aged, I
guess) I try to cut a little slack for people who don't realize
that, especially since a lot of Microsoft documentation refers to
"Access database" instead of Jet.
<SIGH>
Click to expand...

I think it's important to point it out to train people to understand
the distinction. Too many times we get led down the garden path in
this newsgroup because people say they are using an Access database
when they are not using one at all. That annoys the hell out of me.

Of course, as you all know, I'm easily annoyed. ;)
 
Top