Welcome to SPN

Register and Join the most happening forum of Sikh community & intellectuals from around the world.

Sign Up Now!

Protecting a Database Help

Discussion in 'Information Technology' started by Tom, Jul 28, 2006.

  1. Tom

    Tom
    Expand Collapse
    Guest

    Not sure what group to be in, so I will start here.

    I have an Access 2K database I want to protect against obsolescence. I
    would like to add a macro or query or some VB Code that checks to see the
    last time the database was updated. If it exceeds a certain timeframe, an
    message is displayed and the user is Exited from the database.

    Can someone make some suggestions on how to accomplish this or point me in
    the correct direction?

    TIA!
    ---
    Tom
     
  2. Loading...

    Similar Threads Forum Date
    SALDEF Protecting Sikh American Students Sikh Organisations Mar 17, 2011
    United Sikhs Protecting the Identity of Minorities: A Sikh's Duty Sikh Organisations Jan 22, 2011
    United Sikhs 2010 Global Sikh Civil and Human Rights Conference : Role of Women in Protecting Sikh Identity Sikh Organisations Dec 30, 2010
    United Sikhs Protecting Our Right to Kakaars: UNITED SIKHS Works Across the Country to Address Civil Rights Viola Sikh Organisations Oct 18, 2010
    SALDEF Protecting the Sikh ID in Georgia (SALDEV) Sikh Organisations Aug 20, 2010

  3. kabaka

    kabaka
    Expand Collapse
    Guest

    If by "Updated" you mean a user has added, deleted, or edited a record then
    this ISN'T what you're looking for - someone smarter can hopefully help.



    But assuming that by "Updated" you mean a change to the tables / queries /
    forms / report etc.:

    What mechanism are you using to indicate when your database was last
    updated? For example, in one of my apps I have a "Version" Table which I
    update with a number, datestamp & description every time I make a change to
    the app.

    Given that you have some sort of date you can check against somewhere in
    your db, then you could just call a function such as the following to test
    how recent the db is:

    Function Check_DB_Date()
    dim dbs as database, rst as recordset, datestamp as date
    set dbs = currentdb
    set rst = dbs.openrecordset("Select max([DateStamp]) from [Version]")
    datestamp = rst.fields(0).value

    if datediff("d",datestamp,date())>30 then
    msgbox "The version of the db is older than 30 days. Find a more
    recent copy."
    Application.quit
    else
    msgbox "This version is less than 30 days."
    end if
    rst.close
    set dbs = nothing
    end function

    "Tom" wrote:




    > Not sure what group to be in, so I will start here.
    >
    > I have an Access 2K database I want to protect against obsolescence. I
    > would like to add a macro or query or some VB Code that checks to see the
    > last time the database was updated. If it exceeds a certain timeframe, an
    > message is displayed and the user is Exited from the database.
    >
    > Can someone make some suggestions on how to accomplish this or point me in
    > the correct direction?
    >
    > TIA!
    > ---
    > Tom
    >
    >
     
  4. Jeff Boyce

    Jeff Boyce
    Expand Collapse
    Guest

    Tom

    Your criterion seems to be that if the app is older than (fill in a number),
    it is obsolete. I have at least one Access 2.0 application out there still
    running, still providing the service/functionality that the customer wants.
    Why do you believe that age will "obsolete" your application?

    You could add a constant in a code module and run a procedure on startup
    that checks the value in that constant.

    Regards

    Jeff Boyce
    Microsoft Office/Access MVP


    "Tom" <tom@home.com> wrote in message
    news:iiqd929pplt9gl73vm08ge4j5s39dr9a0u@4ax.com...
    > Not sure what group to be in, so I will start here.
    >
    > I have an Access 2K database I want to protect against obsolescence. I
    > would like to add a macro or query or some VB Code that checks to see the
    > last time the database was updated. If it exceeds a certain timeframe, an
    > message is displayed and the user is Exited from the database.
    >
    > Can someone make some suggestions on how to accomplish this or point me in
    > the correct direction?
    >
    > TIA!
    > ---
    > Tom
    >
     
  5. Tom

    Tom
    Expand Collapse
    Guest

    Jeff,

    The nature of the database is that it interchanges competitive part to my
    company's parts. The interchange info changes daily.

    I also supply this information company wide and the database is not owned
    by the company. I want a method that essentially shuts down the
    functionality of the database after say 60 days, if I am no longer around
    to keep it going (long story).

    Hope this helps!

    Tom



    On Mon, 19 Jun 2006 11:49:51 -0700, "Jeff Boyce" <nonsense@nonsense.com>
    wrote:

    >Tom
    >
    >Your criterion seems to be that if the app is older than (fill in a number),
    >it is obsolete. I have at least one Access 2.0 application out there still
    >running, still providing the service/functionality that the customer wants.
    >Why do you believe that age will "obsolete" your application?
    >
    >You could add a constant in a code module and run a procedure on startup
    >that checks the value in that constant.
    >
    >Regards
    >
    >Jeff Boyce
    >Microsoft Office/Access MVP
    >
    >
    >"Tom" <tom@home.com> wrote in message
    >news:iiqd929pplt9gl73vm08ge4j5s39dr9a0u@4ax.com...
    >> Not sure what group to be in, so I will start here.
    >>
    >> I have an Access 2K database I want to protect against obsolescence. I
    >> would like to add a macro or query or some VB Code that checks to see the
    >> last time the database was updated. If it exceeds a certain timeframe, an
    >> message is displayed and the user is Exited from the database.
    >>
    >> Can someone make some suggestions on how to accomplish this or point me in
    >> the correct direction?
    >>
    >> TIA!
    >> ---
    >> Tom
    >>

    >

    ---
    Tom
     
  6. Tom

    Tom
    Expand Collapse
    Guest

    Kabaka,

    Pls see my reply to Jeff Boyce for more insights.

    Thx

    Tom



    On Mon, 19 Jun 2006 11:43:02 -0700, kabaka
    <kabaka@discussions.microsoft.com> wrote:

    >If by "Updated" you mean a user has added, deleted, or edited a record then
    >this ISN'T what you're looking for - someone smarter can hopefully help.
    >
    >
    >
    >But assuming that by "Updated" you mean a change to the tables / queries /
    >forms / report etc.:
    >
    >What mechanism are you using to indicate when your database was last
    >updated? For example, in one of my apps I have a "Version" Table which I
    >update with a number, datestamp & description every time I make a change to
    >the app.
    >
    >Given that you have some sort of date you can check against somewhere in
    >your db, then you could just call a function such as the following to test
    >how recent the db is:
    >
    >Function Check_DB_Date()
    > dim dbs as database, rst as recordset, datestamp as date
    > set dbs = currentdb
    > set rst = dbs.openrecordset("Select max([DateStamp]) from [Version]")
    > datestamp = rst.fields(0).value
    >
    > if datediff("d",datestamp,date())>30 then
    > msgbox "The version of the db is older than 30 days. Find a more
    >recent copy."
    > Application.quit
    > else
    > msgbox "This version is less than 30 days."
    > end if
    > rst.close
    > set dbs = nothing
    >end function
    >
    >"Tom" wrote:
    >
    >
    >
    >
    >> Not sure what group to be in, so I will start here.
    >>
    >> I have an Access 2K database I want to protect against obsolescence. I
    >> would like to add a macro or query or some VB Code that checks to see the
    >> last time the database was updated. If it exceeds a certain timeframe, an
    >> message is displayed and the user is Exited from the database.
    >>
    >> Can someone make some suggestions on how to accomplish this or point me in
    >> the correct direction?
    >>
    >> TIA!
    >> ---
    >> Tom
    >>
    >>

    ---
    Tom
     
  7. Jeff Boyce

    Jeff Boyce
    Expand Collapse
    Guest

    Tom

    Check my earlier response. It wouldn't be absolute, but it would discourage
    the casual/curious.

    Regards

    Jeff Boyce
    Microsoft Office/Access MVP


    "Tom" <tom@home.com> wrote in message
    news:as7e92536ooniifice5g4nlivajt8e17he@4ax.com...
    > Jeff,
    >
    > The nature of the database is that it interchanges competitive part to my
    > company's parts. The interchange info changes daily.
    >
    > I also supply this information company wide and the database is not owned
    > by the company. I want a method that essentially shuts down the
    > functionality of the database after say 60 days, if I am no longer around
    > to keep it going (long story).
    >
    > Hope this helps!
    >
    > Tom
    >
    >
    >
    > On Mon, 19 Jun 2006 11:49:51 -0700, "Jeff Boyce" <nonsense@nonsense.com>
    > wrote:
    >
    >>Tom
    >>
    >>Your criterion seems to be that if the app is older than (fill in a
    >>number),
    >>it is obsolete. I have at least one Access 2.0 application out there
    >>still
    >>running, still providing the service/functionality that the customer
    >>wants.
    >>Why do you believe that age will "obsolete" your application?
    >>
    >>You could add a constant in a code module and run a procedure on startup
    >>that checks the value in that constant.
    >>
    >>Regards
    >>
    >>Jeff Boyce
    >>Microsoft Office/Access MVP
    >>
    >>
    >>"Tom" <tom@home.com> wrote in message
    >>news:iiqd929pplt9gl73vm08ge4j5s39dr9a0u@4ax.com...
    >>> Not sure what group to be in, so I will start here.
    >>>
    >>> I have an Access 2K database I want to protect against obsolescence. I
    >>> would like to add a macro or query or some VB Code that checks to see
    >>> the
    >>> last time the database was updated. If it exceeds a certain timeframe,
    >>> an
    >>> message is displayed and the user is Exited from the database.
    >>>
    >>> Can someone make some suggestions on how to accomplish this or point me
    >>> in
    >>> the correct direction?
    >>>
    >>> TIA!
    >>> ---
    >>> Tom
    >>>

    >>

    > ---
    > Tom
    >
     
  8. Tom

    Tom
    Expand Collapse
    Guest

    Could you point me in the direction of some code that could be used to
    protect the program if I am not around to keep it updated?

    Thanks!



    On Mon, 19 Jun 2006 16:01:01 -0700, "Jeff Boyce" <nonsense@nonsense.com>
    wrote:

    >Tom
    >
    >Check my earlier response. It wouldn't be absolute, but it would discourage
    >the casual/curious.
    >
    >Regards
    >
    >Jeff Boyce
    >Microsoft Office/Access MVP
    >
    >
    >"Tom" <tom@home.com> wrote in message
    >news:as7e92536ooniifice5g4nlivajt8e17he@4ax.com...
    >> Jeff,
    >>
    >> The nature of the database is that it interchanges competitive part to my
    >> company's parts. The interchange info changes daily.
    >>
    >> I also supply this information company wide and the database is not owned
    >> by the company. I want a method that essentially shuts down the
    >> functionality of the database after say 60 days, if I am no longer around
    >> to keep it going (long story).
    >>
    >> Hope this helps!
    >>
    >> Tom
    >>
    >>
    >>
    >> On Mon, 19 Jun 2006 11:49:51 -0700, "Jeff Boyce" <nonsense@nonsense.com>
    >> wrote:
    >>
    >>>Tom
    >>>
    >>>Your criterion seems to be that if the app is older than (fill in a
    >>>number),
    >>>it is obsolete. I have at least one Access 2.0 application out there
    >>>still
    >>>running, still providing the service/functionality that the customer
    >>>wants.
    >>>Why do you believe that age will "obsolete" your application?
    >>>
    >>>You could add a constant in a code module and run a procedure on startup
    >>>that checks the value in that constant.
    >>>
    >>>Regards
    >>>
    >>>Jeff Boyce
    >>>Microsoft Office/Access MVP
    >>>
    >>>
    >>>"Tom" <tom@home.com> wrote in message
    >>>news:iiqd929pplt9gl73vm08ge4j5s39dr9a0u@4ax.com...
    >>>> Not sure what group to be in, so I will start here.
    >>>>
    >>>> I have an Access 2K database I want to protect against obsolescence. I
    >>>> would like to add a macro or query or some VB Code that checks to see
    >>>> the
    >>>> last time the database was updated. If it exceeds a certain timeframe,
    >>>> an
    >>>> message is displayed and the user is Exited from the database.
    >>>>
    >>>> Can someone make some suggestions on how to accomplish this or point me
    >>>> in
    >>>> the correct direction?
    >>>>
    >>>> TIA!
    >>>> ---
    >>>> Tom
    >>>>
    >>>

    >> ---
    >> Tom
    >>

    >

    ---
    Tom
     
  9. dbahooker@hotmail.com

    dbahooker@hotmail.com
    Expand Collapse
    Guest

    well if you used a real program-- like Access Data Projects for
    example; then you could encrypt a query (stored procedure).

    then it would be impossible for them to steal your work.

    -Aaron


    Tom wrote:
    > Could you point me in the direction of some code that could be used to
    > protect the program if I am not around to keep it updated?
    >
    > Thanks!
    >
    >
    >
    > On Mon, 19 Jun 2006 16:01:01 -0700, "Jeff Boyce" <nonsense@nonsense.com>
    > wrote:
    >
    > >Tom
    > >
    > >Check my earlier response. It wouldn't be absolute, but it would discourage
    > >the casual/curious.
    > >
    > >Regards
    > >
    > >Jeff Boyce
    > >Microsoft Office/Access MVP
    > >
    > >
    > >"Tom" <tom@home.com> wrote in message
    > >news:as7e92536ooniifice5g4nlivajt8e17he@4ax.com...
    > >> Jeff,
    > >>
    > >> The nature of the database is that it interchanges competitive part to my
    > >> company's parts. The interchange info changes daily.
    > >>
    > >> I also supply this information company wide and the database is not owned
    > >> by the company. I want a method that essentially shuts down the
    > >> functionality of the database after say 60 days, if I am no longer around
    > >> to keep it going (long story).
    > >>
    > >> Hope this helps!
    > >>
    > >> Tom
    > >>
    > >>
    > >>
    > >> On Mon, 19 Jun 2006 11:49:51 -0700, "Jeff Boyce" <nonsense@nonsense.com>
    > >> wrote:
    > >>
    > >>>Tom
    > >>>
    > >>>Your criterion seems to be that if the app is older than (fill in a
    > >>>number),
    > >>>it is obsolete. I have at least one Access 2.0 application out there
    > >>>still
    > >>>running, still providing the service/functionality that the customer
    > >>>wants.
    > >>>Why do you believe that age will "obsolete" your application?
    > >>>
    > >>>You could add a constant in a code module and run a procedure on startup
    > >>>that checks the value in that constant.
    > >>>
    > >>>Regards
    > >>>
    > >>>Jeff Boyce
    > >>>Microsoft Office/Access MVP
    > >>>
    > >>>
    > >>>"Tom" <tom@home.com> wrote in message
    > >>>news:iiqd929pplt9gl73vm08ge4j5s39dr9a0u@4ax.com...
    > >>>> Not sure what group to be in, so I will start here.
    > >>>>
    > >>>> I have an Access 2K database I want to protect against obsolescence. I
    > >>>> would like to add a macro or query or some VB Code that checks to see
    > >>>> the
    > >>>> last time the database was updated. If it exceeds a certain timeframe,
    > >>>> an
    > >>>> message is displayed and the user is Exited from the database.
    > >>>>
    > >>>> Can someone make some suggestions on how to accomplish this or point me
    > >>>> in
    > >>>> the correct direction?
    > >>>>
    > >>>> TIA!
    > >>>> ---
    > >>>> Tom
    > >>>>
    > >>>
    > >> ---
    > >> Tom
    > >>

    > >

    > ---
    > Tom
     
  10. Jeff Boyce

    Jeff Boyce
    Expand Collapse
    Guest

    Tom

    Please re-read my earlier response. If you don't need ironclad protection,
    just discouragement for the lookie-loo's, set a constant in a code module
    and write a procedure that checks the date in that constant and bails out if
    the date is past.

    Regards

    Jeff Boyce
    Microsoft Office/Access MVP


    "Tom" <tom@home.com> wrote in message
    news:hssg9295b50r8r6itkrjl9lt0dn4hmjovm@4ax.com...
    > Could you point me in the direction of some code that could be used to
    > protect the program if I am not around to keep it updated?
    >
    > Thanks!
    >
    >
    >
    > On Mon, 19 Jun 2006 16:01:01 -0700, "Jeff Boyce" <nonsense@nonsense.com>
    > wrote:
    >
    >>Tom
    >>
    >>Check my earlier response. It wouldn't be absolute, but it would
    >>discourage
    >>the casual/curious.
    >>
    >>Regards
    >>
    >>Jeff Boyce
    >>Microsoft Office/Access MVP
    >>
    >>
    >>"Tom" <tom@home.com> wrote in message
    >>news:as7e92536ooniifice5g4nlivajt8e17he@4ax.com...
    >>> Jeff,
    >>>
    >>> The nature of the database is that it interchanges competitive part to
    >>> my
    >>> company's parts. The interchange info changes daily.
    >>>
    >>> I also supply this information company wide and the database is not
    >>> owned
    >>> by the company. I want a method that essentially shuts down the
    >>> functionality of the database after say 60 days, if I am no longer
    >>> around
    >>> to keep it going (long story).
    >>>
    >>> Hope this helps!
    >>>
    >>> Tom
    >>>
    >>>
    >>>
    >>> On Mon, 19 Jun 2006 11:49:51 -0700, "Jeff Boyce" <nonsense@nonsense.com>
    >>> wrote:
    >>>
    >>>>Tom
    >>>>
    >>>>Your criterion seems to be that if the app is older than (fill in a
    >>>>number),
    >>>>it is obsolete. I have at least one Access 2.0 application out there
    >>>>still
    >>>>running, still providing the service/functionality that the customer
    >>>>wants.
    >>>>Why do you believe that age will "obsolete" your application?
    >>>>
    >>>>You could add a constant in a code module and run a procedure on startup
    >>>>that checks the value in that constant.
    >>>>
    >>>>Regards
    >>>>
    >>>>Jeff Boyce
    >>>>Microsoft Office/Access MVP
    >>>>
    >>>>
    >>>>"Tom" <tom@home.com> wrote in message
    >>>>news:iiqd929pplt9gl73vm08ge4j5s39dr9a0u@4ax.com...
    >>>>> Not sure what group to be in, so I will start here.
    >>>>>
    >>>>> I have an Access 2K database I want to protect against obsolescence.
    >>>>> I
    >>>>> would like to add a macro or query or some VB Code that checks to see
    >>>>> the
    >>>>> last time the database was updated. If it exceeds a certain
    >>>>> timeframe,
    >>>>> an
    >>>>> message is displayed and the user is Exited from the database.
    >>>>>
    >>>>> Can someone make some suggestions on how to accomplish this or point
    >>>>> me
    >>>>> in
    >>>>> the correct direction?
    >>>>>
    >>>>> TIA!
    >>>>> ---
    >>>>> Tom
    >>>>>
    >>>>
    >>> ---
    >>> Tom
    >>>

    >>

    > ---
    > Tom
    >
     
  11. Tom

    Tom
    Expand Collapse
    Guest

    Jeff,

    Yes, I am thinking I do want something fairly strong. My database uses an
    Autoexec that some people know how to bypass and get into the database. I
    think I want something that disables everything after a certain number of
    days have elapsed if I am not around to update. Of course, I don't want
    anyone to know this in the meantime.

    Any thoughts?

    Thanks for your insights and help!

    Tom



    On Tue, 20 Jun 2006 16:03:03 -0700, "Jeff Boyce" <nonsense@nonsense.com>
    wrote:

    >Tom
    >
    >Please re-read my earlier response. If you don't need ironclad protection,
    >just discouragement for the lookie-loo's, set a constant in a code module
    >and write a procedure that checks the date in that constant and bails out if
    >the date is past.
    >
    >Regards
    >
    >Jeff Boyce
    >Microsoft Office/Access MVP
    >
    >
    >"Tom" <tom@home.com> wrote in message
    >news:hssg9295b50r8r6itkrjl9lt0dn4hmjovm@4ax.com...
    >> Could you point me in the direction of some code that could be used to
    >> protect the program if I am not around to keep it updated?
    >>
    >> Thanks!
    >>
    >>
    >>
    >> On Mon, 19 Jun 2006 16:01:01 -0700, "Jeff Boyce" <nonsense@nonsense.com>
    >> wrote:
    >>
    >>>Tom
    >>>
    >>>Check my earlier response. It wouldn't be absolute, but it would
    >>>discourage
    >>>the casual/curious.
    >>>
    >>>Regards
    >>>
    >>>Jeff Boyce
    >>>Microsoft Office/Access MVP
    >>>
    >>>
    >>>"Tom" <tom@home.com> wrote in message
    >>>news:as7e92536ooniifice5g4nlivajt8e17he@4ax.com...
    >>>> Jeff,
    >>>>
    >>>> The nature of the database is that it interchanges competitive part to
    >>>> my
    >>>> company's parts. The interchange info changes daily.
    >>>>
    >>>> I also supply this information company wide and the database is not
    >>>> owned
    >>>> by the company. I want a method that essentially shuts down the
    >>>> functionality of the database after say 60 days, if I am no longer
    >>>> around
    >>>> to keep it going (long story).
    >>>>
    >>>> Hope this helps!
    >>>>
    >>>> Tom
    >>>>
    >>>>
    >>>>
    >>>> On Mon, 19 Jun 2006 11:49:51 -0700, "Jeff Boyce" <nonsense@nonsense.com>
    >>>> wrote:
    >>>>
    >>>>>Tom
    >>>>>
    >>>>>Your criterion seems to be that if the app is older than (fill in a
    >>>>>number),
    >>>>>it is obsolete. I have at least one Access 2.0 application out there
    >>>>>still
    >>>>>running, still providing the service/functionality that the customer
    >>>>>wants.
    >>>>>Why do you believe that age will "obsolete" your application?
    >>>>>
    >>>>>You could add a constant in a code module and run a procedure on startup
    >>>>>that checks the value in that constant.
    >>>>>
    >>>>>Regards
    >>>>>
    >>>>>Jeff Boyce
    >>>>>Microsoft Office/Access MVP
    >>>>>
    >>>>>
    >>>>>"Tom" <tom@home.com> wrote in message
    >>>>>news:iiqd929pplt9gl73vm08ge4j5s39dr9a0u@4ax.com...
    >>>>>> Not sure what group to be in, so I will start here.
    >>>>>>
    >>>>>> I have an Access 2K database I want to protect against obsolescence.
    >>>>>> I
    >>>>>> would like to add a macro or query or some VB Code that checks to see
    >>>>>> the
    >>>>>> last time the database was updated. If it exceeds a certain
    >>>>>> timeframe,
    >>>>>> an
    >>>>>> message is displayed and the user is Exited from the database.
    >>>>>>
    >>>>>> Can someone make some suggestions on how to accomplish this or point
    >>>>>> me
    >>>>>> in
    >>>>>> the correct direction?
    >>>>>>
    >>>>>> TIA!
    >>>>>> ---
    >>>>>> Tom
    >>>>>>
    >>>>>
    >>>> ---
    >>>> Tom
    >>>>
    >>>

    >> ---
    >> Tom
    >>

    >

    ---
    Tom
     
  12. Jeff Boyce

    Jeff Boyce
    Expand Collapse
    Guest

    Tom

    A "Google" on "disable" & "bypass" & "autoexec" & "Access" should give you
    pointers to the code you can add to disable the Autoexec bypass.

    Again, with a constant and a procedure, you can do whatever, including
    shutting down the application.

    Regards

    Jeff Boyce
    Microsoft Office/Access MVP


    "Tom" <tom@home.com> wrote in message
    news:rt1j92tg9qner9i8kkhp49u0tmdcc23agf@4ax.com...
    > Jeff,
    >
    > Yes, I am thinking I do want something fairly strong. My database uses an
    > Autoexec that some people know how to bypass and get into the database. I
    > think I want something that disables everything after a certain number of
    > days have elapsed if I am not around to update. Of course, I don't want
    > anyone to know this in the meantime.
    >
    > Any thoughts?
    >
    > Thanks for your insights and help!
    >
    > Tom
    >
    >
    >
    > On Tue, 20 Jun 2006 16:03:03 -0700, "Jeff Boyce" <nonsense@nonsense.com>
    > wrote:
    >
    >>Tom
    >>
    >>Please re-read my earlier response. If you don't need ironclad
    >>protection,
    >>just discouragement for the lookie-loo's, set a constant in a code module
    >>and write a procedure that checks the date in that constant and bails out
    >>if
    >>the date is past.
    >>
    >>Regards
    >>
    >>Jeff Boyce
    >>Microsoft Office/Access MVP
    >>
    >>
    >>"Tom" <tom@home.com> wrote in message
    >>news:hssg9295b50r8r6itkrjl9lt0dn4hmjovm@4ax.com...
    >>> Could you point me in the direction of some code that could be used to
    >>> protect the program if I am not around to keep it updated?
    >>>
    >>> Thanks!
    >>>
    >>>
    >>>
    >>> On Mon, 19 Jun 2006 16:01:01 -0700, "Jeff Boyce" <nonsense@nonsense.com>
    >>> wrote:
    >>>
    >>>>Tom
    >>>>
    >>>>Check my earlier response. It wouldn't be absolute, but it would
    >>>>discourage
    >>>>the casual/curious.
    >>>>
    >>>>Regards
    >>>>
    >>>>Jeff Boyce
    >>>>Microsoft Office/Access MVP
    >>>>
    >>>>
    >>>>"Tom" <tom@home.com> wrote in message
    >>>>news:as7e92536ooniifice5g4nlivajt8e17he@4ax.com...
    >>>>> Jeff,
    >>>>>
    >>>>> The nature of the database is that it interchanges competitive part to
    >>>>> my
    >>>>> company's parts. The interchange info changes daily.
    >>>>>
    >>>>> I also supply this information company wide and the database is not
    >>>>> owned
    >>>>> by the company. I want a method that essentially shuts down the
    >>>>> functionality of the database after say 60 days, if I am no longer
    >>>>> around
    >>>>> to keep it going (long story).
    >>>>>
    >>>>> Hope this helps!
    >>>>>
    >>>>> Tom
    >>>>>
    >>>>>
    >>>>>
    >>>>> On Mon, 19 Jun 2006 11:49:51 -0700, "Jeff Boyce"
    >>>>> <nonsense@nonsense.com>
    >>>>> wrote:
    >>>>>
    >>>>>>Tom
    >>>>>>
    >>>>>>Your criterion seems to be that if the app is older than (fill in a
    >>>>>>number),
    >>>>>>it is obsolete. I have at least one Access 2.0 application out there
    >>>>>>still
    >>>>>>running, still providing the service/functionality that the customer
    >>>>>>wants.
    >>>>>>Why do you believe that age will "obsolete" your application?
    >>>>>>
    >>>>>>You could add a constant in a code module and run a procedure on
    >>>>>>startup
    >>>>>>that checks the value in that constant.
    >>>>>>
    >>>>>>Regards
    >>>>>>
    >>>>>>Jeff Boyce
    >>>>>>Microsoft Office/Access MVP
    >>>>>>
    >>>>>>
    >>>>>>"Tom" <tom@home.com> wrote in message
    >>>>>>news:iiqd929pplt9gl73vm08ge4j5s39dr9a0u@4ax.com...
    >>>>>>> Not sure what group to be in, so I will start here.
    >>>>>>>
    >>>>>>> I have an Access 2K database I want to protect against obsolescence.
    >>>>>>> I
    >>>>>>> would like to add a macro or query or some VB Code that checks to
    >>>>>>> see
    >>>>>>> the
    >>>>>>> last time the database was updated. If it exceeds a certain
    >>>>>>> timeframe,
    >>>>>>> an
    >>>>>>> message is displayed and the user is Exited from the database.
    >>>>>>>
    >>>>>>> Can someone make some suggestions on how to accomplish this or point
    >>>>>>> me
    >>>>>>> in
    >>>>>>> the correct direction?
    >>>>>>>
    >>>>>>> TIA!
    >>>>>>> ---
    >>>>>>> Tom
    >>>>>>>
    >>>>>>
    >>>>> ---
    >>>>> Tom
    >>>>>
    >>>>
    >>> ---
    >>> Tom
    >>>

    >>

    > ---
    > Tom
    >
     

Share This Page