Results 1 to 4 of 4
  1. #1
    Join Date
    Nov 2003
    Posts
    18

    Unanswered: -

    -
    Last edited by TheGame7; 12-10-03 at 11:07.

  2. #2
    Join Date
    Dec 2002
    Location
    Préverenges, Switzerland
    Posts
    3,740
    yes of course.

    you need:

    exit sub 'quit here to avoid the error handler
    ErrHandler:


    izy
    currently using SS 2008R2

  3. #3
    Join Date
    Dec 2002
    Location
    Préverenges, Switzerland
    Posts
    3,740
    PS best not to use "ErrHandler" as the label... maybe you have several error handlers.

    use the ugly-but-safer

    Private sub SubIsCalledThis()
    on error goto err_SubIsCalledThis
    'blah
    'all you code goes here
    'blah
    exit sub 'quit to avoid error handling

    err_SubIsCalledThis:
    'error handling goes here

    end sub

    so that each routine has a unique label names. saves confusion or worse.

    izy
    currently using SS 2008R2

  4. #4
    Join Date
    Dec 2002
    Location
    Préverenges, Switzerland
    Posts
    3,740
    there are too many ways.

    simplest (assuming you dont have thousands of rows in tblPassword AND you have a field userID (long) to lookup and you are looking for userID=1):

    dim thePW as string
    thePW = DLOOKUP("Password", "tblPassword", "userID = 1")

    BUT it is not brilliant security to store your PW as plain-text in a table! consider encrypting the stored version. use the same encryption on the user input and compare the two encrypted versions.

    if you are feeling masochistic and you have nothing to do the next few weeks, you could try messing with Access' built in security nightmare.

    izy
    currently using SS 2008R2

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •