Deploying an ADP

[JennyPeters]

I'm trying to deploy an Access ADP frontend to several users. Replication is not an option for ADPs, so what would be the best way to deploy frontend changes to all the existing frontends?

Thanks,

Jenny Peters

 

[scking]

Jenny,

You told us nothing about any options you may have for deployment using tools, how many customers you are deploying to, the size of the deployed .adp file, any LAN connections to the customers. These all impact the solution to your question.

My .adp application is quite large and I transfer it to a password controlled FTP site then send the link to allow them to download the application in an Email or Word file describing the installation procedures and any changes with the link. Remember, if you distribute an application with VBA references, then you need to consider the target population of computers in your solution and maybe create a Setup file with third party software which will install all the dependent .dll files.





---------------------
scking@arinc.com
---------------------

 

[JennyPeters]

Thanks Scking,

I'm in LAN environment inwhich I have to redistribute the same Access frontend to 15 people.

The file is only 6Mb, but still, it takes a good 2 hours to make sure everyone gets a copy etc. Especially when there are minor changes, this is quite cumbersome.

Replication would be a great solution, though not applicable to an .adp!

Does this help?

Thanks,

jenny

 

[scking]

If you are on a LAN environment you should be able to create a shared directory, place the file in it, and prompt the users to download/copy the file to their directories. Pulling rather than pushing the database. Have the users a little responsible for their system.

Place the file on an FTP server and email then a link. Clicking the link will let them decide to open or save.

ftp://ftp.arinc.com/AnyFilename





---------------------
scking@arinc.com
---------------------