How to distribute a database ?

[Alan Martin]

Apologies if this is in the wrong area.
I have written a few simple Access (2000) databases, which are kept on a central server which my colleagues use. Recently I have had issues where fields had been corrupted due to some one using a newer version of Access that the 'base was written on.
Firstly, is there anything I can do to stop this happening?
Secondly, If I wanted to send this database out as a stand alone unit which did not rely on a local copy of Access what software would I need?

Alan

 

[Argonak]

The acess 2002 Desktop developer's handbook suggests using Packaging Wizard which is included within Microsoft Office Developers. It creates a packaged product which would install both your database and a runtime only version of access for the user to use. You'd be wise to limit user acess to the dbs in its final version regardless though as the user would still be able to open the dbs in a normal version of access and have full access to all components and information.

 

[cheuschober]

Forgive me for sounding foolish (as I'm only beginning to understand the versioning working system) but I thought 97-up back-ends were basically compatible with any newer version front-end through linked tables?

Just curious,
~Chad

 

[Mile-O]

Yes, that's true. I have a few 97 backends with 2002 frontends.

 

[cheuschober]

That's what I thought! Otherwise I'd wonder how I was converting our '97 db to our 2000 model through an interim 2000 FE with both sets of tables linked without having '97 installed on my system.

It seems to me that in light of that fact so long as you ensure that your user is linking to your tables through their front end instead of opening the back-end that you could be relatively safe from corruption.

This doesn't replace the good office-mechanics of keeping everyone with the correct versions, of course.

Regards,
~Chad

 

[Alan Martin]

Thanks for the replies.

My problem is that I have no control over the software versions.

I need 2 things.

1 Some way of detecting the verion of Access the user has and stopping him/her if it is not suitable. Sounds ruthless but it protects the database.

2 Info on what to get to create a runtime version. How much does the developer version cost?