Ok I have searched the MS website for info on this. I am totally
confused.
If I want to deploy an Access 2003 app and allow my users to run it
using Access 2003 Runtime, where do I get the Runtime?
I just purchased Office 2003 Professional. Is Access 2003 Runtime
included with that or not?
It APPEARS that the only way I can get Access 2003 Runtime is to
purchase Microsoft Visual Studio. Is that correct? If so, I am
screwed big time.
So, this leaves me with another question: If I leave our Access 2000
app in 2000 format, avoid use Access 2003 to continue development and
upgrades but avoid incorporating any Access 2003 specific features,
will my users be able to continue using Access 2000 Runtime to run the
app?
All help much appreciated.
-LW
10  2949 
I'm not surprised you're confused - it's confusing.
Currently the only way to get your hands on the Access 2003 run-time
executable is on the Office Professional 2003 CD. There's an install file and
a cab file hidden in a folder somewhere like English\ACCRT. That's the file,
but not the permission to deploy it. For permission to deploy, you need to
purchase the "Microsoft Visual Studio Tools for the Microsoft Office System".
So, in a nutshell - to deploy an Access 2003 Runtime application, you must own
both Office Professional 2003 (or just Access 2003) and the "Microsoft Visual
Studio Tools for the Microsoft Office System".
Yes, they probably could have thought of a shorter name - I guess we could
always call it MSVSTFTMOS for short. Hey - TANSTAAFL.
On Mon, 11 Apr 2005 00:58:50 -0500, Lauren Wilson <pr*****@private.com> wrote: Ok I have searched the MS website for info on this. I am totally
confused.
If I want to deploy an Access 2003 app and allow my users to run it
using Access 2003 Runtime, where do I get the Runtime?
I just purchased Office 2003 Professional. Is Access 2003 Runtime
included with that or not?
It APPEARS that the only way I can get Access 2003 Runtime is to
purchase Microsoft Visual Studio. Is that correct? If so, I am
screwed big time.
So, this leaves me with another question: If I leave our Access 2000
app in 2000 format, avoid use Access 2003 to continue development and
upgrades but avoid incorporating any Access 2003 specific features,
will my users be able to continue using Access 2000 Runtime to run the
app?
All help much appreciated.
-LW
Well that bites. That runtime thing is the basis of *ALL* the applications
in our organization. What do you do? Just go with the flow and quit
developing in access, and start developing in VB straight-up? Access has
some real advantages as far as ease of use for my users, they don't have to
know SQL or anything. It's good for me, I develop in it, I know they can't
get in there and screw with it. I know they couldn't with a compiled VB app
either, but that isn't the point. I'm just used to doing it this way, and I
don't see why Microsoft has to go tacking more costly stuff on top of what
we already need. To Microsoft, the megolith, More is More, to me, the
humble programmer with limited resources, Less is More!
Anything I wanted to do I could have done with Access 97. maybe we should
have stayed there!
-B
"Steve Jorgensen" <no****@nospam.nospam> wrote in message
news:2h********************************@4ax.com... I'm not surprised you're confused - it's confusing.
Currently the only way to get your hands on the Access 2003 run-time
executable is on the Office Professional 2003 CD. There's an install file
and
a cab file hidden in a folder somewhere like English\ACCRT. That's the
file,
but not the permission to deploy it. For permission to deploy, you need
to
purchase the "Microsoft Visual Studio Tools for the Microsoft Office
System".
So, in a nutshell - to deploy an Access 2003 Runtime application, you must
own
both Office Professional 2003 (or just Access 2003) and the "Microsoft
Visual
Studio Tools for the Microsoft Office System".
Yes, they probably could have thought of a shorter name - I guess we could
always call it MSVSTFTMOS for short. Hey - TANSTAAFL.
On Mon, 11 Apr 2005 00:58:50 -0500, Lauren Wilson <pr*****@private.com>
wrote:
Ok I have searched the MS website for info on this. I am totally
confused.
If I want to deploy an Access 2003 app and allow my users to run it
using Access 2003 Runtime, where do I get the Runtime?
I just purchased Office 2003 Professional. Is Access 2003 Runtime
included with that or not?
It APPEARS that the only way I can get Access 2003 Runtime is to
purchase Microsoft Visual Studio. Is that correct? If so, I am
screwed big time.
So, this leaves me with another question: If I leave our Access 2000
app in 2000 format, avoid use Access 2003 to continue development and
upgrades but avoid incorporating any Access 2003 specific features,
will my users be able to continue using Access 2000 Runtime to run the
app?
All help much appreciated.
-LW
I don't understand your concern.
Access 2003 HAS a runtime. As Steve pointed out, you need to purchase the
following in order to create an Access 2003 runtime application:
- Microsoft Access 2003
- Visual Studio Tools for Office 2003 (which includes the Access 2003
Developer Extensions)
The ADE is the product that gives you the license to deploy the 2003 runtime
components and you have to have Access 2003 installed in order to install
the ADE.
If you're using MSDN, note that while VSTO is available in all subscription
levels of MSDN, the Access Developer Extensions are not included with all
versions. ADE is only available at Universal level.
The stand-alone VSTO box includes both VSTO and the ADE.
See http://msdn.microsoft.com/vstudio/of...ficetools.aspx for more
details
--
Doug Steele, Microsoft Access MVP http://I.Am/DougSteele
(no e-mails, please!)
"ng" <ng@ng.com> wrote in message news:Row6e.9719$H_5.9459@trnddc01... Well that bites. That runtime thing is the basis of *ALL* the
applications in our organization. What do you do? Just go with the flow
and quit developing in access, and start developing in VB straight-up?
Access has some real advantages as far as ease of use for my users, they
don't have to know SQL or anything. It's good for me, I develop in it, I
know they can't get in there and screw with it. I know they couldn't with
a compiled VB app either, but that isn't the point. I'm just used to
doing it this way, and I don't see why Microsoft has to go tacking more
costly stuff on top of what we already need. To Microsoft, the megolith,
More is More, to me, the humble programmer with limited resources, Less is
More!
Anything I wanted to do I could have done with Access 97. maybe we should
have stayed there!
-B
"Steve Jorgensen" <no****@nospam.nospam> wrote in message
news:2h********************************@4ax.com... I'm not surprised you're confused - it's confusing.
Currently the only way to get your hands on the Access 2003 run-time
executable is on the Office Professional 2003 CD. There's an install
file and
a cab file hidden in a folder somewhere like English\ACCRT. That's the
file,
but not the permission to deploy it. For permission to deploy, you need
to
purchase the "Microsoft Visual Studio Tools for the Microsoft Office
System".
So, in a nutshell - to deploy an Access 2003 Runtime application, you
must own
both Office Professional 2003 (or just Access 2003) and the "Microsoft
Visual
Studio Tools for the Microsoft Office System".
Yes, they probably could have thought of a shorter name - I guess we
could
always call it MSVSTFTMOS for short. Hey - TANSTAAFL.
On Mon, 11 Apr 2005 00:58:50 -0500, Lauren Wilson <pr*****@private.com>
wrote:
Ok I have searched the MS website for info on this. I am totally
confused.
If I want to deploy an Access 2003 app and allow my users to run it
using Access 2003 Runtime, where do I get the Runtime?
I just purchased Office 2003 Professional. Is Access 2003 Runtime
included with that or not?
It APPEARS that the only way I can get Access 2003 Runtime is to
purchase Microsoft Visual Studio. Is that correct? If so, I am
screwed big time.
So, this leaves me with another question: If I leave our Access 2000
app in 2000 format, avoid use Access 2003 to continue development and
upgrades but avoid incorporating any Access 2003 specific features,
will my users be able to continue using Access 2000 Runtime to run the
app?
All help much appreciated.
-LW
So, this STILL leaves me with another question: If I leave our Access
2000 app in 2000 format, use Access 2003 to continue development and
upgrades but avoid incorporating any Access 2003 specific features,
will my users be able to continue using Access 2000 Runtime to run the
app?
On Mon, 11 Apr 2005 19:24:56 -0400, "Douglas J. Steele"
<NOSPAM_djsteele@NOSPAM_canada.com> wrote: I don't understand your concern.
Access 2003 HAS a runtime. As Steve pointed out, you need to purchase the
following in order to create an Access 2003 runtime application:
- Microsoft Access 2003
- Visual Studio Tools for Office 2003 (which includes the Access 2003
Developer Extensions)
The ADE is the product that gives you the license to deploy the 2003 runtime
components and you have to have Access 2003 installed in order to install
the ADE.
If you're using MSDN, note that while VSTO is available in all subscription
levels of MSDN, the Access Developer Extensions are not included with all
versions. ADE is only available at Universal level.
The stand-alone VSTO box includes both VSTO and the ADE.
See http://msdn.microsoft.com/vstudio/of...ficetools.aspx for more
details
Yes.
On Mon, 11 Apr 2005 22:14:36 -0500, Lauren Wilson <pr*****@private.com> wrote:
So, this STILL leaves me with another question: If I leave our Access
2000 app in 2000 format, use Access 2003 to continue development and
upgrades but avoid incorporating any Access 2003 specific features,
will my users be able to continue using Access 2000 Runtime to run the
app?
On Mon, 11 Apr 2005 19:24:56 -0400, "Douglas J. Steele"
<NOSPAM_djsteele@NOSPAM_canada.com> wrote:
I don't understand your concern.
Access 2003 HAS a runtime. As Steve pointed out, you need to purchase the
following in order to create an Access 2003 runtime application:
- Microsoft Access 2003
- Visual Studio Tools for Office 2003 (which includes the Access 2003
Developer Extensions)
The ADE is the product that gives you the license to deploy the 2003 runtime
components and you have to have Access 2003 installed in order to install
the ADE.
If you're using MSDN, note that while VSTO is available in all subscription
levels of MSDN, the Access Developer Extensions are not included with all
versions. ADE is only available at Universal level.
The stand-alone VSTO box includes both VSTO and the ADE.
See http://msdn.microsoft.com/vstudio/of...ficetools.aspx for more
details
Lauren Wilson wrote: So, this STILL leaves me with another question: If I leave our Access
2000 app in 2000 format, use Access 2003 to continue development and
upgrades but avoid incorporating any Access 2003 specific features,
will my users be able to continue using Access 2000 Runtime to run the
app?
Yes, that should be fine.
Personally I've had problems with using A2003 to modify an A2000 ADP
application..... it keeps corrupting it on me :(
Br@dley
On Tue, 12 Apr 2005 03:52:58 GMT, "Br@dley" <no*****@4u.com> wrote: Lauren Wilson wrote: So, this STILL leaves me with another question: If I leave our Access
2000 app in 2000 format, use Access 2003 to continue development and
upgrades but avoid incorporating any Access 2003 specific features,
will my users be able to continue using Access 2000 Runtime to run the
app?
Yes, that should be fine.
Personally I've had problems with using A2003 to modify an A2000 ADP
application..... it keeps corrupting it on me :(
Br@dley
Make sure you're using the latest A2K3 service pack. It helps that problem
very noticeably.
Steve Jorgensen wrote: On Tue, 12 Apr 2005 03:52:58 GMT, "Br@dley" <no*****@4u.com> wrote:
Lauren Wilson wrote: So, this STILL leaves me with another question: If I leave our
Access 2000 app in 2000 format, use Access 2003 to continue
development and upgrades but avoid incorporating any Access 2003
specific features, will my users be able to continue using Access
2000 Runtime to run the app?
Yes, that should be fine.
Personally I've had problems with using A2003 to modify an A2000 ADP
application..... it keeps corrupting it on me :(
Br@dley
Make sure you're using the latest A2K3 service pack. It helps that
problem very noticeably.
I'm pretty sure I have the latest updates of everything....incl.
A2003sp1
Br@dley
Lauren Wilson wrote: So, this STILL leaves me with another question: If I leave our Access
2000 app in 2000 format, use Access 2003 to continue development and
upgrades but avoid incorporating any Access 2003 specific features,
will my users be able to continue using Access 2000 Runtime to run the
app?
If you normally distribute an MDE you will still need a copy of Access 2000 to
create that. Access 2003 can only create an MDE in the newer 2002/2003 format
which would not work for your users with the 2000 runtime.
--
I don't check the Email account attached
to this message. Send instead to...
RBrandt at Hunter dot com
On Tue, 12 Apr 2005 11:42:57 GMT, "Rick Brandt"
<ri*********@hotmail.com> wrote: Lauren Wilson wrote: So, this STILL leaves me with another question: If I leave our Access
2000 app in 2000 format, use Access 2003 to continue development and
upgrades but avoid incorporating any Access 2003 specific features,
will my users be able to continue using Access 2000 Runtime to run the
app?
If you normally distribute an MDE you will still need a copy of Access 2000 to
create that. Access 2003 can only create an MDE in the newer 2002/2003 format
which would not work for your users with the 2000 runtime.
This is straight from the Great Big Book of DAMN! What on earth is
Microsoft trying to do by placing a new obstacle to MDE distribution?
I think it's time to accelerate our plans to move this entire 5 year
old, 10,000 user base app to a non-Microsoft platform. This thread has been closed and replies have been disabled. Please start a new discussion. Similar topics
by: Brian Loesgen |
last post by:
The next San Diego .Net User Group meeting is Tuesday, November 25,
2003 at the Scripps Ranch Library.
Scripps Ranch Library
10301 Scripps Lake Drive
San Diego, CA 92131-1026
Please join us...
|
by: Colin Chudyk |
last post by:
Hi,
Here is my situation. Can anyone provide insight?
I have developed a database in Access 2002. I am planning to distribute it
as a split MDE (front) / MDB (back) to be used by the Access...
|
by: Mike |
last post by:
Hi
Hi
We are currently upgrading from access 97 to office 2003 on site. We
would like to upgrade our access databases to Access 2003 but we wish
to remove Microsoft access software from our end...
|
by: Simple Man |
last post by:
We have a citrix server that users will be signing into from a remote
location. One application is an Access database. Right now, lan users
are using the Access 2003 runtime to run these...
|
by: Wayne |
last post by:
I am looking at installing an Access 2003 application on some machines
that don't have any version of Access previously installed. After
reading lots of posts on this group and elsewhere I assume...
|
by: Jordan S. |
last post by:
SQL Server will be used as the back-end database to a non trivial client
application.
In question is the choice of client application:
I need to be able to speak intelligently about when one...
|
by: Mell via AccessMonster.com |
last post by:
I created databases on Access 2003 and I want to deploy them to users. My
code was also done using 2003.
If they have Ms Access 2000 or higher, will they be able to use these dbs
with all code,...
|
by: boyleyc |
last post by:
Hi all
the following code works perfectly well. Basically it populates a
series of check boxes on my form, depending on whether dlookup finds an
associated record.
The problem i have is that...
|
by: Paul H |
last post by:
As I understand it, to distribute a runtime version of Access 2003 with my
app I need to spend £600 on "Visual Studio Tools for Office System package"
which contains the RT plus a load of stuff I...
|
by: lllomh |
last post by:
Define the method first
this.state = {
buttonBackgroundColor: 'green',
isBlinking: false, // A new status is added to identify whether the button is blinking or not
}
autoStart=()=>{
|
by: DJRhino |
last post by:
Was curious if anyone else was having this same issue or not....
I was just Up/Down graded to windows 11 and now my access combo boxes are not acting right. With win 10 I could start typing...
|
by: isladogs |
last post by:
The next Access Europe meeting will be on Wednesday 4 Oct 2023 starting at 18:00 UK time (6PM UTC+1) and finishing at about 19:15 (7.15PM)
The start time is equivalent to 19:00 (7PM) in Central...
|
by: Aliciasmith |
last post by:
In an age dominated by smartphones, having a mobile app for your business is no longer an option; it's a necessity. Whether you're a startup or an established enterprise, finding the right mobile app...
|
by: tracyyun |
last post by:
Hello everyone,
I have a question and would like some advice on network connectivity. I have one computer connected to my router via WiFi, but I have two other computers that I want to be able to...
|
by: giovanniandrean |
last post by:
The energy model is structured as follows and uses excel sheets to give input data:
1-Utility.py contains all the functions needed to calculate the variables and other minor things (mentions...
|
by: Teri B |
last post by:
Hi, I have created a sub-form Roles. In my course form the user selects the roles assigned to the course.
0ne-to-many. One course many roles.
Then I created a report based on the Course form and...
|
by: isladogs |
last post by:
The next Access Europe meeting will be on Wednesday 1 Nov 2023 starting at 18:00 UK time (6PM UTC) and finishing at about 19:15 (7.15PM)
Please note that the UK and Europe revert to winter time on...
|
by: GKJR |
last post by:
Does anyone have a recommendation to build a standalone application to replace an Access database? I have my bookkeeping software I developed in Access that I would like to make available to other...
| |
