[AccessD] Deployment

Thanks Jim.  I'll either try that or give it to my developer to implement.

Rocky

----- Original Message ----- 
From: "Jim Lawrence (AccessD)" <accessd at shaw.ca>
To: "Access Developers discussion and problem solving"
<accessd at databaseadvisors.com>
Sent: Thursday, March 04, 2004 6:08 PM
Subject: RE: [AccessD] Deployment


> Hi Rocky:
>
> IF you have a windows server handy for orchestrating the deployment you
> could try something as follows:
>
> 1. Create a sub-directory, off your ftproot directory, for each person or
> group of persons you wish to send the file to.
> 2. Create a user name and/or group for all who you wish to deliver the
> package to. Give appropriate access rights. (username/password)
> 3. In your IIS, create a virtual ftp account, using/pointing the name(s)
to
> the ftproot dir. Make sure the virtual ftp name is the same as the actual
> directory name. (If the physical directory is name .\MyProduct the virtual
> ftp directory should be named MyProduct). Attach the new account(s)
through
> the virtual ftp process as prompted. If you are only giving download
rights,
> set the virtual directory to Read-Only.
> 4. Send each group or single user(s), with your requesting email a line as
> follow:
>
ftp://MyFTPVirtualAccount:theTopSecretPassword@MySiteURLorAddress/MyProductF
> ileName.zip
>
> Pressing on the line above will automatically start a download process.
>
> HTH
> Jim
>
> -----Original Message-----
> From: accessd-bounces at databaseadvisors.com
> [mailto:accessd-bounces at databaseadvisors.com]On Behalf Of Rocky Smolin -
> Beach Access Software
> Sent: Wednesday, March 03, 2004 7:56 AM
> To: AccessD at databaseadvisors.com
> Subject: [AccessD] Deployment
>
>
> Dear List:
>
> I've got an app I'm developing for the consumer market and we're in beta
> testing now.  It's in A2K so all the betas have to have Access.
>
> Eventually it will have to be packaged as a run-time. But at that point it
> will be shrink-wrapped.
>
> In the short term we could expand our beta testing universe with a
run-time.
> So I'm trying to figure out the best way to do this.
>
> The problem AFAIK with the run-times is their size.  Right now we can
email
> the mde to a beta tester and it's about 3-4MB.  If I put up a run-time on
my
> web site, beta testers are not likely to know how to do an FTP program.
>
> I suppose I could make a password protected folder on my web site, and get
> my web site developer to make the run-time downloadable or installable
from
> the site.  I don't know how to do this.  Maybe she does.
>
> I've got A97 developer's edition, Wise Installer, and the Sagekey script
for
> A97.  But I don't think that the app can be converted back to A97.  In any
> event, the total A97/Wise/Sagekey package runs to about 70MB IIRC.
>
> I could buy A2002 or A2003 if they've got a better deployment capability
> than they've had in the past.
>
> What are your recommendations, suggestions, thoughts?
>
> Thanks in advance,
>
> Rocky Smolin
> Beach Access Software
> --
> _______________________________________________
> 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
>