problem with access deployment in using runtime app

[cluce]

I am trying to deploy a small access project that connects to sql but when I run the program using the runtime client I get nothing, no forms or anything? But when I run it using the full version it works.

I downloaded a sample database from MS and connected that to SQL to retrieve the data. When I use runtime client for this program it works.

Does anybody have any ideas why my programs are not coming up?
This is having me pull all of my hair.

[nico5038]

When the runtime version is executed on a different machine, your references could be "MISSING".
Did you try to check the references on the "runtime machine" e.g. by installing full Access temporarely ?

Nic;o)

[cluce]

When the runtime version is executed on a different machine, your references could be "MISSING".
Did you try to check the references on the "runtime machine" e.g. by installing full Access temporarely?

Nic;o)

thanks for the reply.
Well after I tried it on a machine without the full access I installed the runtime on my machine that also has the full version installed on it. The program only works with the full version not the runtime. Maybe its not packaging the program correctly or maybe it doesnt have all the files intsalled to run???? I do know its not putting a shortcut on my desktop during install like it should.
I am not sure what to do. How can I check my references?

[nico5038]

Hmm, in the runtime environment checking the references isn't possible by using the Tools/References the full version will offer.
Thus my proposal to install Access fully to check.
When you can't install Access, you could do several things:
1) Create a package and include all .dll's (libraries) needed.
For this you need the Access Professional edition (till version 2000, higher versions require the packager of VB)
I also once used a freeware packager to create such a package and make a selfinstalling application.
2) Check the libraries (.ocx, .dll, etc.) that are used for the used references (Tools/Reference under VBA) and make sure a copy of these is installed (or added) to the other machine.
3) Add some code to the .mdb to check for missing references and report those so the needed ones can be installed or you could try to link an older/nerwer version from code.

Nic;o)

[cluce]

[QUOTE=nico5038]Hmm, in the runtime environment checking the references isn't possible by using the Tools/References the full version will offer.
Thus my proposal to install Access fully to check.
When you can't install Access, you could do several things:
1) Create a package and include all .dll's (libraries) needed.
For this you need the Access Professional edition (till version 2000, higher versions require the packager of VB)
I also once used a freeware packager to create such a package and make a selfinstalling application.
2) Check the libraries (.ocx, .dll, etc.) that are used for the used references (Tools/Reference under VBA) and make sure a copy of these is installed (or added) to the other machine.
3) Add some code to the .mdb to check for missing references and report those so the needed ones can be installed or you could try to link an older/nerwer version from code.

I have access 2007 and it packages the whole program for me. So I really dont know how to tell what it is packaging. I did look under program files and see what was installed. There was only one file in the program folder--- .accdr
maybe I need to change the file type before I save it. Of course, I need to figure out how to do it.

A couple programs I developed worked in runtime but most of them dont. I even tried to download a sample databse from MS and use sql as the backend and that comes up blank.

[nico5038]

Hmm, Access2007 that's a different kind of ballgame.
I would make sure that the .accdr is placed in a thrusted folder, else the code won't execute...

Nic;o)

[cluce]

Hmm, Access2007 that's a different kind of ballgame.
I would make sure that the .accdr is placed in a thrusted folder, else the code won't execute...

Nic;o)

whats a thrusted folder?

[nico5038]

When pressing the OfficeButton you'll find a security section. Select that and you'll be able to set the location where Access will "Thrust" the database and will enable the code excution.

Nic;o)