DownloadStudio And visual Basic in Microsoft Office 2007

[vip_shadow]

I'm on a windows 7 32bit.
After latest changes in registry(your suggestion above) I'm still receiving the same "error in loading DLL" error.

for now, I used the system restore to be able using the database.
After restoring windows, Access is just fine.

[Peter]

We have fixed the problem in our installer, so DownloadStudio version 5.2 and later will not cause this problem.

[vip_shadow]

I'll be waiting for the new version.
Just a little about my latest experiments:

As I explained above, none of your registry keys worked for me.
After importing them I was receiving the same error messages about loading the dll file.

Referring to registry keys of a PC before installing DownloadStudio, I modified your registry keys as following, and tested on 6 PCs. It was a success.
All 6 PCs are running my databases without any error and DownloadStudio is sitting there downloading my staffs as it's expected to. Here's the reg keys I imported:

REGEDIT4

[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\TypeLib\{00025 E01-0000-0000-C000-000000000046}\5.0]


[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\TypeLib\{00025 E01-0000-0000-C000-000000000046}\5.0]
@="Microsoft DAO 3.6 Object Library"

[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\TypeLib\{00025 E01-0000-0000-C000-000000000046}\5.0]
"PrimaryInteropAssemblyName"="dao, Version=10.0.4504.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"

[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\TypeLib\{00025 E01-0000-0000-C000-000000000046}\5.0\0]


[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\TypeLib\{00025 E01-0000-0000-C000-000000000046}\5.0\0\win32]


[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\TypeLib\{00025 E01-0000-0000-C000-000000000046}\5.0\0\win32]
@=hex(2):25,43,6f,6d,6d,6f,6e,50,72,6f,67,72,61,6d ,46,69,6c,65,73,25,5c,4d,69,63,72,6f,73,6f,66,74,2 0,53,68,61,72,65,64,5c,44,41,4f,5c,64,61,6f,33,36, 30,2e,64,6c,6c,00,

[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\TypeLib\{00025 E01-0000-0000-C000-000000000046}\5.0\FLAGS]


[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\TypeLib\{00025 E01-0000-0000-C000-000000000046}\5.0\FLAGS]
@="0"

[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\TypeLib\{00025 E01-0000-0000-C000-000000000046}\5.0\HELPDIR]


[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\TypeLib\{00025 E01-0000-0000-C000-000000000046}\5.0\HELPDIR]
@=hex(2):25,43,6f,6d,6d,6f,6e,50,72,6f,67,72,61,6d ,46,69,6c,65,73,25,5c,4d,69,63,72,6f,73,6f,66,74,2 0,53,68,61,72,65,64,5c,44,41,4f,5c,64,61,6f,33,36, 30,2e,64,6c,6c,00,

Your key was written to import 00025 E01 while I tried 00025E01(without space). There are also several other little changes.

Hope it helps.

[vip_shadow]

It's very strange.
I've posted 00025E01-0000-0000-C000-000000000046
but it's shown as 00025 E01-0000-0000-C000-000000000046.(there's a space between 00025 and E01)

Maybe that was why your registry key added above didn't work for me.
I simply copied an pasted your keys.



Even if I click the Edit button to correct my post, there's no space between 00025 and E01.
But as soon as I post it, an space is added between 00025 and E01.

Now I've found a bug in vBulletin

[kathyw]

I had the same issue - where I was getting error message while trying to load dao360.dll. Once I unticked the Microsoft Office 12 reference for that database all worked well. I just had one user that was having issues - but as this database was all created using DAO rather than ADO changing references has allowed all to operate the database