Can I run Access without having Office?
- Thread starter casey
- Start date
ElsVanMiert
Registered User.
- Local time
- Today, 01:03
- Joined
- Dec 14, 2000
- Messages
- 152
Overview about runtime issues
ACCESS ONLINE ENCYCLOPEDIA www.unsoftwareag.com
Article Code: D1
Runtime issues: an overview
Transforming MDB files into EXE files
It is definitely not possible to transform a MDB- or MDE-file into an executable file since the MDB and MDE-files contain dynamic data such as tables.
The runtime version of Access can open any MDB and MDE file. It is (nearly) identical with the full version except that the database window is inaccessible, database objects can only be created and modified by code and you need a navigation system that is based on forms.
Furthermore, some functions are not available in the Runtime version such as the "Filter by Form" feature.
The runtime version is sold in the so-called "Developer Edition" and its license agreement allows ACCESS developers to distribute it freely with their custom applications.
Upgrading issues: A97 Developer Edition vs MOD-2000
The MS Access 97 Developer Edition is no longer on sale. You might find a "used" copy, but it is quite difficult because of the MS licence agreements: mainly purchased by professional Access developers, the A2K-Developer-Update-licence REPLACES (!) the A97-licence.
Update purchasers are not allowed to sell their A97-Developer-Edition and most are not interested since they often have customers with A97-applications still running.
Necessary disk space
The runtime files occupy more than 150 MB of disk space (since IE5 is included and installed automatically, these files can not be suppressed).
Consequently, you need to distribute your application on CD-ROM. There is a patch (minimal version) available at the MS download center that reduces the necessary disk space to 70 MB (IE 5 is replaced by IE 3.4), but even if you use the minimal version CD-ROM deployment is inevitable. Furthermore, the minimized version lacks several functions.
The Package and Deployment Wizard
All ACCESS applications require a certain number of files. The minimum case scenario is one single MDB or MDE file, but in general applications are more complex: activated security systems require MDW files and startup shortcuts, language or training versions work with several backend files, special folder structures are necessary as well as fonts, icon files, shortcuts, ActiveX elements, wizards, CHM files, sound and graphic files...
The complete folder and file structure needs to be managed by a special installer program. MS delivers the so-called "Package and Deployment Wizard" aka PDW with the Developer Edition.
Unfortunately, the PDW is not very confortable to work with, its functions are limited and it is extremely inflexible.
Even its activation is tricky:
After the installation of the PDW on your hard disk you will not find it in ACCESS' list of add-ons! You first need to open the VB-Editor window and activate the PDW.
The reason is the fact that the PDW has not been designed for ACCESS 2000 but for Visual Basic 6! This explains why a part of the functions that do not work with the deployment of applications (no shortcuts or ICO-Files, often the keyboard-language changes automatically from non-english languages like Danish and Dutch to English and so on.
Lots of professional ACCESS developers replace the PDW a more performant installer. You will find the MDT-2000 installer on our PowerUps! page. MDT-2000 is the only installer on the market that has been designed specifically for ACCESS 2000.
ACCESS ONLINE ENCYCLOPEDIA www.unsoftwareag.com
Article Code: D1
Runtime issues: an overview
Transforming MDB files into EXE files
It is definitely not possible to transform a MDB- or MDE-file into an executable file since the MDB and MDE-files contain dynamic data such as tables.
The runtime version of Access can open any MDB and MDE file. It is (nearly) identical with the full version except that the database window is inaccessible, database objects can only be created and modified by code and you need a navigation system that is based on forms.
Furthermore, some functions are not available in the Runtime version such as the "Filter by Form" feature.
The runtime version is sold in the so-called "Developer Edition" and its license agreement allows ACCESS developers to distribute it freely with their custom applications.
Upgrading issues: A97 Developer Edition vs MOD-2000
The MS Access 97 Developer Edition is no longer on sale. You might find a "used" copy, but it is quite difficult because of the MS licence agreements: mainly purchased by professional Access developers, the A2K-Developer-Update-licence REPLACES (!) the A97-licence.
Update purchasers are not allowed to sell their A97-Developer-Edition and most are not interested since they often have customers with A97-applications still running.
Necessary disk space
The runtime files occupy more than 150 MB of disk space (since IE5 is included and installed automatically, these files can not be suppressed).
Consequently, you need to distribute your application on CD-ROM. There is a patch (minimal version) available at the MS download center that reduces the necessary disk space to 70 MB (IE 5 is replaced by IE 3.4), but even if you use the minimal version CD-ROM deployment is inevitable. Furthermore, the minimized version lacks several functions.
The Package and Deployment Wizard
All ACCESS applications require a certain number of files. The minimum case scenario is one single MDB or MDE file, but in general applications are more complex: activated security systems require MDW files and startup shortcuts, language or training versions work with several backend files, special folder structures are necessary as well as fonts, icon files, shortcuts, ActiveX elements, wizards, CHM files, sound and graphic files...
The complete folder and file structure needs to be managed by a special installer program. MS delivers the so-called "Package and Deployment Wizard" aka PDW with the Developer Edition.
Unfortunately, the PDW is not very confortable to work with, its functions are limited and it is extremely inflexible.
Even its activation is tricky:
After the installation of the PDW on your hard disk you will not find it in ACCESS' list of add-ons! You first need to open the VB-Editor window and activate the PDW.
The reason is the fact that the PDW has not been designed for ACCESS 2000 but for Visual Basic 6! This explains why a part of the functions that do not work with the deployment of applications (no shortcuts or ICO-Files, often the keyboard-language changes automatically from non-english languages like Danish and Dutch to English and so on.
Lots of professional ACCESS developers replace the PDW a more performant installer. You will find the MDT-2000 installer on our PowerUps! page. MDT-2000 is the only installer on the market that has been designed specifically for ACCESS 2000.
ghudson
Registered User.
- Local time
- Yesterday, 20:03
- Joined
- Jun 8, 2002
- Messages
- 6,193
Is the PDW version for Access XP more user friendly that the 2K version?
Also, the SetUp wizard I use for Access 97 is very easy to use and I just counted the files I need in a typical installation and it only has 57 files that total 18 megabytes (I am not including my db and related files) in the setup package. The only part I do not like is that the installation shortcuts are installed in the users profile folder (not All Users) on Windows XP computers.
Thanks!
Also, the SetUp wizard I use for Access 97 is very easy to use and I just counted the files I need in a typical installation and it only has 57 files that total 18 megabytes (I am not including my db and related files) in the setup package. The only part I do not like is that the installation shortcuts are installed in the users profile folder (not All Users) on Windows XP computers.
Thanks!
Similar threads
