Running Database Without Access

[hootie318]

I thought I read on this board about setting up a database so that it runs even if access is not on the computer. Can this happen. I run a program on one of my computers at work that uses access, but doeas not require access to be installed.

 

[wizcow]

Hootie

You need the "Developer" edition (I think its called) of access to produce stand-alone programs. And its pretty expensive.
But... it can be done.

Tom

 

[Pat Hartman]

wizcow, there is no such thing as a stand-alone Access application. In order to run an Access app, you need some version of Access installed!!!!!! Either retail or runtime. There are dozens of posts here telling you that the developer's edition does not in any way shape or form modify your access database. All it does is provide a license for you to distribute the runtime version of MSAccess.

 

[WindSailor]

Deploying Microsoft Access Applications using the Access Runtime:

http://msdn.microsoft.com/library/d.../detskdevelopingaccessruntimeapplications.asp

Deploying Complex Microsoft Office Access Runtime-Based Solutions - Access 2003:

http://msdn.microsoft.com/library/d.../en-us/odc_ac2003_ta/html/odc_acdeployade.asp

In this section, you'll find links to technical articles, developer documentation, resource kits, book excerpts, support centers, and more for the previous two versions of Microsoft Access.

http://msdn.microsoft.com/office/previous/access/default.aspx

As a new developer in Access I am continually learning... I haven't personally distributed a runtime environment yet (basically being lazy), but I have distributed mdb and mde files... all of which react differently on different computers even though they have identical software on them. That's where the fun is... making sure your app will react the same on as many computers as possible, especially when you start to code on particular environments.
Use the latest and best version that you can afford.
In Office 2003, Microsoft no longer has a developer version of MS Office, but they have Developer Tools in which you can purchase seperately.
According to other various resources, this should be the last version of Access (2003) that supports the jet database and that the .Net environment will be incorperated in the future versions of MS Office.

 

[spacepro]

For your Information.

When I distribute Access Database as an EXE , I create the application in VB using the Access in 7.0 format at the backend, this is done by using the visual data manager in Visual Basic 6.0.

So all user orientated objects are displayed in the EXE but use the data in a access 7.0 database, which when packaged includes all files to operate the EXE, saying that I have never installed a compiled EXE on a PC where Access is not installed.

Personally I use Visual Basic if I need it to be an EXE.

Andy

 

[wizcow]

Pat

Right you are. I was confused as to how the 'Packager' worked, or even what it was called. After reading the articles that WindSailer has posted, I see that the packager just installs Access with your application.

spacepro

I am trying to use VB6 as a front end on a project right now, but I am not sure how to tie it to the access back end. Is this an easy thing to do?

Tom

 

[spacepro]

Tom,

If you select the following from VB

AddIns > Visual Data Manager

Using the visual data manager you can tie the database to the frontend, just set your datasources to the database on your form properties.

The db needs to be in 97 format to work.

Normally I will create all of the tables and queries in access (better userface). Then start designing my EXE in VB then tie the data to the db.

Hope this helps

Any problems give me a shout

Andy

 

[pat_nospam]

Without VB, i.e. if you used the Developer solution just for the Access FrontEnd MDE file, would it remain tied to the backend MDB file on the network? Can you use Access runtime to distribute the front end if it is dependent on the network shared backend?

TIA - Pat

 

[boblarson]

In response to Spacepro's comment:

The db needs to be in 97 format to work.

The answer is - No, you can use A2K format also. You just need to have updated to Jet 4.0 to use it in VB6.

See this link:
Upgrading to Jet 4.0

 

[spacepro]

Thanks Boblarson,

You learn something new everyday.

I was unaware of this , so thank you for correcting me.

Thanks

Andy

 

[Pat Hartman]

pat,
Normally the package and deployment wizard would be used to distribute the entire application, fe and be. But, since this is an internal distribution, you shold be able to package just the fe. As long as the path to the network be is the same for all users, then you won't have any problems, the links will remain intact. Make sure that you are using UNC naming conventions when linking the tables rather than a hard-coded drive.

 

[pat_nospam]

Make sure that you are using UNC naming conventions when linking the tables rather than a hard-coded drive.

Pat - Just curious what these naming conventions are that will restore linked tables if they are moved?

I'd like to employ this method before I deploy the database.

TIA

Pat

 

[ghudson]

UNC [Universal Naming Convention]...

\\Server\Partition\Directory\File.mdb

Instead of...
X:\Directory\File.mdb

UNC advantage is that not everybody uses the same drive letter when mapping to a server.