[RESOLVED] VBA Shell Problem

[recarv]

I'm working on a program written in VBA that uses the Shell() function to call a command line executable. The problem is that this code never outputs to the file "checksum"

Call Shell("C:\instagram\md5sum\fciv.exe C:\instagram\replicated\" & ThisWorkbook.user & "_binlog.txt > C:\instagram\replicated\checksum")

Does anyone know why this code might not be working correctly?

I've run this from cmd shell and it goes off without an hitches.

Thanks in advance,

Ross

[Hack]

Moved from ClassicVb.

[zaza]

I think I attempted such things before, and came to the conclusion that you can't use Shell to pass a command line argument. As I recall, you can do a workaround in terms of running cmd.exe and then sending it keys, but I don't think you can do it directly like that.


But I'm prepared to be wrong.

zaza

[RobDog888]

Here you go zaza. I added the parameters how I think you need them. Not sure if the working directory is the right one either. Also, ThisWorkbook.user does not show for me so I assume its a custom property or function.

Option Explicit
 
Private Declare Function ShellExecute Lib "shell32.dll" Alias "ShellExecuteA" (ByVal hwnd As Long, ByVal lpOperation As String, _
ByVal lpFile As String, ByVal lpParameters As String, ByVal lpDirectory As String, ByVal nShowCmd As Long) As Long
 
Private Const SW_HIDE            As Long = 0
Private Const SW_SHOWNORMAL      As Long = 1
Private Const SW_SHOWMINIMIZED   As Long = 2
Private Const SW_SHOWMAXIMIZED   As Long = 3
 
Private Sub CommandButton1_Click()
    ShellExecute Application.hwnd, "Open", "C:\instagram\md5sum\fciv.exe", "C:\instagram\replicated\" & ThisWorkbook.user & "_binlog.txt > C:\instagram\replicated\checksum", "C:\instagram\replicated", SW_SHOWNORMAL
End Sub

I also have written code to shell the CMD.exe and output to a file if you need it.

[zaza]

Aha, the old "ShellExecute" trick.

Nice one RD.

But I still don't think you can do it just by passing the whole string to Shell().

zaza

[RobDog888]

Did it work though? Also shouldnt checksum be a file and not a directory?

[zaza]

Actually, the code isn't for me...


I'm sure he appreciates it, though.

[recarv]

Actually I found a near identical code snippet on the net elsewhere and still doesn't seem to work.

However, I found another workaround to accomplish the task I needed.

I wanted to make sure that in between programmatic writes to the binary log someone did not enter in their own statements. As the bin log will be used as publisher to a database this could be disasterous.

Anyway, if anyone cares, instead of writing the binlog to a file everytime, it writes to a BLOB field in a table. Only when the binlog is finally being used is the contents of the BLOB written to the file, thereby ensuring no tampering in the meantime.

Even better, and MD5 in mySQL of the BLOB before the write, then a re-read of the binlog file back into the BLOB and an md5 after (before committing a transaction) provides yet another check

Anyway, I think zaza is correct.

Thanks anyway.

R