By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
454,101 Members | 971 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 454,101 IT Pros & Developers. It's quick & easy.

Access Developer's Edition Questions

P: n/a
I use A2003, but I assume the following is similar for other versions.

I am getting pressure to distribute some apps to users who don't have MS
Access. If anyone would care to read, can I please present my
summarized understanding of what the Developer's Edition does?

I may well have some of my terms mixed up:

From what I've read here, it installs a stripped down version of Access
and the Jet database engine and this is what is called up when an
application is started.

Is that correct?

DOes the app Front and and Back End (if used) have the same format if
you use the run time versus against a full install of Access?

What about if a user already has Access installed? I know in A97 at
least another manager had purchased an application for tracking deferred
maintenance that was "run time" Access and it resulted in a total
screwing of the reference set up for his A97 on his machine (and my apps
using format, left, etc, would not work on his machine).

Thanks very much in advance for any comments.
--
Tim http://www.ucs.mun.ca/~tmarshal/
^o<
/#) "Burp-beep, burp-beep, burp-beep?" - Quaker Jake
/^^ "Whatcha doin?" - Ditto "TIM-MAY!!" - Me
Nov 13 '05 #1
Share this Question
Share on Google+
7 Replies


P: n/a
On Fri, 28 Jan 2005 15:11:48 -0330, Tim Marshall
<TI****@antarctic.flowerpots> wrote:

<snip>

From what I've read here, it installs a stripped down version of Access
and the Jet database engine and this is what is called up when an
application is started.

Is that correct? Crippled rather than stripped down. Jet is the same.
DOes the app Front and and Back End (if used) have the same format if
you use the run time versus against a full install of Access?
Not sure what you meanWhat about if a user already has Access installed?

Can be bad news if it a later version, which is bound to happen
eventually. This can be the case even if it is a later version of
Office without Access. Also you need to be good with double negatives
to answer the install questions. But maybe this has improved.

The whole question of deploying Access is its Achilles heel in my
opinion.
David

Nov 13 '05 #2

P: n/a
Tim Marshall wrote:
I use A2003, but I assume the following is similar for other versions.

I am getting pressure to distribute some apps to users who don't have MS
Access. If anyone would care to read, can I please present my
summarized understanding of what the Developer's Edition does?

I may well have some of my terms mixed up:

From what I've read here, it installs a stripped down version of Access
and the Jet database engine and this is what is called up when an
application is started.

Is that correct?
Yes.
DOes the app Front and and Back End (if used) have the same format if
you use the run time versus against a full install of Access?
Yes.
What about if a user already has Access installed? I know in A97 at
least another manager had purchased an application for tracking deferred
maintenance that was "run time" Access and it resulted in a total
screwing of the reference set up for his A97 on his machine (and my apps
using format, left, etc, would not work on his machine).


There's a few threads about having different versions of Access
installed, not sure if the same applies to the runtime.

--
This sig left intentionally blank
Nov 13 '05 #3

P: n/a
What about if a user already has Access installed? I know in A97 at
least another manager had purchased an application for tracking deferred
maintenance that was "run time" Access and it resulted in a total screwing
of the reference set up for his A97 on his machine (and my apps using
format, left, etc, would not work on his machine).
See the following link www.sagekey.com for a method of deploying run-time
access applications without affecting other versions of Access that may be
installed on the users machine. NOTE: it is not free, but IMHO well worth
the small investment.

"Trevor Best" <no****@besty.org.uk> wrote in message
news:41***********************@news.zen.co.uk... Tim Marshall wrote:
I use A2003, but I assume the following is similar for other versions.

I am getting pressure to distribute some apps to users who don't have MS
Access. If anyone would care to read, can I please present my summarized
understanding of what the Developer's Edition does?

I may well have some of my terms mixed up:

From what I've read here, it installs a stripped down version of Access
and the Jet database engine and this is what is called up when an
application is started.

Is that correct?


Yes.
DOes the app Front and and Back End (if used) have the same format if you
use the run time versus against a full install of Access?


Yes.
What about if a user already has Access installed? I know in A97 at
least another manager had purchased an application for tracking deferred
maintenance that was "run time" Access and it resulted in a total
screwing of the reference set up for his A97 on his machine (and my apps
using format, left, etc, would not work on his machine).


There's a few threads about having different versions of Access installed,
not sure if the same applies to the runtime.

--
This sig left intentionally blank

Nov 13 '05 #4

P: n/a
Scott Berry wrote:
See the following link www.sagekey.com for a method of deploying run-time
access applications without affecting other versions of Access that may be
installed on the users machine. NOTE: it is not free, but IMHO well worth
the small investment.


I'll look into this, Scott, thanks very much. As I mentioned, I've seen
how A97 on another manager's machine was wrecked by the installation of
a run time Access app and I'm very concerned about possibly doing the
same to others.

--
Tim http://www.ucs.mun.ca/~tmarshal/
^o<
/#) "Burp-beep, burp-beep, burp-beep?" - Quaker Jake
/^^ "What's UP, Dittoooooo?" - Ditto
Nov 13 '05 #5

P: n/a
Tim Marshall <TI****@antarctic.flowerpots> wrote:

Do note that A2003 will only run on Win 2000 SP3 or Win XP or newer. So if your
target audience includes Win 98 or NT 4.0 you've got problems.
From what I've read here, it installs a stripped down version of Access
and the Jet database engine and this is what is called up when an
application is started.

Is that correct?
Correct.
DOes the app Front and and Back End (if used) have the same format if
you use the run time versus against a full install of Access?
Yes. Although you'd likely want to distribute an MDE.
What about if a user already has Access installed? I know in A97 at
least another manager had purchased an application for tracking deferred
maintenance that was "run time" Access and it resulted in a total
screwing of the reference set up for his A97 on his machine (and my apps
using format, left, etc, would not work on his machine).


Royal pain. As others have suggested www.sagekey.com is an excellent solution.

Microsoft Access (Office) Developer Edition FAQ
http://www.granite.ab.ca/access/developereditionfaq.htm
--
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
Nov 13 '05 #6

P: n/a
On Mon, 31 Jan 2005 05:45:56 GMT, Tony Toews <tt****@telusplanet.net>
wrote:
Just to add, other respondents have perhaps assumed that the problem
is just in installing a run time app on machines with other versions
of Office. My warning is that there will be trouble ahead when users
install newer versions of Office and you are off the scene, You can't
be sure how they will manage the new installation.
David

Nov 13 '05 #7

P: n/a
d.***************@blueyonder.co.uk (David Schofield) wrote:
Just to add, other respondents have perhaps assumed that the problem
is just in installing a run time app on machines with other versions
of Office. My warning is that there will be trouble ahead when users
install newer versions of Office and you are off the scene, You can't
be sure how they will manage the new installation.


Good point. www.sagekey.com handles that.

I'd clarify that a bit to see if they install a newer version of Office Pro which
includes Access.

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
Nov 13 '05 #8

This discussion thread is closed

Replies have been disabled for this discussion.