Runtime

M

Mike Revis

Hi Group,
I have been using Office XP Developer to make runtime versions of my
database. Access 2000.

For some reason I have purchased Office Pro 2003.

If I start using Access 2003 will I be able to use the XP developer to make
runtime versions? If not it seems that I will have to get Visual Studio.
Actually that's a question.

If I get Visual Studio 2007 will I be able to make runtime versions of
Access 2003 or do I need to find an older version of Visual Studio?

As always, any thoughts, suggestions or comments are welcome.

Mike
 
A

Albert D. Kallal

Mike Revis said:
Hi Group,
I have been using Office XP Developer to make runtime versions of my
database. Access 2000.

For some reason I have purchased Office Pro 2003.

If I start using Access 2003 will I be able to use the XP developer to
make runtime versions?

No, the runtime works with the same version of MS access, and I think going
back to early 90's, each version of ms-access was always paired to the same
"runtime". So, no, you really can't mix and max verisons.

However, I have heard that the a2003 runtime will consume a mde made from
a2000-a2003. So in some instances you can use a later version (runtime) to
deploy new something that perhaps was created in an earlier version. For the
most part xp and 2003 do use the same file format, so, you might actually be
able to create a mde/mdb in access 2003, and then throw it on sheer machine
and package it with the xp version of ms-access (however, I see little
reason upgrade from access 2002 (xp) to access 2003 if you already have
access 2002.

I suspect that you realize the runtime has no particular connection between
the actual mdb file that you deploy on that machine. In other words once the
runtime is installed, you can copy any particular access file to that
machine (mdb, or mde), and simply double click on that it to launch it.
There is no real speical connection between the runtime and the mde/mdb file
you deploy. However, as a general rule you've always had to pair the version
of MS access with a version of the application you're running, and this rule
does not really change a whole lot for the runtime, or the full version.
If not it seems that I will have to get Visual Studio. Actually that's a
question.

Actually purchasing visual studio will not get to the access runtime tools.
In the case of access 2003, you have to specifically purchased visual studio
tools for office (VSTO). And when you purchase this, you you're not required
to install any part of visual studio, or purchase visual studio at all to
get the runtime and package wizard system.
If I get Visual Studio 2007 will I be able to make runtime versions of
Access 2003 or do I need to find an older version of Visual Studio?

For access 2007, the access runtime system is a completely 100% free
download now, and you don't have to purchase anything. So, the answer here
is no, Visual Studio 2007, or Visual Studio 2003 does not help you here, and
it never did in the past.
As always, any thoughts, suggestions or comments are welcome.

Access 2007 is nice, since the runtime + package wizard system is free now.
 
M

Mike Revis

Thank you Albert.
In light of all that I think I will just stick with xp for now.
It has been working just fine and I don't know why I would want to change.

Regards
Mike
 
T

Tony Toews [MVP]

Albert D. Kallal said:
However, I have heard that the a2003 runtime will consume a mde made from
a2000-a2003.

I'm currently doing that right now. Developing in A2003. Creating
the MDE in A2000. Distributing the runtime using A2003. I'm doing
this as I still have some clients running A2000 runtime.

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/
 
T

Tony Toews [MVP]

Mike Revis said:
In light of all that I think I will just stick with xp for now.
It has been working just fine and I don't know why I would want to change.

Security patches are my biggest concern. If there's a vulnerability
will a patch for Access be available from Microsoft?

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/
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top