Installing my app

[asawyer]

If I don't have or don't want to use the Access 2003 Extensions to create a
package to install my .mde, is there a simple way to do it?
I don't use any 3rd party tools, so it's only the .mde file.


I would want to install access 2003 rt if needed and maybe a shortcut.

Could I just install the rt and then create a shortcut to my mde without
even using an installer??
or is there a fairly simple installed I could use?

Thanks,
Alan Sawyer

 

[Albert D.Kallal]

I would want to install access 2003 rt if needed and maybe a shortcut.

I as a general rule use the package wizard to build the runtime install.

Could I just install the rt and then create a shortcut to my mde without
even using an installer??

Yes, you can. And, in fact, I find this approach is PREFERRED. Once your
client has the runtime installed, then any new updates etc. that you deploy
do not need the installer. (besides, using that installer to JUST deploy a
mde without the runtime don't make sense anyway).

There are a few solutions.

** package ONLY the mde with the ms-access install tools. This is a really
good approach, as then the users do NOT need to put in the original cd of
yours to un-install. This does assume that you packaged the runtime as
another separate installs. The only problem with this approach is that I
find upgrades is a pain in the neck, as the install OFTEN states that you
already installed the application. You can manually force the installer to
re-generated the version by erasing the "product" code that is generated
(step 5 of 7 in the wizard). However, I find this a pain to have to re-gen
the product number for JUST a upgrade. There is a way to get the product
version set (step 6 of 7 in the wizard), but I have poor luck, so, I don't
use the ms-access wizard to package my mde's anymore..(I use something
else).

*** Use a ziip utility like winzip (you can find it at www.winzip.com). I
had a registered version for years, and it allows you to create a .exe file
that when clicked on will un-zip the file (a mde in this case) to your
directory of choice. This is really the most simply approach, and I used
this for many years. However, the problem is that you can't do things like
"check" for a version of ms-access, or place a shortcut on your desktop.
But, for simple, you can't beat it.

*** Use Inno installer. This is without question your best choice here. In
fact, I use Inno to both install the runtime AND install the mde. (I use
Inno for both). Inno can also build your desktop shortcuts, check for a
existing version of ms-access. You can also do registry settings (you need
to do a few of those to get rid of the security prompts). I can't think of
a better, simpler, or more useful installer. And, it is free. You can get it
here:

http://www.jrsoftware.org/isinfo.php

I simply can't tell you how great this tool is. So, even for just sending a
client a mde file, I wrap it into a inno .exe file for them to click on. I
don't have to tell there were to copy, or un-zipper or anything. Just simply
run the file...and they are upgraded.

 

[asawyer]

Thanks,
I looked at Inno but got confused in that I couldn't find any examples of MS
Access setups.
Is the script*?) something that you can share or point me to so I can give
it a try?
Alan

 

[Albert D.Kallal]

Thanks,
I looked at Inno but got confused in that I couldn't find any examples of
MS
Access setups.
Is the script*?) something that you can share or point me to so I can give
it a try?
Alan

Yes, you have to write your own scripts. However, they are very easy. I had
mine up an running in about 1 hour.

For example, to install the ms-access runtime, you FIRST make a runtime
install with the ms-access package wizard. This will produce your runtime
install. (as mentioned, it is up to you if you include the mde, but I make
the mde a separate install with inno, and NOT ms-access wizard installer).

Remember, since we are only coping files here, then the scripts are very
simple in nature. So, to install the ms-access runtime, I am STILL actually
using the ms-access install wizard, but I do a "quiet" install. This way, I
use the Inno installer on "top". This also eliminates SEVERAL prompts from
the ms-access install (such as "custom" options that NO ONE EVER uses!). So,
I do this, since I don't want my clients to have a whole bunch of
"different" looking screens to install my software - I want the SAME look
and feel for both the runtime system, and my mde's that I deploy. In the
following example, I obviously created the runtime install with the wizard
to a directory called c:\ridesruntime

After the above ms-access wizard creates the runtime, I now package it using
inno with:

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

[Setup]
SourceDir=c:\RidesRunTime
AppName=Rides Runtime System
AppVerName= Rides 1.5
DefaultDirName=c:\RidesRunTime
Compression=lzma
SolidCompression=yes

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


[Files]
Source: "*"; DestDir: "{app}"
Source: "files\*"; DestDir: "{app}\files"
Source: "files\setup\*"; DestDir: "{app}\files\setup"
[Run]
FileName: {app}\setup.exe; Parameters: "/qb"

So, the above packages the ms-access runtime install I made with the wizard.
Adding the "/qb" to the standard Microsoft installer does a quiet install,
but DOES show the progress of the install. I am sure if you played with the
ms-access wizards, you will recognize the above directories that it creates.

After the above is installed on a pc, then simply copying the mde file to
the target pc is all you need. However, you can also use inno. (take a look
at the sample scripts).

Here is sample one I use to install the mde part, and note how it checks if
ms-access is installed
(by the way, the access 2003 wizard WILL create desktop shortcuts for
you..but if the location of office is changed, then the access wizard
produces the WRONG shortcut cut. In fact, for this problem/bug is why I now
use Inno. So, note well that the ms-access wizard will create desktop
shortcuts, but not for non-standard locations of office. The other problem
was that the access wizard does NOT allow you to specify a shortcut to the
workgroup file if the path name does NOT exist on your computer (which is
going to be MOST of the time if you split your application). By the way, if
you don't have a split application, then none of my advice is of any use to
you!! (but, you can't possibly be deploying applications, and not have a
split applications - just in case this is a possibility for you, then read
the following of mine on why you split here:

http://www.members.shaw.ca/AlbertKallal/Articles/split/index.htm


Anyway, the following assumes a split database, and thus I am ONLY copying
the mde (application part) to the users target pc.


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

[Setup]
SourceDir=C:\Documents and Settings\All Users\Application Data\winq
AppName=Windship Quotation System
AppVerName= Quotes XP 2.0
DefaultDirName={commonappdata}\winq
DefaultGroupName=Windship Quotes
Compression=lzma
SolidCompression=yes

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


[Files]
Source: "WinqXP.mde"; DestDir: "{app}"
Source: "windi.ico" ; DestDir: "{app}"
Source: "WinqXP.bmp" ; DestDir: "{app}"


[Icons]
Name: "{commondesktop}\Windship Quotes"; FileName:
"{reg:HKLM\SOFTWARE\Microsoft\Office\11.0\Access\InstallRoot\,Path}MSACCESS.EXE";
Parameters: """{app}\winqXP.mde"" /runtime"; IconFilename:
"{app}\windi.ico"; comment: "Starts Windship Quotes System"

function InitializeSetup(): Boolean;


var
strRes: string;
begin

result := False
if RegQueryStringValue(HKEY_LOCAL_MACHINE,
'SOFTWARE\Microsoft\Office\11.0\Access\InstallRoot\', 'path', strRes) then

result := True;

if Result = False then
MsgBox('The Runtime Files MUST be installed BEFORE' #13#13 'Installing
this Program. - setup will stop', mbInformation, MB_OK);

end;

You of course can also add registry settings etc. as  you need...and take a
look at the many examples included with inno.

I not going to purport any great knowledge of Inno here. We are talking
about DEAD simple scripts, and the above were simply samples from Inno that
I modifed........but a few simple scripts got me well on my way, and I could
not be more happy...

 

[asawyer]

Thanks, that helps a lot.
Alan

 

[asawyer]

So you're using the normal Access Extensions Packager to create the run time
install?
I'm having issues in getting the Packager to work, and that's why I was
trying to find something else.
MS does have the runtime in a package already?? Could I use that, or do you
think I should try to figure out what the problem is with the packager and
try to go that way first.
Alan

 

[asawyer]

I think I got a good Access 2003 RT Package created, so I'm going to play
with INNO now.
Thanks for your help.
Alan Sawyer

 

[asawyer]

Albert,
How do you install updates to your software?
Do you use Auto Updater, or something like that?
Alan

 

[Albert D.Kallal]

Albert,
How do you install updates to your software?
Do you use Auto Updater, or something like that?
Alan

I just create a new mde, and wrap it in a inno install, and then send that
to the client. It really depends on how the client is setup in the first
place.

For many of my customers, they are running single user (still split of
course). So, to update the software, you just need to copy a new mde to the
pc.

For remote clients, and ones where I don't want to email them a update, I
just have them go

help->about rides

(gee, if you are going to use the runtime, then I sure a long long time ago
you started using custom menus...right?).

You get the following screen shot:

http://www.members.shaw.ca/AlbertKallal/rides2/index.htm

(Like all other software on my pc, they all have a about box....so should
you!!).

If the user clicks on the download/update rides butting, I simply use a
hyperlink to my web site, and they get a new version. The code behind the
download/update rides button is:


Dim strExe As String


If MsgBox("This will download the lastest version of Rides" & vbCrLf & _
"Do you want to update Rides?", vbQuestion + vbYesNoCancel,
AppName) <> vbYes Then
Exit Sub
End If

' ok...start the update....

strExe = Left(strWebSupport, InStrRev(strWebSupport, "/")) &
"ridesxp.exe"

Application.FollowHyperlink strExe

Application.Quit

Note that strWebSupport is simply a variable with a path name to the support
web site.

The above code will produce

http://www.kallal.ca/SomeDirecotryYouUse/ridexxp.exe"

So, if you place a simple inno install file on your web site that matches
the above url address. Now, if user clicks on this button, the install will
start.

So, you simply hyperlink to a .exe file. You can even hyperlink to a file on
a your hard disk, or to a web site. Note how the code's next line is to QUIT
the current application. (so, the inno install will simply overwrite the mde
file).

The above is a "nice" way, and really very easy. (gee, I think I count about
4 lines of code to update them from a web site?? In fact, that is LESS
writing and less work then me writing this email post!!l!!!) Really, what
could be easer in terms of work, and even in terms of code that you have to
write?

You can also email a client the inno instill. However, I find to day that a
LOT (most) companies now filter out any attachment that has a .exe extension
(and, I don't blame them). So, I now use a web site to update them. Just
throw the inno .exe install on your web space, and have the client go get it
there (virtually all internet providers supply some free web space...just
use that!!).