Ray said:
Can anyone tell me if installs made using these extensions will run on
older
O/S such as Win98/2000?
I think you complete miss-understood how the runtime works. The runtime
system is essentially the same as the full version except that you can NOT
design forms and code etc.
What this means is that all of the same problems of installing multiple
versions of ms-access on the same machine exist. What this means is that if
you install two versions of ms-access on the same machine, then both
installs will be fighting over the mdb/mde file extension. None of this
information should be a surprise to you if you realize that the runtime
behaves the SAME as the full version. Once you are armed with this
knowledge, then any question you have about what machine the runtime works
on can be answered by asking what version ms-access can run on what machine.
same thing = same problems.
So, I just wanted to get the above out of the way, since you were asking
does the runtime install on previous versions of windows:
answer: same thing = same restrictions.
So, the last version of office that installed on window 9x was office 2002.
So, for example, the runtime for a2003 will not install on window 98, since
office 2003 does not install on windows 98. So, as I said, there is NOT a
difference in terms of how the runtime for access installs and behaviours as
compared to the full versions. Every ting, and every problem remains
identical..
I have older versions developed and deployed with Access 20000 developer
Ah, ok...the above version will work on windows 98, and windows 2000, and
windows xp, and windows vista....
What is stopping you from continue to use the a2000 dev system then???
edition and am now faced with buying the VB Toolks for Access
You only need the developer edition if you plan to create new installs for
that older software. You do realize what I said above??? There is NO
special connection between a mde, or mdb file, and that of installing the
runtime (or the developer tools). They are complete separate. If you install
the runtime, then you can freely copy a mde (or mdb) to that target
computer. So, it not clear why you need the a2000 developer edition here?
You don't need the developers edition to build updates. You just modify the
mdb, and then create a mde..and email that to the customer. What is
stopping you here? (I must be missing something in your explain here). You
can install using the a2000 runtime you have now, and then for updates, or
new versions..you simply supply the mde (you don't need the developer tools
to make that mde or deploy it to your users).
(over $1000
here in Canuck land) or waitinf for the free extensions and getting an
Access
upgrade.
Which version you talking about? As far as I can tell, you don't need to
purchase anything. Perhaps you are looking for the a2000 runtime. As far as
I know, it not available anymore. The only one available right now is a2003.
As I explained, the a2003 runtime is the same as ms-access 2003, and it will
not install on pre windows 2000 boxes (same as full version...). And, by
the way, you can't install office 2000 on windows 3.1, or DOS either.
However, all of those access versions..going back to windows 3.1 can be
installed on a brand new vista box. So, as always, for the last 20 years I
can remember....we can useably move forward easy, but not backwards (since
new versions start to use features that don't exits on previous os). For
example, you can't install access 2.0 which ran on windows 3.1 on a previous
pc running DOS 6.2. (since DOS did not really even use a mouse or have a
graphical interface). However, that 15+ year old version of ms-access will
install and run fine on a new box today.
Personally I find it confusing that they still want $1,000 for something
old
that they are now giving away free.
Gee, I thought that how software always worked! You add things that people
were willing to pay for into the next verson. For example, in a2000, we did
not have a printer object, and it was painful to switch printers. In a2002,
we now have a printer object, and don't have to write, or purchase software
that allows printer switching..since it is built in. In a2003, we got the
ability to change the font in the zoom box, and also in the sql viewer. And,
context help now works while you in the sql view. And, we also got some XML
import stuff for a2003. So, I always thought that the whole idea of the next
version was to provide new features, and dangle somthing that makes us want
to upgrade.
In office 2007, we now have pdf creating ability. Again, we used to have to
purchase that stuff. I not really much surprised (or confused as you say)
that over time, the next version has all kinds of new features and things
that previous cost extra. I actually kind of though that getting extra
features was a incentive for users to upgrade. So, now we get the runtime as
included, and that is a nice gift horse for sure!!!
Perhaps I missed something, and you actually do need the a2000 runtime. I
don't believe the a2000 runtime can be purchased from MS now anyway. You can
purchase full copies of access 2003 for $109 US (upgrade price). Hence,
ms-access is rather cheap and low cost. I suppose if you are deploying more
then 10 copies, then purchasing the developer extensions for a2003 would
make sense. However, as mentioned, office 2002 was the last version that
installed on pre 2000 boxes, and this will not solve your win98 deployment
problems.
Why not just install the software you have now...and then deploy a new
mde/mdb for that install? As I said before, the way the runtime works is
that you install the runtime, and then any old mdb, or mde placed on the
machine will run (you just double click on that mdb file...and access will
launch -- there is NO special connection of any type between the runtime,
and the mdb/mde deplyed with the runtime). So, I not really sure why you
need the a2000 developer tools when you already have a install built???
Nothing stops you from supply a new updated mde in this case.
I suppose if you must create ** NEW ** packages for a2000 runtime, and
somehow don't have the 2000 developer tools, then I can start to see your
problem. If you need win98 ability, the you can't go beyond a2002. It not
clear if you trying to modify existing versions of the runtime install, or
build NEW installs. (note that the a2000 developer tools will not let you
modify your runtime install scripts unless you have the original configs).
So, to modify the current applications you have you will still need all of
the source files (the original mdb, and the config/set files made by the
package wizard). So, to be 100% clear, the developer tools ONLY gives you
the runtime, and nothing special occurs to the mdb, or mde with the
developer tools (those mdb/mde simply just get copied to the target
machines).
You can consider purchasing office 2007, and get the runtime tools for free.
You would still need ms-access 2007. If we follow past history, it the
release time frame for the runtime follows some months after the full
version realise. mid Summer to fall is a good guess as for the release
time...
however, if you must support win98 boxes...then you stuck using a2000 as you
have.....
