Access Runtime 2000

[vilmarie]

How I make and executable of access. I have a problem when I try to create a setup.exe. I don't understand what type of application is necessary to make this .exe(mdb., mde,)

 

[sfreeman]

uh, you don't.

Access does not run as an exe file. You may be thinking of VB.

As far as I know, the closest you can get is to create an mde file from your mdb file.



Sam_F
"90% of the problem is asking the right question.

 

[MoLaker]

MSAccess.exe is the executable. The databases it creates are not. If you need to distribute a database to users who do not have MS Access, you can create a run-time installation - if you have MS Access Professional. The run-time wizard creates a installation file set which installs a run-time version of MSAccess.exe along with the necessary support files.

 

[MoLaker]

Correction - you need the Developers version of Access.

 

[vilmarie]

Thanks.... I run the Access Developer 2000 with the .mde application. I have in the network folder: SMP.mdb, SMP_be.mdb, SMP.mdw adn SMP.mde. I divide the database in BE and FE. The problem is that the Developer is run in other machine that is standalone. I create the package with the SMP.mde. Then I copy the package to the machine that is conncet to the network. But when I run the setup.exe and make change in the application don't change the data in the SMP_BE.mdb(network). I think that the error is that I create the package in other machine. That is true or not?

 

[MoLaker]

That's what it sounds like. The development machine's front-end is not linked to the back-end that the distributed application is intented to use. You either need to attach the developer machine to the network and link to the back-end on the network before creating the installation setup OR develop a method of re-linking your front-end to the back-end. That way, regardless of where you developed, you could link to the correct back-end.

I recommend the latter for other reasons, too. Network gurus are always changing things - like building a new server or whatever. Including a means to re-link your database greatly improves the versatility of the application from the standpoint of back-end location and possible future modifications to the back-end.

There is one other way to salvage what you have done. On a machine that is connected to the network and has MS Access installed (Developer's Edition not necessary) - open a copy of your front-end MDB. Link it to the back-end on the network and then create a MDE. Copy this MDE to your setup file set. This way, the MDE in your setup will be pointed to the network back-end and not to the back-end currently included in your setup. This will only work if all users machines have the same network drive mappings or if you use UNC.