Re: security for migrated db

anonymous_at_discussions.microsoft.com
Date: 05/20/04

  • Next message: Hari Prasad: "Re: Unable to Backup on Network"
    Date: Wed, 19 May 2004 16:45:53 -0700
    
    

    Thanks for the additional info.

    yba

    >-----Original Message-----
    >DoCmd is great for opening forms, in fact that's the
    only way to
    >programmatically open a form. For stored procedures, use
    an ADO
    >Connection or a Command object (which supports
    parameters). With
    >DoCmd, you don't have any way of getting information
    back from the
    >stored procedure as to whether it encountered any
    errors, or any way
    >of handling output parameter values.
    >
    >--Mary
    >
    >On Tue, 18 May 2004 15:15:42 -0700, "yba"
    ><anonymous@discussions.microsoft.com> wrote:
    >
    >>The version of Access that I am using is the OfficeXP
    >>version (2002, I belive). You mentioned that calling
    the
    >>docmd is not the best way of executing stored
    >>procedures. The app I am working on has a command
    button
    >>that executes a couple of stored procedures to modify
    >>(not just display) records in the database (append,
    >>delete, etc...) then opens a form that has a stored
    >>procedure associated with it to display the data
    >>associated with the form. If there is a more efficient
    >>way of doing this, I'd appreciate the tips and
    >>suggestions.
    >>
    >>Thanks,
    >>
    >>yba
    >>
    >>
    >>>-----Original Message-----
    >>>Are you by any chance using Access 2000? If so,
    >>upgrading to a newer
    >>>version solves many of the UI issues. FWIW, calling
    >>docmd is not the
    >>>best way of executing stored procedures. However,
    >>without more
    >>>information about your app and the specific errors you
    >>received, it's
    >>>difficult to make a more specific recommendation.
    >>>
    >>>--Mary
    >>>
    >>>On Mon, 17 May 2004 13:59:26 -0700, "yba"
    >>><anonymous@discussions.microsoft.com> wrote:
    >>>
    >>>>I am migrating a database from a Small Business
    Server
    >>>>that is currently overloaded. The SBS server is also
    >>the
    >>>>domain controller. When moving the database to a new
    >>>>server that is not on a domain controller, my access
    >>>>database project (ADP) now how in parentheses (dbo)
    >>after
    >>>>all database objects (stored procedures, tables,
    >>etc...)
    >>>>
    >>>>When the project is launched, it errors out stating
    >>that
    >>>>it can't see the stored procedures I am
    >>programmatically
    >>>>calling using the docmd function. However, I can go
    to
    >>>>the database window in access, which shows all the
    >>>>objects, and open/execute them from there just fine.
    >>Is
    >>>>this a security problem?
    >>>>
    >>>>Thanks
    >>>
    >>>.
    >>>
    >
    >.
    >


  • Next message: Hari Prasad: "Re: Unable to Backup on Network"
  • Quantcast