Welcome to SPN

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

Sign Up Now!

Access and vb runtime

Discussion in 'Information Technology' started by Luke Bellamy, Nov 1, 2005.

Tags:
  1. Luke Bellamy

    Luke Bellamy
    Expand Collapse
    Guest

    Hi - I recently installed vb runtime sp6 on my development
    machine without thinking too much. Now I actually use the
    common dialog controls etc so when I started up my mde app
    I compiled with sp5 previously it gave me an error trying to
    open forms with some of these controls on it.
    Note that I also use stand alone vb apps with sp5 which I
    upgraded visual studio to sp6.

    So I'm assuming I have 2 options:
    1. Roll back to sp5 if possible, but if not reformat my machine.
    2. Include sp6 in my distribution artefacts and upgrades for existing users.

    Can option 1 be done nicely?
    I'd prefer not to go with option 2 as you are required to be logged
    in as admin to apply an upgrade (for vb runtime) and each client in
    a network configuration needs to be updated.

    Any comments appreciated.
    Thanks,
    Luke
     
  2. Loading...


  3. Larry Linson

    Larry Linson
    Expand Collapse
    Guest

    On the menu of the database window, Tools | References and add a reference
    to the appropriate library. On the other hand, if you distribute your MDE to
    users who do not have that library, but use/reference it, you are likely to
    have problems (sometimes called, "DLL Hell").

    A possible probelm is that the more recent version may have eliminated the
    older version from your system, so that you cannot go back even if you want
    to.

    Which of the Common Controls do you use? And how do you use them? Perhaps
    there is another way.

    Larry Linson
    Microsoft Access MVP


    "Luke Bellamy" <Luke@CashWhiz.com.au> wrote in message
    news:uZ5R0Nf3FHA.3036@TK2MSFTNGP10.phx.gbl...
    > Hi - I recently installed vb runtime sp6 on my development
    > machine without thinking too much. Now I actually use the
    > common dialog controls etc so when I started up my mde app
    > I compiled with sp5 previously it gave me an error trying to
    > open forms with some of these controls on it.
    > Note that I also use stand alone vb apps with sp5 which I
    > upgraded visual studio to sp6.
    >
    > So I'm assuming I have 2 options:
    > 1. Roll back to sp5 if possible, but if not reformat my machine.
    > 2. Include sp6 in my distribution artefacts and upgrades for existing
    > users.
    >
    > Can option 1 be done nicely?
    > I'd prefer not to go with option 2 as you are required to be logged
    > in as admin to apply an upgrade (for vb runtime) and each client in
    > a network configuration needs to be updated.
    >
    > Any comments appreciated.
    > Thanks,
    > Luke
    >
    >
     
  4. Luke Bellamy

    Luke Bellamy
    Expand Collapse
    Guest

    I reference comdlg32.ocx, mscomctl.ocx, and comctl32.ocx.

    So in my Access 2002 app I have the dialog controls to open, save
    files and choose colours. As for the commons controls I use the
    progress bar.
    And to be honest I can remember why they are both selected (mscomctl.ocx
    and comctl32.ocx)

    I know you can use a Win API to open and close files but the others
    may be a bit trickier.

    Do you know if I had sp5 on my machine and distributed with vb runtime sp5,
    and then another application install runtime sp6 would it still be backward
    compatible?

    Thanks for your help Larry.
    ---------------
    Luke Bellamy
    Newcastle, Australia

    "Larry Linson" <bouncer@localhost.not> wrote in message
    news:eXMfWlm3FHA.3976@TK2MSFTNGP15.phx.gbl...
    > On the menu of the database window, Tools | References and add a reference
    > to the appropriate library. On the other hand, if you distribute your MDE
    > to users who do not have that library, but use/reference it, you are
    > likely to have problems (sometimes called, "DLL Hell").
    >
    > A possible probelm is that the more recent version may have eliminated the
    > older version from your system, so that you cannot go back even if you
    > want to.
    >
    > Which of the Common Controls do you use? And how do you use them? Perhaps
    > there is another way.
    >
    > Larry Linson
    > Microsoft Access MVP
    >
    >
    > "Luke Bellamy" <Luke@CashWhiz.com.au> wrote in message
    > news:uZ5R0Nf3FHA.3036@TK2MSFTNGP10.phx.gbl...
    >> Hi - I recently installed vb runtime sp6 on my development
    >> machine without thinking too much. Now I actually use the
    >> common dialog controls etc so when I started up my mde app
    >> I compiled with sp5 previously it gave me an error trying to
    >> open forms with some of these controls on it.
    >> Note that I also use stand alone vb apps with sp5 which I
    >> upgraded visual studio to sp6.
    >>
    >> So I'm assuming I have 2 options:
    >> 1. Roll back to sp5 if possible, but if not reformat my machine.
    >> 2. Include sp6 in my distribution artefacts and upgrades for existing
    >> users.
    >>
    >> Can option 1 be done nicely?
    >> I'd prefer not to go with option 2 as you are required to be logged
    >> in as admin to apply an upgrade (for vb runtime) and each client in
    >> a network configuration needs to be updated.
    >>
    >> Any comments appreciated.
    >> Thanks,
    >> Luke
    >>
    >>

    >
    >
     
  5. Luke Bellamy

    Luke Bellamy
    Expand Collapse
    Guest

    Larry - FYI I have implemented the API calls to open/save files (from
    MVPS.org/access), select colours from
    the colour dialog (from MVPS.org/access), and implemented the alternate to
    the progress bar using rectangles
    as posted on the microsoft web site.

    That should ease my pain.

    Thanks Larry,
    Luke

    "Larry Linson" <bouncer@localhost.not> wrote in message
    news:eXMfWlm3FHA.3976@TK2MSFTNGP15.phx.gbl...
    > On the menu of the database window, Tools | References and add a reference
    > to the appropriate library. On the other hand, if you distribute your MDE

    to
    > users who do not have that library, but use/reference it, you are likely

    to
    > have problems (sometimes called, "DLL Hell").
    >
    > A possible probelm is that the more recent version may have eliminated the
    > older version from your system, so that you cannot go back even if you

    want
    > to.
    >
    > Which of the Common Controls do you use? And how do you use them? Perhaps
    > there is another way.
    >
    > Larry Linson
    > Microsoft Access MVP
    >
    >
    > "Luke Bellamy" <Luke@CashWhiz.com.au> wrote in message
    > news:uZ5R0Nf3FHA.3036@TK2MSFTNGP10.phx.gbl...
    > > Hi - I recently installed vb runtime sp6 on my development
    > > machine without thinking too much. Now I actually use the
    > > common dialog controls etc so when I started up my mde app
    > > I compiled with sp5 previously it gave me an error trying to
    > > open forms with some of these controls on it.
    > > Note that I also use stand alone vb apps with sp5 which I
    > > upgraded visual studio to sp6.
    > >
    > > So I'm assuming I have 2 options:
    > > 1. Roll back to sp5 if possible, but if not reformat my machine.
    > > 2. Include sp6 in my distribution artefacts and upgrades for existing
    > > users.
    > >
    > > Can option 1 be done nicely?
    > > I'd prefer not to go with option 2 as you are required to be logged
    > > in as admin to apply an upgrade (for vb runtime) and each client in
    > > a network configuration needs to be updated.
    > >
    > > Any comments appreciated.
    > > Thanks,
    > > Luke
    > >
    > >

    >
    >
     

Share This Page