[AccessD] Distribution - a bit OT

Arthur Fuller artful at rogers.com
Sat May 31 17:15:02 CDT 2003


I have only created two installations with the Developer stuff, and neither
needed any fancy DLL installs or anything outside Access, but the rest was
relatively simple, including installing MSDE and then restoring a database
to said installation. The code to restore the db took the longest time of
all the processes, but it ended up at about 50 lines of code.

Sage and Wise doubtless have their place, but if you're not calling DLLs
etc. I frankly don't see the need for them. The built-in stuff does
everything I needed: create a directory, copy everything required into it,
create a setup program that installs everything in the user-selected
directory, then run a program (in my case a batch file) to do everything
else that's necessary.

Arthur

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of John Colby
Sent: May 31, 2003 4:41 PM
To: accessd at databaseadvisors.com
Subject: RE: [AccessD] Distribution - a bit OT


Even a vb or C++ app has to store the data somewhere.  Is that going to be
an mdb?  If so Jet has to be installed.

As another lister said, a "slap a CD in and install" is possible, and it
will NOT interfere with any other versions, if you use the sagekey etc
stuff.

John W. Colby
www.colbyconsulting.com

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com]On Behalf Of Paul Black
Sent: Saturday, May 31, 2003 4:00 PM
To: accessd at databaseadvisors.com
Subject: [AccessD] Distribution - a bit OT


Hi

I submitted a proposal to a client this week for a custom application. Their
nose is a bit bent out of shape because they feel they should be able to
slap a CD in the drive click the install button and the app will install in
a nice self-contained thing-a-ma-bob (that is what they said).

Why do we have to have MS Access installed? You don't, I said, I can supply
a runtime version.

Why do we have to worry about what version of MS Access is installed
already? We did not ask for MS Access, we asked for a custom computer
application.

Why do we have to worry about installing a runtime version on a machine with
Access already on it and causing all kinds of problems (paraphrased)?

Plain and simple they want an app that is a DBS management system but they
want something that is completely autonomous. What do I do? What would you
do? I may have already lost this deal but need to prepare for the next time
this happens.

Do I offer a solution that is all VB or C++ or some such thing or am I
missing the boat here. Please help.


Thanks

PB

_________________________________________________________________
The new MSN 8: advanced junk mail protection and 2 months FREE*
http://join.msn.com/?page=features/junkmail

_______________________________________________
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com



_______________________________________________
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com



More information about the AccessD mailing list