Re: dhSqlLite.dll question

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance


"MP" <NoSpam@xxxxxxxxxx> schrieb im Newsbeitrag
news:eMXd760kHHA.4112@xxxxxxxxxxxxxxxxxxxxxxx

I'm wondering where I should be storing dhsqllite.dll,
sqlite3_engine.dll, and dhSortedDictionary.dll for best results
(guess question applies to any dlls that need registered in
general but these are the ones i'm trying to use now)
Normally on your development-machines you should place
the Dlls inside \system32 and register the ActiveX-ones there.
For your deployed solutions I'd recommend, to place the
Dlls beside your Exe.

...
but the paths vary on machines so I'm thinking I should just put a dll
folder on my portable hd which is where I'm doing my work anyway

I assume if i register them on both machines and both point to the usb
drive, that it would all work?
If you work inside the VB-IDE, then you could get problems with
the Non-ActiveX-Dlls (e.g. DirectCom.dll or SQLite3_engine.dll)
regarding "Dll not found" errors, if these Standard-Dlls are not in the
VB6.exe-Path or in your Win- or WinSys-Folders.
You'd have to include the Dll-Path of your USB-Device into
your Systems Path-Variable, to avoid potential problems, working
from inside the VB-IDE.
As said, running compiled Versions of your final solution don't
need this additional efforts, if you deploy the Dll-dependencies
into the appropriate "App.Path" (and let the Setup register the
ActiveX-ones there).

would a single coder (not on a team) typically put all dlls in one
central location?
That depends, if some Dlls have to interact with each other (as
e.g. dhSQLite.dll and SQLite3_engine.dll do), then you should
keep them together in any Path you choose (of course under respect
of what I've written above regarding the VB6-IDE, being the
Host of your VB-Code-Debug-Runs.
Components of other vendors could be placed together in other
(Sub-)Paths - no need to put all 3rd-party binaries into one folder.
If you want to have all "development-binaries" in one place, I'd
recommend \Sytem32. Then you always know, where you have
to look if something behaves weird (and ... a local Harddisk is
a local Harddisk - a Network-Share in your LAN is also not
bad nowadays, but with an USB-Disk there's always a somewhat
higher risk, regarding acceleration of gravity ;-).

Think, there's no general recommendation regarding this topic.
You'll have to find a way that best suits your purposes (same
thing as with backup-strategies).

Olaf


.

Relevant Pages

  • Re: problem porting vb dev apps to new computer
    ... > created by the "C' project, then do the same for all the ocx from the ... you can select any number of dlls or ocxs in windows ... Register and unregister components with context menus ... > a totally clean system with VS6 that the ocx get built before the parts ...
    (microsoft.public.vb.general.discussion)
  • Re: Restore of SBS System State
    ... It does not matter for the error when you register some dlls. ... Unable to view event log and some tabs of user's properties on SBS, ... regsvr32 oleaccrc.dll ...
    (microsoft.public.windows.server.sbs)
  • Re: Calling .NET COM object from MFC application
    ... MFC exe calls C# managed DLL which in turn calls other ATL/MFC COM DLLs, ... All the COM and .Net DLLs must be registered on the "clean" machine or they ... assembly (which is properly configured to "Register for COM interop"), ... trying to initialize this "third party" COM. ...
    (microsoft.public.vc.mfc)
  • Re: SBS2003 backup fails every night (sometimes it works manually)
    ... worked.Many patches and reboots.You may want edit your register DLLs ... I am aware of much different articles/solutions to register dll's and I ... I just did a vssadmin list writers and there are a lot in state 5: ... "Jim Behning SBS MVP" wrote: ...
    (microsoft.public.windows.server.sbs)
  • Re: SQLDMO with VB6
    ... client side functionality without the need to install the SQL Server Client Utilities. ... MDAC does not install the Sqldmo.dll file or any of the many dependent DLLs associated with the ... You need to register COM based DLLs through the Regsvr32 utility. ...
    (microsoft.public.sqlserver.tools)