Re: Access Runtime

Good Morning and Hi to all my readers.
First of all I’d like to thank everybody for their contributions and agree
that there are many ways, some simple, some elegant and all quite practical
to change/update a clients file.
However I think, with all due respect to all that there is a point that is
being missed which is as follows:
Microsoft have provided as part of their customer support a tool, namely
‘Access 2007 Developer Extensions and Runtime’ that I believe from my
experience does NOT function as the support documentation seem to indicates.
Yes it does a very good job of packaging an Access Database including adding
subdirectories where the BE and Backup of the BE can be safely stored, but it
does not seem permit me, the originator (unless I’m doing something wrong) to
distribute an upgraded FE. (What do you mean the car will only go round left
hand corners.)
With regard to comment with lots of VERYs in it, firstly, if you try to run
the original setup it tells you that the application is already installed and
that it must be uninstalled before you can reinstall (who would do that, the
client must have some responsibility for their actions). And secondly when
you create the updated setup you only include the files/applications that you
want update and NOT the data or backup files.
So back to my original questions.
My thanks to all.

--
Still trying


"J_Goddard via AccessMonster.com" wrote:

Hi All -

In the above discussion, is it not assumed that the FE and the BE (Data) are
in separate database files? What happens if they are in the same file?

John



Albert D. Kallal wrote:
Thanks Rick I'll try your solution it may work in the short term, but the
question still remains why carn't I do it through the Package Wizard when
all
microsofts documentation indicated that I can?

I not sure where that been indicated, but you do realize that is a VERY VERY
VERY VERY VERY VERY VERY good thing that you find it difficult to overwrite
a database file with the wizard. I don't think it takes MUCH imagination on
your part as to the cries of people accidentally inserting their install
disk and it overwrites their data. Heck, just accident running that install
disk in the drive should NOT overwrite your data files. The cries and even
perhaps lawsuits would ensure if a simply install could overwrite the data
files.

Reading your responces though I realise that I referes to the file
extension
incorrectly in my reply to Douglas I should have written .ACCDR and not
.ACCDE.

The "r" extension is not really needed, and all it does is save you using
the /runtime switch in your startup shortcut. I would suggest you use
WinZip, or as mentioned something free like "inno" to update the front end.

Keep in mind there is NO special connection between the runtime and your
accDE file that you distribute to your users. Get the runtime installed (I
usually just package a .txt file). From that point on, updates are a simple
file copy...and I usually use the free inno installer for this....

here is what a inno script looks like:

; SEE THE DOCUMENTATION FOR DETAILS ON CREATING .ISS SCRIPT FILES!

[Setup]
SourceDir=c:\Documents and Settings\All Users\Application Data\RidesL
AppName=Rides Reservation System
AppVerName= Rides 2.0
DefaultDirName={commonappdata}\RidesL
DefaultGroupName=Rides
Compression=lzma
SolidCompression=yes

DirExistsWarning=no
DisableDirPage=yes
DisableProgramGroupPage=yes
Uninstallable=no

[Files]
Source: "RidesXP.mde"; DestDir: "{app}"
Source: "Rides.ico" ; DestDir: "{app}"
Source: "RidesXP.bmp" ; DestDir: "{app}"

*----------------------------

the nice advantage of this system is you get a SINGLE .exe file for the
above install. This means you can use a web link for updates, and with about
one line of code, your users can have the following type of update for their
software:

http://www.kallal.ca/ridestutorialp/upgrade.html

The above install screens are how my ms-access users update their software,
and the screens are what the above script produces....


--
John Goddard
Ottawa, ON Canada
jrgoddard at cyberus dot ca

Message posted via http://www.accessmonster.com


.

Relevant Pages

  • Re: Overwrite the O/S ?
    ... > Can I overwrite O/S, AIX 4.3.3 using the preservation option when I do a ... 'preservation install' is misleading. ... You might fake the pad string to make the install ...
    (comp.unix.aix)
  • Re: Interesting activeX problem / solution
    ... Version branching ... By forcing an overwrite you are risking breaking software on peoples ... ipworks4.dll (proprietary e-mail add-in for direct e-mailing in the ... and if there are dangers of having my install always overwrite. ...
    (comp.databases.ms-access)
  • Re: Deploying Access 2007 Runtime / developer extensions / basic MSI installer questions
    ... Sagekey script won't have that feature. ... overwrite, or never overwrite, unless I'm missing something. ... option during install to only install a new program file, ... registry, which I hope isn't a problem in Vista). ...
    (comp.databases.ms-access)
  • Re: 5.1-5.3 upgrade
    ... you are doing a MIGRATION. ... overwrite will completely wipe out your install base and all ... You don't have to run any of the pre-migration scripts. ...
    (AIX-L)
  • Re: Access Runtime
    ... in separate database files? ... VERY VERY VERY VERY VERY good thing that you find it difficult to overwrite ... just accident running that install ... SEE THE DOCUMENTATION FOR DETAILS ON CREATING .ISS SCRIPT FILES! ...
    (microsoft.public.access.forms)