Hi Olaf,
(or others who might know.)
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)

I work from two locations, laptop and desktop so I schlep a usb hd around
with my code files on it

vb6 instlalled in c:program files on desktop and  d:program files on laptop

originally i thought they should be either in winnt\system32 or \Program
Files\Microsoft Visual Studio\VB98
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?

would a single coder (not on a team) typically put all dlls in one central
location?

any thoughts?

thanks
mark

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.

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).

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

Show quote Hide quote but with an USB-Disk there's always a somewhat
LOL
oh yeah, especially cause my company name is Ace Destruction Co. and one of
my company mottos is "Gravity Never Sleeps" (tm)
Thanks for the response and insight
I guess it's no big deal to change the refernece in the vbp from home to
work when I change location

and thanks again for sharing that great code!
Mark

VB 10 To Support Native Exe/DLL
Is there anyone uses VS6 on Windows2000 Pro?
Exiting from a Do Loop
Advice on storage and retrieval
Closing recordset
Decimal to Longs
Excuting a command line program from within VB
Hyperlink in a CSV
What are &H100&
Real Runtime Control -?-