NinaKim
asked on
Do you need MSRD2X35.DLL and MSREPL35.DLL?
I have a VB6 project that references DAO 3.51 to access a small Access 97 MDB. The project does neither access (import/export) other data formats nor uses database replaction. But the VB6 PWD would still include MSRD2X35.DLL and MSREPL35.DLL in the distribution package.
My question is:
Are these two files required to be included in the package?
My question is:
Are these two files required to be included in the package?
MDAC is a seperate concept from VB.. as such.. I would include the files to maintain MDAC integrity on the client machine.
Despite that, I ran a where used on the two aforementioned DLLs and pretty much they are standalones (not dependent files) used for Import/Export and Replication as the questioner suggests. Together they amass 700kb of code, so I can see the questioner's dilemna. In that regard, you may want to give it a try.
How is that for a wishy washy answer?.. LOL
Despite that, I ran a where used on the two aforementioned DLLs and pretty much they are standalones (not dependent files) used for Import/Export and Replication as the questioner suggests. Together they amass 700kb of code, so I can see the questioner's dilemna. In that regard, you may want to give it a try.
How is that for a wishy washy answer?.. LOL
ASKER
Thanks for the comments.
emoreau,
Yes, I made sure that no references were given to any related objects. Also, no components (for these) were added.
wsh2,
That's right. I even run the application on a clean m/c (without these two DLLs) without encountering any problems. But as you pinpointed, the size of those two files are fairly large that I don't really want to include in distribution whenever possible. And I wanted be 100% sure before I attempt to do that.
Are there any other comments out there?
emoreau,
Yes, I made sure that no references were given to any related objects. Also, no components (for these) were added.
wsh2,
That's right. I even run the application on a clean m/c (without these two DLLs) without encountering any problems. But as you pinpointed, the size of those two files are fairly large that I don't really want to include in distribution whenever possible. And I wanted be 100% sure before I attempt to do that.
Are there any other comments out there?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Just read emoreau's link.. Welp that kinda solves that.
Seems to me, it is best to include the files.. <groan>. NinaKim, I just hope you are NOT deploying by diskette.. LOL
Seems to me, it is best to include the files.. <groan>. NinaKim, I just hope you are NOT deploying by diskette.. LOL
ASKER
I had already reviewed the KB article and other relevant articles but couldn't find a clue to whether these two files MUST be included in a particular VB6 project. And as far as I know, other DAO/Jet files do not depend on these two files.
As the system registry goes, MSRD2X35.DLL (Registered) has only one entry in the section:
HKEY_LOCAL_MACHINE\SOFTWAR
MSREPL35.DLL (Not Registered) has none.
Anyway, thanks for the comments. I will award the points.
As the system registry goes, MSRD2X35.DLL (Registered) has only one entry in the section:
HKEY_LOCAL_MACHINE\SOFTWAR
MSREPL35.DLL (Not Registered) has none.
Anyway, thanks for the comments. I will award the points.
These 2 dll are included as soon as you use DAO 3.51 (as you do). I don't know if you can remove them but my tip is do not fool with it. It can cause problem later!