Results 1 to 5 of 5

Thread: about MS Access policy

  1. #1

    Thread Starter
    Lively Member
    Join Date
    Jun 2003
    Posts
    89

    about MS Access policy

    Hi,
    I developed a small application based on a .mdb database.
    I don't own a copy of Microsoft Access, so I'm creating my MDBs using ADO/DAO and managing them with other tools such as Table Editor.

    Now, someone I know is interested in my application and I would like to sell it to him. Can I sell my software even if my customer and me don't own Microsoft Access?
    Thanks

    sorry for the dumb question, I didnt come up with anything searching the internet.
    Last edited by BrightSoul; Dec 19th, 2004 at 07:24 AM.
    - mo! I said MOOOOOOO!!
    - ...yep, that's a cow, alright.

  2. #2
    MS SQL Powerposter szlamany's Avatar
    Join Date
    Mar 2004
    Location
    Connecticut
    Posts
    18,263

    Re: about MS Access policy

    We do MS SQL SERVER development, so I don't know the answer to this question - but you might get more answers posting in the DATABASE DEVELOPMENT forum. There are many ACCESS questions floating around in there all the time...

  3. #3
    Ex-Super Mod RobDog888's Avatar
    Join Date
    Apr 2001
    Location
    LA, Calif. Raiders #1 AKA:Gangsta Yoda™
    Posts
    60,709

    Re: about MS Access policy

    I believe the runtimes associated with Access are distributable but not the ones
    that allow you to display and interact with the GUI, so to speak. If your
    program only uses Access as the back-end using ADO/DAO then I think your ok.

    For the best understanding of MS' licensing, try a search on M$ for the exact
    wording since you are going to be selling your prog.

    HTH
    VB/Office Guru™ (AKA: Gangsta Yoda®)
    I dont answer coding questions via PM. Please post a thread in the appropriate forum.

    Microsoft MVP 2006-2011
    Office Development FAQ (C#, VB.NET, VB 6, VBA)
    Senior Jedi Software Engineer MCP (VB 6 & .NET), BSEE, CET
    If a post has helped you then Please Rate it!
    Reps & Rating PostsVS.NET on Vista Multiple .NET Framework Versions Office Primary Interop AssembliesVB/Office Guru™ Word SpellChecker™.NETVB/Office Guru™ Word SpellChecker™ VB6VB.NET Attributes Ex.Outlook Global Address ListAPI Viewer utility.NET API Viewer Utility
    System: Intel i7 6850K, Geforce GTX1060, Samsung M.2 1 TB & SATA 500 GB, 32 GBs DDR4 3300 Quad Channel RAM, 2 Viewsonic 24" LCDs, Windows 10, Office 2016, VS 2019, VB6 SP6

  4. #4

    Thread Starter
    Lively Member
    Join Date
    Jun 2003
    Posts
    89

    Re: about MS Access policy

    thanks, much appreciated
    - mo! I said MOOOOOOO!!
    - ...yep, that's a cow, alright.

  5. #5
    Junior Member llkhoutx's Avatar
    Join Date
    Jan 2005
    Location
    Houston, TX
    Posts
    19

    Re: about MS Access policy

    Access is frought with program security & protection problems, but is relatively cheap. Any Access front-end and back-end mdb and/or mde is freely distributable - any GUI object created can be freely distributed. Multi Access versions also create a user problem, as you'll encounter all versions in the market and will have to maintain multiple versions of your progam. Only A2003 is readily available today. A2K, A2k2 and A2003 all handle A2K back-ends, which is some help.

    However, for a runtime version, one needs Office Developer edition compatiuble with your Access version, which will generate a runtime package feely distributable. However, it's also fought with problems, especially if users have multiple versions of Access installed. Wise also has a runtime packager which is purportedly very good, but it also requires Office Developer. A runtime will install and run without and regardless of any existing version of Access on the installed PC. That make the runtime a good choice.

    $2,000 should be enough for all the programs you need.

    Gary Robinson has a very good book on Microsoft Access Database Protection and Secutity. He has some Access program security protection techniques which I've not seen published elsewhere.

    Customers have to have a compatible version of Access or you have to provide a runtime version.

Posting Permissions

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



Click Here to Expand Forum to Full Width