Access 2000 Runtime Problem

[stressball]

Hi,
I need to know more about creating an Access 2000 Runtime.

I have to convert an Access 97 database to Access 2000, fix the problems it has and then package and deploy it as an Access 2000 runtime version as the clients do not own Access 2000, only 97.

I have Access 2000 which I have converted it into, and I also have Office 2000 Developer with Access 2000 runtime. My problem being what do I do? There does not seem to be any documentation on the disk or in the book, or on the net (I have looked on technet) as to how I take my Access 2000 database and use Office 2000 developer to deploy it royalty free.

If someone could help me out with this or point me to the appropriate website I would be most grateful.

Thanks

 

[fpdkris]

I hope this helps.

On the Access Dev CD there is a runtime directory. (Although not a packaged solution) I copy that dir to the user's pc and run the set-up from that dir. It creates a new dir with all required Runtime executables, registers itself to Windows. I then simply install or point to my application and the runtime executes properly. There is also a helpful readme on the CD which pretty much covers the above.

 

[TheInsider]

Hi,
Here are the intial steps involved:

1) Install the Package and Deployment Wizard, if it is not already installed. Basically, run the install on Developer Tools CD #2 choose "Install Microsoft Office 2000 VBA Tools".
2) On the Developer Tools CD #2 there should be an "accessrt" directory. Under this directory are two folders; "full" and "min". "full" contains the files for a full/large runtime version, while "min" contains a compact runtime version. Personally, I use full. Go to (double-click) the folder that contains the version that you want to include with your installation. Either one will work.
4) Select the entire contents within this folder and copy it to "C:\Program Files\Microsoft Office\ODETools\V9\Runtime". If the "Runtime" folder doesn't exist, then create it first.
5) Open the database that you wish to create a setup package with.
6) Go to the code window of any module and go to the menu bar at the top. Choose "Add-Ins" and then "Add-In Manager".
7) Double click the "VBA Package and Deployment Wizard" so that the "Load Behavior" says "Loaded", then click "OK".
8) From the "Add-Ins" menu choose "Package and Deployment Wizard...".
9) Choose "Package".
10) Choose "Standard Setup Package", click "Next".
11) Choose your assembly directory then choose "Next".
12) Check the checkbox that says "Include Access Runtime".
13) Finish going through the steps of the packaging wizard.

That's it. When the user attempts to install the setup package, it will detect that they need Access 2000 and will install the runtime if needed.
Rob Rob Marriott
rob@career-connections.net

 

[stressball]

CCTC1
Thank you for your reply, could you please let me know if this is possible:

The database is split, there is a backend which resides on the c:\ drive of the server, and there are 2 front ends, 1 front end has some linked tables and some tables of its own.
Access 2000 will be installed on the server, is it possible for the backend to be a full version and the front ends to be Access 2000 runtimes (Created with Office Developer) interacting with the backend?
(Currently the database is all Access 97, but they need to add more PCs and they want to upgrade to Access 2000 without purchasing more office packs than they need to)

Thanks.

 

[TheInsider]

Yes, you can use the 2000 runtime for the front ends, however, you won't be able to access/edit/create any tables, queries, etc. in the front end with a runtime version. i.e. You mentioned that the front end has some tables and queries of its own -- you won't have access to these. Rob Marriott
rob@career-connections.net

 

[stressball]

Thanks, to clarify, are you saying that I will not have access to modify the front end tables and queries?
I assume that is what you mean, as the forms the user inputs data into and the reports they can view data in are based on both the linked tables and the front-end tables they will still be able to input and view data through the forms and reports regardless of whether the tables and queries are linked or not.
Is my thinking correct?

 

[TheInsider]

Yes, that is correct. They will have normal interaction through the forms. Rob Marriott
rob@career-connections.net