-
Hi,
This has already been covered I expect but for the sake of trying to find it....
Can someone please tell me why this doesn't work :
lngResult = apiCreateShellLink("..\..\desktop\", "Quick View", lblPath.Caption & "\Quickview.exe", "")
When I have declared the following in a module (global)
Public Declare Function apiCreateShellLink Lib "STKIT432.DLL" Alias "fCreateShellLink" (ByVal lpstrFolderName As String, ByVal lpstrLinkName As String, ByVal lpstrLinkPath As String, ByVal lpstrLinkArgs As String) As Long
Thanks in advance
Vince
-
What version of VB are you using?
-
("..\..\desktop\" may be the problem.
that will move up 2 directories and down into desktop. If that path doesn't exist (based onyour current directory) then it will fail)
try this: "\windows\desktop\"
and even that will fail on some systems.
The \windows\ is the os path and you have to use api to find it.
if you think this is bs, it would in fact fail on my system. I have a winme directory and no windows directory.
-
Sorted it
Matthew : vb6 dunno which sp
Lord Orwell, hmm poss but as you said wouldn't work on them all (desktops I mean)
I changed a lil bit of the code :
lngResult = apiCreateShellLink("", "..\..\desktop\Quick View", lblPath.Caption & "\Quickview.exe", "")
and it seemed to work fine. I don't know what the first parameter is but leaving it blank suggests it pulls a default directory from windows...
Thanks for your help though
Vince
PS: Any ideas on custom installation packages - my program is 49k but reques dlls of 3 mb .....
-
Do you have vb4 as well because STKIT432.DLL is a Vb4 file.
VB6STKIT.DLL = VB6
-
Nope - no vb4
I assumed it came with vb6 as the package and deployment part ?
Anyways - I have managed to get it working - although I am unimpressed with the P & D, my 49k proggy need 3mb of dlls :/ nasty.
Just for the tree view, and a couple of other dlls I require.
Wonder if I can get these dlls and have a package to see if they are on the system or not, then install them only if they are newer... or non existant...
Regards
Vince
-
leave out the msvbvm60.dll
its already on 99% of systems. And include a help file to a download site in the unlikely event they don't have it.
I use vb5 cuz EVERY version since windows for workgroups comes with its runtime.
