Hey guys,

Question: I have been told that if I find the DAO350.dll in my applications I'm supposed to remove it, and make DAO350.msi a pre-requisite of the application.

I don't necessarily think this is a good idea, and my preferred strategy would be to remove the DLL and add the DAO350 merge module.

Just wondering what you think about this??
0 Comments   [ - ] Hide Comments


Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
Answer this question or Comment on this question for clarity


Adding the merge file would be the "standard" way of applying all the dependencies. I wonder if your companies DAO350.msi has the same file versions as the merge module you would add to your package.

I dont know if you would run into problems with your package (with DAO350 merge module) and the DAO350.msi self healing over the top of each other.

The safest bet might be just to use DAO350.msi and not the merge module.
Answered 10/11/2004 by: Garrett
Orange Belt

Please log in to comment
yeah, i'm still not sure. What if the DLL is isolated. Surely you wouldnt remove it then?
Answered 10/14/2004 by: dm1
Blue Belt

Please log in to comment
well dm1 .i would put in the merge module no question about it.FACT
Answered 10/15/2004 by: Fordy
Senior Yellow Belt

Please log in to comment
If you think scalability then remove it and manage it as a seperate entity.

If you have 10 packages with the DAO merge module in them and decide to upgrade DAO for 1 app, then you have to change the other 10.

If you remove it and make it install it seperately, then to upgrade it for all apps means uninstalling it and reinstalling the upgrade to affect all the apps.

This is far more scalable and manageable.
Answered 10/15/2004 by: MSIMaker
Second Degree Black Belt

Please log in to comment