Installing and Using the Access Runtime

JHMarshIII

Registered User.
Local time
Today, 16:10
Joined
Feb 8, 2002
Messages
19
How do I install the runtime?

I own a copy of O2K Pro and recently bought the Developer disks at a steep discount. This was the equivalent of buying O2K Developer. I want to distribute my DBs in exe format.

When Auto-running the CD it puts the whole MSDN library and other stuff on my machine. But all I want to know is how to install and use the Runtime module on mine and other machines. I'm not ready for VB just yet.

Is the Runtime just a file that need be present on the end-user's machine? How does the Runtime get called/invoked? How would I pull the data out of the exe file/db or export the data that is captured?

Thanks, John ..
 
If you want to just view your databases on a machine without Access installed.
Browse the developer CD.
ODETools\V9\AccessRT
Double click on the setup exe.
This will install the runtime files.
You need to then make sure the shortcut to your database points to the runtime files to run.
i.e.
C:\Program Files\MSOffice\Art\MSOffice\MSAccess.exe
 
If you want to just view your databases on a machine without Access installed.
Browse the developer CD....

Just view? Won't the access runtime permit the end-user to update tables, queries, DB application permitting?
 
If you are trying to install an Access 2000 database on to a machine that doesn't have Access or an earlier version of Access it needs the run-time files so the end user can open the database. When you use the Package and Deployment wizard you get the option to include the run-time files. If you include them and save the deployment package to a cd which you then give to someone else, when the cd deploys the database it determines whether the end user has Access 2000 on the PC, if it does it just installs the database, if it doesn't it installs the database and the run-time files to enable that user to open the database.
 
"I'm not ready for VB just yet." Did you use Macros? If so you really need to convert them to VBA and add error handling ( the developer tool kit does add error handling if you use the error handling add in). If your Error handling isn't nearly bulletproof your app will rather nastily dump you when an error occurs.
 
Runtime will let the user add records run queries etc(depending on the permissions that you set)but it won't let you make design changes ( I think!!)
What I meant by just viewing is that the way I explained above lets you use your database but you would have to set everything up manually.
If you use package and deploy it it is all done for you.
The down side to P&D is that your overall program will become large due to the cabinet files etc.
My method will bypass that but means you would need to do the initial setup.


[This message has been edited by Nero (edited 04-15-2002).]
 

Users who are viewing this thread

Back
Top Bottom