[AccessD] Distribution - a bit OT

John Colby jcolby at colbyconsulting.com
Sat May 31 18:13:54 CDT 2003


But if you use the installers, the "different version" is only used by your
app, and isn't even visible to other apps.  It's just "files needed" for
your app.  No need for lawsuits.

John W. Colby
www.colbyconsulting.com

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com]On Behalf Of Drew Wutka
Sent: Saturday, May 31, 2003 6:58 PM
To: 'accessd at databaseadvisors.com '
Subject: RE: [AccessD] Distribution - a bit OT


It is NOT a Visual Basic Application though.  Installing a VB application
will not affect other installed software (unless you write you're own .dll's
that overwrite common .dll's.).

If I had a user install something that was documented as a 'Visual Basic
Application', but it went and installed a different version of Access, there
would be a lawsuit involved.

Drew

-----Original Message-----
From: John Bartow
To: accessd at databaseadvisors.com
Sent: 5/31/03 3:28 PM
Subject: RE: [AccessD] Distribution - a bit OT

You will run into this all the time with the know it all (arrogant) IT
types.

First off don't tell them its Access if they don't want to hear it. Its
a
"Visual Basic Application which uses a standard Microsoft data file for
storage. Give the app an icon using the tools | startup options menu
options
and hide everything else.

Secondly, everything they want as far as installation demands can be
done if
you use a Wise or Install shield installation with the help of Sage Key
scripts. This has been discussed a lot in the archives so I won't go
into
it.

If they make a point of that you are not to use Access for anything jack
the
price up about triple and do it in VB or 1000% and do it in C++

HTH
JB

> -----Original Message-----
> From: accessd-bounces at databaseadvisors.com
> [mailto:accessd-bounces at databaseadvisors.com]On Behalf Of Paul Black
> Sent: Saturday, May 31, 2003 3: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
_______________________________________________
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