runtime version of database for distribution

[bert5g]

I am currently using Access 2002 to create a database for distribution to persons who will not be running Access. Since I am new to this I was wondering what developer tools I would need and the approximate cost. I am somewhat experienced with Access but have never created a runtime version. Is this difficult to do? Are there people who will package the application for me but allow me to retain distribution rights? Thanks,
Al
NJ

 

[lupins46]

It's pretty much all bad news I'm afraid.

For OfficeXP, to get the licence to distribute the Access runtime you must buy the Developer Edition of OfficeXP. This is includes a full copy of OfficeXP as well as the developer tools. Assuming you still want to do this, your next problem is finding a copy to buy.

The developer tools include a Package and distribution wizard which will build an installation package for your Access application (including the access runtime). However, it is very hit and miss as to whether this will install on your target machine. If you can guarantee the consistent configuration of your target population then you can use a reference machine to test and fix the installation. It should then install on your target machines.

But if you are planning to distribute to 'unknown' user machines then you will not be successful with the P&D wizard because it has practically no ability to adapt to different configs.

There are tools from Wise (installer) and Sagekey ( installation scripts) which aim to provide a proper Access runtime installation package - I have never used them but they are reported as being successful. Note that you must still get the license to distribute from the OfficeXP developer edition in this case.

I have never heard of any 'distribution package' service companies, but it's not something I've ever looked for, so other posters may have info.

 

[AJN2004]

lupins46 is pretty much correct in what he says with the exception of the installation difficulties.

I develop and distribute Access programs myself and have used both the Office XP developer and the newer Access 2003 Developer Extensions. If you set the install path to, let's say "C:\Programms\MYProgramm\" then your program should let itself install on all machines without any problem. Only drawback that I can think of is with older versions of the Windows installer.

I haven't used the XP developer for a while, but I think I'm right in saying that the user can also select where he/she wants the program installed (with 2003 Dev. this is the case). The program will then be installed in the chosen directory with all libraries and files.

Where you might encounter difficulties is with macro security. Any program that has macros and or Visual Basic code that is to be opened with Office 2002 will result in warnings about macro security that the user first has to answer before the program starts. This can be combated in that you update all machines with the newest JET Database and MDAC (both available on the MS download page). Depending on your network security you may have to digitally sign your program.

If your program is intended to be multi user then consider creating a client/server database (front end – backend). In the front end you will place your forms, queries, reports etc., the back end holds the tables for your database. Initially you can create just one db with all objects, once you're happy with the design simply export your tables into a new db and place this db on your server. By using the table linking assistant you can link your front end to the back end. One more point, you must set the front end db to share in the options dialog. The front end db is the one that you will distribute.

Have a look at the Microsoft Knowledge Base for the developer and multi user db's, you should find enough information to help you in your decisions.

hth

 

[bert5g]

---not all bad news. I will keep all in mind as I decide my next step. I had not considered problems with the macro's and VB script during installation. Thanks for the insight.
Al--NJ