I see both terms used. It appears that there is a developers tool kitt hat
one can obtain to use with his or her existing access application. However,
the term Developer's Edition appears to me to indicate a completely different
and separate program.
Can someone plese elaborate on the differences for me?

Thank you all
--
Plus 65

If memory serves, the only version that had both versions was Access 2000.
You could either get just the Developer's Tool Kit (which provided you with
what you needed to legally distribute the Access run-time) or you could get
Office 2000 Developer Edition, which included the Developer's Tool Kit and a
copy of Office 2000 Professional.

Tony Toews attempts to enumerate all of the terminology at
http://www.granite.ab.ca/access/developereditionfaq.htm

--
Doug Steele, Microsoft Access MVP
http://I.Am/DougSteele
(no private e-mails, please)


"Plus65" <(E-Mail Removed)> wrote in message
news:8E111F8F-9533-496C-A190-(E-Mail Removed)...
>I see both terms used. It appears that there is a developers tool kitt hat
> one can obtain to use with his or her existing access application.
> However,
> the term Developer's Edition appears to me to indicate a completely
> different
> and separate program.
> Can someone plese elaborate on the differences for me?
>
> Thank you all
> --
> Plus 65

Hi.

In addition to Doug's and Tony's advice, you may also be interested the free
Access 2007 Runtime and Access Developers Extensions (tools used to build
and distribute Access database applications), which is about $800 in savings
over purchasing the Visual Studio Tools for Office (VSTO) that is required
for Access 2003. They require a retail version of Access 2007 to develop
the database file with, but the Runtime version is a free distribution for
those customers who don't have Access but want to run your database
application.

One may download these files from the following Web pages:

Access 2007 Developer Extensions:

http://www.microsoft.com/downloads/d...displaylang=en

Access 2007 Runtime:

http://www.microsoft.com/downloads/d...displaylang=en

HTH.
Gunny

See http://www.QBuilt.com for all your database needs.
See http://www.Access.QBuilt.com for Microsoft Access tips and tutorials.
Blogs: www.DataDevilDog.BlogSpot.com, www.DatabaseTips.BlogSpot.com
http://www.Access.QBuilt.com/html/ex...ributors2.html for contact
info.

"Douglas J. Steele" <NOSPAM_djsteele@NOSPAM_canada.com> wrote:

>Tony Toews attempts to enumerate all of the terminology at
>http://www.granite.ab.ca/access/developereditionfaq.htm

<chuckle> Yeah, I did my best attempt.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/

wOW! Ever read one or your posts and wish that you had edited it better for
spelling?

Thanks for your responses guys. Very helpful.

A little further info needed. Do the runtime versions work on a network?

Thanks again
--
Plus 65


"Plus65" wrote:

> I see both terms used. It appears that there is a developers tool kitt hat
> one can obtain to use with his or her existing access application. However,
> the term Developer's Edition appears to me to indicate a completely different
> and separate program.
> Can someone plese elaborate on the differences for me?
>
> Thank you all
> --
> Plus 65

The runtime version is the same msacess.exe executable as in the full
version: it's just been limited (through literally hundreds of registry
entries) so that it cannot make design changes.

Like all other Windows products, it must be properly installed on each
client workstation. Once that's done, it can certainly work with files that
are on the network, although the recommended approach is to split the
application into a front-end (containing the queries, forms, reports, macros
and modules), linked to a back-end (containing the tables and
relationships). Only the back-end should be on the server. Each user should
have his/her own copy of the front-end, ideally on his/her hard drive.

--
Doug Steele, Microsoft Access MVP
http://I.Am/DougSteele
(no private e-mails, please)


"Plus65" <(E-Mail Removed)> wrote in message
news:89A4BF5B-67E3-463F-BFE5-(E-Mail Removed)...
> wOW! Ever read one or your posts and wish that you had edited it better
> for
> spelling?
>
> Thanks for your responses guys. Very helpful.
>
> A little further info needed. Do the runtime versions work on a network?
>
> Thanks again
> --
> Plus 65
>
>
> "Plus65" wrote:
>
>> I see both terms used. It appears that there is a developers tool kitt
>> hat
>> one can obtain to use with his or her existing access application.
>> However,
>> the term Developer's Edition appears to me to indicate a completely
>> different
>> and separate program.
>> Can someone plese elaborate on the differences for me?
>>
>> Thank you all
>> --
>> Plus 65

"Douglas J. Steele" <NOSPAM_djsteele@NOSPAM_canada.com> wrote:

>The runtime version is the same msacess.exe executable as in the full
>version: it's just been limited (through literally hundreds of registry
>entries) so that it cannot make design changes.

Except that in A2003 it installs the version of Access and dlls which
were distributed with your original version of Access. That is no
patches or Service Packs. Furthermore, in some cases, Microsoft
Update doesn't find the runtime install and doesn't do the update. So
you'll manually need to download and install O2003 SP2 or SP3 on that
workstation.

Note that some of us are not recommending SP3 due to the nature of
some of it's bugs.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/

Plus65 <(E-Mail Removed)> wrote:

>wOW! Ever read one or your posts and wish that you had edited it better for
>spelling?

<chuckle> I have spell check enabled. But occasionally yes.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/

> Except that in A2003 it installs the version of Access and dlls which
> were distributed with your original version of Access. That is no
> patches or Service Packs. Furthermore, in some cases, Microsoft
> Update doesn't find the runtime install and doesn't do the update. So
> you'll manually need to download and install O2003 SP2 or SP3 on that
> workstation.
>
> Note that some of us are not recommending SP3 due to the nature of
> some of it's bugs.

And please note that some of us are not recommending SP-2 either, due to
that annoying inability to update linked spreadsheets. So having no
automatic download and installation of these service packs isn't such a bad
thing. ;-)

HTH.
Gunny

See http://www.QBuilt.com for all your database needs.
See http://www.Access.QBuilt.com for Microsoft Access tips and tutorials.
Blogs: www.DataDevilDog.BlogSpot.com, www.DatabaseTips.BlogSpot.com
http://www.Access.QBuilt.com/html/ex...ributors2.html for contact
info.

"'69 Camaro" <(E-Mail Removed)_SPAM>
wrote:

>And please note that some of us are not recommending SP-2 either, due to
>that annoying inability to update linked spreadsheets.

That one doesn't affect me so no big deal.

>So having no
>automatic download and installation of these service packs isn't such a bad
>thing. ;-)

FWIW Microsoft Update Manager has not yet prompted me to install
Office SP3. Which I find rather interesting.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/