Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion GroupsFormsForms ProgrammingQueriesModules / DAO / VBAReports / PrintingMacrosDatabase DesignSecurityConversionImporting / LinkingSQL Server / ADPMultiuser / NetworkingReplicationSetup / ConfigurationDeveloper ToolkitsActiveX ControlsNew UsersGeneral 1General 2
Access DirectoryToolsTutorialsUser Groups
Related Topics
SQL ServerOther DB ProductsMS OfficeMore Topics ...

MS Access Forum / Developer Toolkits / December 2005

Tip: Looking for answers? Try searching our database.

Distributing an application (ACCESS 2000)

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
L Mehl - 28 Nov 2005 02:05 GMT
Hello --

I will distribute my first application.

My understanding of what I need is:
- Split app into FE and BE
- Use http://www.mvps.org/access/tables/tbl0009.htm to re-link on each run
of app
- Create MDE
- Use Developer Edition to distribute Access Runtime files
- Use http://www.sagekey.com/  as install package to avoid conflict with
installed versions of Access

Are there other things to do?

Other questions:

Doug Steele said in response to questions posted by jptpjs on 10/3/05:
> MDE the FE for code security
"Usually a good idea"
what other options do I have to protect the intellectual property
represented by the code.

Can readers suggest how to install the BE database in a specific directory?
Is that handled by the Developer Edition tools or install package?

Can readers suggest the best source for a clear explanation of how to use
Developer Edition?

Since an exe is not created for this distribution package, I assume
InnoSetup can't be used.  Is this correct?

Thanks for any further help.

Larry Mehl
Alex Dybenko - 28 Nov 2005 09:27 GMT
Hi,
if you are planning to use Sagekey scripts - you can easy modify their
scripts to install BE into separate directory, but personally i do not
include BE into setup, but just ask some experinced user to copy it manually
once, just afraid that it could be overwrited. BTW - it is also good idea to
add some code to perform daily backups:
http://alexdyb.blogspot.com/2005/07/how-to-perform-daily-backups.html

InnoSetup you can also use, but perhaps you need to make your own script for
it:
http://alexdyb.blogspot.com/2005/04/free-script-to-build-access-runtime.html

Signature

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

> Hello --
>
[quoted text clipped - 32 lines]
>
> Larry Mehl
L Mehl - 28 Nov 2005 22:34 GMT
Alex --

Thank you for the suggestions.

Larry

> Hi,
> if you are planning to use Sagekey scripts - you can easy modify their
[quoted text clipped - 6 lines]
> InnoSetup you can also use, but perhaps you need to make your own script for
> it:

http://alexdyb.blogspot.com/2005/04/free-script-to-build-access-runtime.html

> --
> Alex Dybenko (MVP)
[quoted text clipped - 37 lines]
> >
> > Larry Mehl
davidp - 21 Dec 2005 16:21 GMT
Another thing that you may want to do is to disable the shift key.
This will prevent other user to get to the forms/reports etc.

You may also want to include hiden command that will allow you to enable the
shift key.  Incase you accidently lock yourself out.  
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.