Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations wOOdy-Soft on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Distribution of database

Status
Not open for further replies.

jgoodman00

Programmer
Jan 23, 2001
1,510
How does everyone here distribute their database's once they are created. i.e do you create an installation program & if so what do you use to creat this program....I ask this, because I have never had to distribute one yet, but my current project will require this.....
 
I've only ever had to distribute to a small number of users in a single location, the one I'm working in. I name the front end with a version number and have the users copy it off the network to their workstations (and they have retail copies of Access installed there). I'm there to help them with problems, so a lot of the support issues of distribution don't apply to me. This saves a good bit of work, if your situation allows it. Rick Sprague
 
I think to distrubute to to access users they only need the database file itself, and any activeX controls you have used as they may not have them on their system. This can be done with a setup program (plenty out there).

To distribute to everyone, and this may include people who do not have your version of Access or do not have access at all, then you will the office developers kit which include a setup program, HTML help editor, answer wizard(office 2000) etc. This will create a runtime environment for users to access the database.

Hope that helps

Matt Regards

Matt

matt@begg-uk.co.uk
 
Distributing an Access application can be a painful experience. You need to prepare your app carefully:
-split in frontend and backend
-integrate bullet-proof error handling
-integrate security
-integrate refreshlink-code
-integrate backup-procedures
-integrate update-automatisms

If your app is does only rely on the standard libraries (no OCX or special procedures), if you do not use graphics and sound or multiple backends (training, sample...) and if your client has a full version of ACCESS, then you might install your app with a standard installer.
If your application exceeds this standard then you might easily get into trouble. The install wizard of the Runtime-version is horrible and full of bugs, you will need to replace him (either Sagekey( or MDT2000(
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top