Welcome to SPN

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

Sign Up Now!

Release to End Users

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

Tags:
  1. Jennifer Cali

    Jennifer Cali
    Expand Collapse
    Guest

    I've (finally!) finished my database and want to give it to a few
    family/friends. Not all of them have Access, however, on their computers. Is
    there a program out there that I can buy that will enable me to "burn" some
    type of program onto a CD with my database to allow them to run the program?
    Or does a user HAVE to have Access to run?

    --
    Thank you! - Jennifer
     
  2. Loading...

    Similar Threads Forum Date
    Controversial Akal Takht Releases Nanakshahi Calendar Hard Talk Feb 9, 2013
    News Akal Takht Releases Amended Nanakshahi Calendar in Haste (also in Punjabi) Punjab, Punjabi, Punjabiyat Feb 18, 2011
    India Vedanti releases ‘original’ Nanakshahi Calendar Breaking News Jan 18, 2011
    He’s The World’s Best Water Photographer… And He’s Just Released These Haunting Images. Sikh Sikhi Sikhism Aug 30, 2015
    Movies Ashdoc's movie review---Masaan ( released july 2015 ) Theatre, Movies & Cinema Jul 29, 2015

  3. Jon Ley

    Jon Ley
    Expand Collapse
    Guest

    Either end user has to have full Access version, or developer has to buy
    Developer version (pre Access 2003) or Visual Studio Tools for Office (for
    Access 2003) which allows you to distribute a run-time version of Access.
    Distributing Access run-time can be its own special can of worms if you start
    sending this to users who may already have a different version of Access
    installed. Although multiple versions of Access can co-exist on a machine,
    the file associations can easily get confused so you don't necessarily get
    the expected result if you just double-click your mdb.

    "Jennifer Cali" wrote:

    > I've (finally!) finished my database and want to give it to a few
    > family/friends. Not all of them have Access, however, on their computers. Is
    > there a program out there that I can buy that will enable me to "burn" some
    > type of program onto a CD with my database to allow them to run the program?
    > Or does a user HAVE to have Access to run?
    >
    > --
    > Thank you! - Jennifer
     
  4. Jennifer Cali

    Jennifer Cali
    Expand Collapse
    Guest

    Jon, thanks for the tips. If you were me (and I won't hold you to anything, I
    promise), which would you suggest using? The developer version or Visual
    Studios Tools? Is there a way to ensure that the program, once distributed
    via CD, can be installed & run on computers regardless of if they have Access
    or not?
    --
    Thank you! - Jennifer


    "Jon Ley" wrote:

    > Either end user has to have full Access version, or developer has to buy
    > Developer version (pre Access 2003) or Visual Studio Tools for Office (for
    > Access 2003) which allows you to distribute a run-time version of Access.
    > Distributing Access run-time can be its own special can of worms if you start
    > sending this to users who may already have a different version of Access
    > installed. Although multiple versions of Access can co-exist on a machine,
    > the file associations can easily get confused so you don't necessarily get
    > the expected result if you just double-click your mdb.
    >
    > "Jennifer Cali" wrote:
    >
    > > I've (finally!) finished my database and want to give it to a few
    > > family/friends. Not all of them have Access, however, on their computers. Is
    > > there a program out there that I can buy that will enable me to "burn" some
    > > type of program onto a CD with my database to allow them to run the program?
    > > Or does a user HAVE to have Access to run?
    > >
    > > --
    > > Thank you! - Jennifer
     
  5. Jon Ley

    Jon Ley
    Expand Collapse
    Guest

    Jennifer,

    I'm not 100% sure, but I think you have no choice over ODE/VSTO. I think it
    is determined by which version of Access you are using. If you are using
    anything prior to 2003 then you need ODE, if you are using 2003 then you will
    need VSTO. I do not have much experience of Access 2003, and none of either
    ODE or VSTO (now there's a thing to admit when I'm trying to offer advice!),
    but from the experience I do have I would offer the following thoughts. I've
    no doubt others will chip in to tell me if I'm way off course. You could also
    search the groups for threads relating to ODE or VSTO; it's a question that
    comes up pretty regularly.

    1. Whichever way you go, the CD you create will include a 'runtime' version
    of Access which will allow users to open databases and run any VBA code or
    macros that are already included in the database design. However I guess
    there is some mechanism to prevent you from creating new objects within a
    database (possibly tables and queries, almost certainly forms, reports,
    macros and modules). Not entirely sure, but you may be in trouble if your VBA
    code tries to create temporary tables or modify the SQL of queries.

    2. There may be implications if you distribute the runtime version to
    someone who already has the full version, but you would need to check this.

    3. Various people recommend buting third party tools for creating the
    installation package, rather than using the Package and Deployment Wizard
    that comes with ODE.

    4. The few systems I have seen that use 2003 are really annoying as every
    time you open the database you get loads of warnings about unsafe expressions
    etc. This is all designed to protect you from malicious code that could be
    secreted away inside a database, and there are ways around it, but it
    involves digitally signing your application and there is loads in the 2003
    help about it. Because of our set up at work with various people on various
    versions I haven't really been inclined to research it properly yet - I've
    just told the 2003 users that they have to press a few extra buttons when
    they open the database.

    Happy hunting!

    Jon.

    "Jennifer Cali" wrote:

    > Jon, thanks for the tips. If you were me (and I won't hold you to anything, I
    > promise), which would you suggest using? The developer version or Visual
    > Studios Tools? Is there a way to ensure that the program, once distributed
    > via CD, can be installed & run on computers regardless of if they have Access
    > or not?
    > --
    > Thank you! - Jennifer
    >
    >
    > "Jon Ley" wrote:
    >
    > > Either end user has to have full Access version, or developer has to buy
    > > Developer version (pre Access 2003) or Visual Studio Tools for Office (for
    > > Access 2003) which allows you to distribute a run-time version of Access.
    > > Distributing Access run-time can be its own special can of worms if you start
    > > sending this to users who may already have a different version of Access
    > > installed. Although multiple versions of Access can co-exist on a machine,
    > > the file associations can easily get confused so you don't necessarily get
    > > the expected result if you just double-click your mdb.
    > >
    > > "Jennifer Cali" wrote:
    > >
    > > > I've (finally!) finished my database and want to give it to a few
    > > > family/friends. Not all of them have Access, however, on their computers. Is
    > > > there a program out there that I can buy that will enable me to "burn" some
    > > > type of program onto a CD with my database to allow them to run the program?
    > > > Or does a user HAVE to have Access to run?
    > > >
    > > > --
    > > > Thank you! - Jennifer
     
  6. Jennifer Cali

    Jennifer Cali
    Expand Collapse
    Guest

    Hey Jon,
    Much appreciate the info - that was totally helpful. I'm going to buy Visual
    Studio Tools for Office 2005; that sounds like the best choice. You rock!

    --
    Thank you! - Jennifer


    "Jon Ley" wrote:

    > Jennifer,
    >
    > I'm not 100% sure, but I think you have no choice over ODE/VSTO. I think it
    > is determined by which version of Access you are using. If you are using
    > anything prior to 2003 then you need ODE, if you are using 2003 then you will
    > need VSTO. I do not have much experience of Access 2003, and none of either
    > ODE or VSTO (now there's a thing to admit when I'm trying to offer advice!),
    > but from the experience I do have I would offer the following thoughts. I've
    > no doubt others will chip in to tell me if I'm way off course. You could also
    > search the groups for threads relating to ODE or VSTO; it's a question that
    > comes up pretty regularly.
    >
    > 1. Whichever way you go, the CD you create will include a 'runtime' version
    > of Access which will allow users to open databases and run any VBA code or
    > macros that are already included in the database design. However I guess
    > there is some mechanism to prevent you from creating new objects within a
    > database (possibly tables and queries, almost certainly forms, reports,
    > macros and modules). Not entirely sure, but you may be in trouble if your VBA
    > code tries to create temporary tables or modify the SQL of queries.
    >
    > 2. There may be implications if you distribute the runtime version to
    > someone who already has the full version, but you would need to check this.
    >
    > 3. Various people recommend buting third party tools for creating the
    > installation package, rather than using the Package and Deployment Wizard
    > that comes with ODE.
    >
    > 4. The few systems I have seen that use 2003 are really annoying as every
    > time you open the database you get loads of warnings about unsafe expressions
    > etc. This is all designed to protect you from malicious code that could be
    > secreted away inside a database, and there are ways around it, but it
    > involves digitally signing your application and there is loads in the 2003
    > help about it. Because of our set up at work with various people on various
    > versions I haven't really been inclined to research it properly yet - I've
    > just told the 2003 users that they have to press a few extra buttons when
    > they open the database.
    >
    > Happy hunting!
    >
    > Jon.
    >
    > "Jennifer Cali" wrote:
    >
    > > Jon, thanks for the tips. If you were me (and I won't hold you to anything, I
    > > promise), which would you suggest using? The developer version or Visual
    > > Studios Tools? Is there a way to ensure that the program, once distributed
    > > via CD, can be installed & run on computers regardless of if they have Access
    > > or not?
    > > --
    > > Thank you! - Jennifer
    > >
    > >
    > > "Jon Ley" wrote:
    > >
    > > > Either end user has to have full Access version, or developer has to buy
    > > > Developer version (pre Access 2003) or Visual Studio Tools for Office (for
    > > > Access 2003) which allows you to distribute a run-time version of Access.
    > > > Distributing Access run-time can be its own special can of worms if you start
    > > > sending this to users who may already have a different version of Access
    > > > installed. Although multiple versions of Access can co-exist on a machine,
    > > > the file associations can easily get confused so you don't necessarily get
    > > > the expected result if you just double-click your mdb.
    > > >
    > > > "Jennifer Cali" wrote:
    > > >
    > > > > I've (finally!) finished my database and want to give it to a few
    > > > > family/friends. Not all of them have Access, however, on their computers. Is
    > > > > there a program out there that I can buy that will enable me to "burn" some
    > > > > type of program onto a CD with my database to allow them to run the program?
    > > > > Or does a user HAVE to have Access to run?
    > > > >
    > > > > --
    > > > > Thank you! - Jennifer
     

Share This Page