Marketing Application - Tools Needed?

[Malcolm P]

I need direction re. distribution of an application and updating of a
distributed application.

I've been told by one source that I would have to use "MDAC" and "installer
script" and by another source that they used "Setup Factory... spent quite a
few weeks learning how to program that product ... then wrote about 500
lines of code (in that product) to control the installation process."

My question:
What programing language must I learn to handle this process?
Visual Basic.......... Visual Basic for Applications....... Visual
Basic.Net...............
One of the above? All of the above? None of the above but something else?

 

[Alex Dybenko]

if your application was built in Access - then you can use either setup
wizard of appropriate office developer edition version, or
installshiled/wise together with www.sagekeys.com scripts.

 

[TC]

Your first decision is whether you want to use the runtime version of
Access, or not.

If you /do/, you'll need to buy some extra software from people like
SageKey, to make it work well.

If you /don't/, you'll need to buy some other installation product,
such as Wise, InnoSetup, Setup Factory, or whatever, so you can create
a professional installation program.

I said this & more to you before, no? (since those are my words that
you've quoted). So, have you researched what I suggested before? For
example, have you looked into the "front end/back end" database
structure & why you will need that?

HTH,
TC

 

[Malcolm P]

TC
The reason I posted this question is because I was waiting for one last
reply from you to a final question, which follows:
What programing language are you talking about (re. your 500 lines of code)?
Is it VBA, Visual Basic for Applcations?
________________________________________________________________

Also:
1> I do know about front and back end division of the data base.
2> I invested in the software to do runtime and found runtime inadequate.
I invested in Access 2003 and Visual Studio Tools for Office 2003 (which
includes the Access 2003 Developer Extensions) . Consequently, I have to
distribute the program only to those with Access.

 

[Malcolm P]

My question:
What programing language must I learn to handle this process?
Visual Basic.......... Visual Basic for Applications....... Visual
Basic.Net...............
One of the above? All of the above? None of the above but something else?

Or.......................
Do the items you suggest not require code to be written?

 

[Alex Dybenko]

Hi Malcolm,
to build access application - you need to learn Visual Basic for
Applications
to create setup - you don't need to learn any of mentioned language

 

[TC]

Sorry Malcolm, I missed your reply in the other thread. I use google
groups to keep track of what I have posted. Sometimes it doesn't tell
me that someone has replied to one of my poists, & so I lose track of
that.

Answers below.

TC
The reason I posted this question is because I was waiting for one last
reply from you to a final question, which follows:
What programing language are you talking about (re. your 500 lines of code)?
Is it VBA, Visual Basic for Applcations?

No. In my case it was the programming language for a product called
Setup Factory.

Basically, Setup Factory lets you choose the files that you wan to
install, and the folders were you want to install them. Then it zips-up
all those files into an installation program with professional-looking
screens & so on. Your users run that installation program (not Setip
Facotry) to install your software on their PC. Setup Factory creates
the installation program that your users will then run.

Setup Factory (and similar programs) usually do other things, such as,
optionally requiring the user to enter a valid serial number before he
can install the product. Or requiring the user to read & agree to some
terms & conditions before he can instll it, & so on.

Setup Factory & similar products can often be programmed, using their
own programming language, so your installation program /run code/ when
the user tries to install your software. This lets your installation
program be far more capable than just a big zip file.

In my case, I have programmed Setup Factory to check that the user's PC
has a suitable version of Access, and check that my product is not
already installed. (Otherwise, instaling it again might overwrite their
data file.) It also does several other things that I can not remember
right now!

I'm not sure that I would recommend Setup Factory any more, for various
reasons. But ther are many other similar producs; for example, Wise
Installer, Inno Setup, Microsoft Installer, and so on. If you are /not/
going to use the Access runtime version, you need to evaluate these
other products & see which one would meet your needs.

1> I do know about front and back end division of the data base.

Then you need to research those terms, as I have (ahem) already said!
If you want to be able to distribute updates for your database, you
absolutely definitely positively must split it into a "front end/back
end" structure. Go to groups.google.com, and type the following into
the box; this should get you started: FE BE group:*access*

2> I invested in the software to do runtime and found runtime inadequate.

I made the deciion years ago, never to use the Accvess runtime. I've
never regeretted that decision

I invested in Access 2003 and Visual Studio Tools for Office 2003 (which
includes the Access 2003 Developer Extensions) . Consequently, I have to
distribute the program only to those with Access.

I decided to take that risk for my products. To this point, it has
(surprisingly) never been a problem! My products clearl;y state on
their cd, cd cover, user manual, & so on: "This product requires a
working, retail copy of Microsoft Access version 97, 2000, 2002, or
2003, on the PC". My installation program checks for that, and repeats
that message (at runtime) of the user tries to install the product on a
PC that does /not/ have Access, or does not have a suitable verion.

Cheers,
TC

 

[Alex]

Hi hope it's ok to just tag my question here since it's exactly what I was
looking for. I need to do the same thing where I need to deploy an
application for a client who will be selling to the general public. I just
talked to someone at SageKey and at Wise. It looks like one could just buy
the MSI installer through sage key instead of buying the wise installer and
then having to buy the scripts from sagekey. My question, how is this
product different from the package wizard that comes in the developer tools?

Thanks a bunch

 

[Alex Dybenko]

Hi,
I am using SageKey scripts with Wise installation for several years, must
admit that this solution is much better then developer tools PDW. Scripts
are completely customizable, so you can do almost everything. Certainly a
good investment for developer

 

[Alex]

Thanks Alex - why does one need Wise installer as well as the scripts? From
what I understand, one has to create the runtime using the package wizard,
then use the wise installer and the scripts to customize it?? (THis is from
the guy at Sage). I didn't quite follow the logic and purpose of each of the
tools.

Thanks

 

[Alex Dybenko]

Hi,
Personally - I use Wise scripts, so I need Wise installer to compile scripts
now I see they offer scripts for MSI - in this case you certainly don't need
Wise or Installshield

--
Alex Dybenko (MVP)
http://alexdyb.blogspot.com
http://www.PointLtd.com