Runtime

Topic

New Reply

OK…since I cannot easily convert my Access db to VB for a stand alone program can I use this existing db and set it up for a runtime program? What do I need to do this if it can be done? I currently am using Access in the Office 2000 professional suite of programs.

Reply | Quote

Replies

You would use the MS Office Developers Edition Tools in ’97. Unsure in 2000.

Reply | Quote

You would need Microsoft Office 2000 Developer Edition. It comes with the Access 2000 Runtime. This edition also comes with the Packaging and Deployment wizard so you can easily distribute your app to users.

The thing you’ll have to be aware of is that when making a stand alone Access database there are a host of issues to consider. Most of the built-in features of Access are not available in the Runtime version – such as the toolbars for filtering and sorting. If you want your users to have this functionality you’ll have to build custom toolbars and sometimes write the code for these functions yourself.

Hope this helps

Reply | Quote

One other quick note on MS ODE 2000: with the introduction of data access pages in Access 2000, MS decided that all installs of an Access run-time application would need to have an IE 5.0 install. This greatly impacts the size of the install package – 150MB or so no matter how small your actual app is. MS has rethought that position (what with the general yuckiness of data access pages) and has a patch available so you can create a runtime install without including an IE install; you trim off about 75MB, but still have one whopper of a package you have to schlep about your network.

BTW, if anyone knows of a way to reduce the size of install packages, I’d love to know about it!!

Reply | Quote

Hi Shane,

This may or may not be the patch you’re talking about, but there is a much smaller Runtime option available from Microsoft. Here’s the link: http://msdn.microsoft.com/code/sample.asp?…ompositedoc.xml

Reply | Quote

Mark:

Yup, that is the one I was talking about. It’s nice that it drops the size by 50%, but it’s still a bit large, eh?! Seems unfortunate to have a 70+ MB install necessary for a 1 MB front-end. Thanks for the pointer, though!

Reply | Quote