Package Deployment Problems

[Lieu]

Hello everyone, I am having troubles creating a functional package. It is very difficult to narrow down the problem as the errors are not happening consistantly. For example, the package works perfectly on the development PC, and sporadically on other machines. I will attempt an install on a fresh computer and the install will crash giving an error message that certain dll's are missing. I will fix this and I will get other error messages on certain computers. What is wierd though, is that on some computers it may crash the first time, but will install fine the second time. This would tell me that the second one works, but when I try to install the second on a fresh PC it will crash. I can get it working often, but it seems like I have to create a new package and install it a second time to get the first one to work. This is really mind-boggling. I know that this may be too general of symptoms, but perhaps someone has heard of anything like this before. Maybe someone could try and create a package on their computer? Thanks, and I appreciate any help or advise you can give.

Hai Lieu :-)

[Clunietp]

What files are you distributing? Just the regular VB runtimes or also database files like DAO or the MDAC?

[jottiwell]

Hello,

We've had lots of problems distributing Access 2000 packages. We found that the package can't get through the profiles on Win 95, therefore if you log in as ( for example ) administrator and install it, the thing will run fine, but only when you're in as administrator, else it'll hang at startup from a different person's login to the same machine. It'll either hang and say something like 'access must be installed to run' / 'a required dll is missing', or it'll just hang at the first form, or even more irritatingly, it'll let you use the firstform but then not save, or move or do anything else.

Before you install the package, remove the existing profiles, set the computer to log everyone on as the same, ( control panel > passwords > users ), reboot the thing, and then complete the install that way ( remember to reboot the machine when prompted and NOT alter any of the settings, go in again as the same person with the profiles still switched off, only then ( on the second reboot ) after access says it's completed turn the profiles back on.

Try this, it worked for us...

Hope it helps