Question regarding Distributing

[Guest]

I have an application so to speak I have developed using MS Access and I am
wanting to be able to legally distribute it to people without Access or even
with it no mattter... The application will be distributed for profit as well
so I am not sure the rules on this. I know I need the runtime to distribute
but where can I get the software I need to do this? What developer edition do
I need and will it legally allow me to distribute the application for profit?

 

[Simonglencross]

Depending on what version of office your are using for example if you using
office xp then you need the deveolper version and you can then distribute
your access project legally even if the recipient has not got the whole
version of access etc. Hope this helps

Simon.

I have an application so to speak I have developed using MS Access and I am
wanting to be able to legally distribute it to people without Access or even
with it no mattter... The application will be distributed for profit as well
so I am not sure the rules on this. I know I need the runtime to distribute
but where can I get the software I need to do this? What developer edition do
I need and will it legally allow me to distribute the application for

profit?

 

[Brett Collings [429338]]

I have an application so to speak I have developed using MS Access and I am
wanting to be able to legally distribute it to people without Access or even
with it no mattter... The application will be distributed for profit as well
so I am not sure the rules on this. I know I need the runtime to distribute
but where can I get the software I need to do this? What developer edition do
I need and will it legally allow me to distribute the application for profit?

You need the developers tools edition for the version of Access that
you have. This could be Visual Studio or the Office Developers Tools
for older versions. They are expensive because you are paying for the
Distribution License for Access runtime.

In addition, you may need Installshield and SageKeys to safely delpoy
your applications. The MS product does a very poor job and can cause
all sorts of conflicts with existign copies of office on client
machines.

Brett
Cheers,
Brett

 

[Guest]

Ah thanks for the guidance. The application was developed using Access 2000 I
am guessing I need to find that developer edition on ebay or something.
Although I am considering maybe just getting a Access 2003 upgrade and the
visual studio that has the included extensions but I am not sure of the
advantages of it... Is it really all that worth it to move up? Is there that
many difference between the two or security improvements that would justify
spending the extra 400 dollars or so it would cost rather than just getting a
2k developer edition from ebay and being able to distribute for profit with
that?

 

[Larry Daugherty]

Whether to stay at Acc 2000 or spend more money to go to 2003 is a value
judgement that you have to make. I would say that for a difference of $400,
go for the latest. The most valuable component in the mix will be your
time.

Other recommendations:

Start hanging around the microsoft.public.access.developer.toolkits and
deftoolkitode newsgroups for scuttlebutt.

To the extent possible, replace ActiveX controls with API and code
equivalents - see www.mvps.org/access for lots of goodies. There is also an
ActiveX newsgroup. Otherwise your life may become busier than you'd like as
people call in demanding help in getting your application to work. To the
extent possible, test it on lots of different OS and environment
configurations.

If you haven't split your application into Front End and Back End, do so and
test it thoroughly in the runtime configuration as above before you release
it. When you do release, I recommend releasing your front end as an .MDE
file. That way no one can fiddle with your code and then call on you to fix
it.

HTH