Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Chris Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Search results for query: *

  1. Norm11

    Designating a Script Engine for Custom File Extension

    OK, let me back up. The attachment isn't VBS or VBA or any other script. It's a proprietary filetype used by a commercial tracking application we use here. So I cannot--in any way--change the attachment or its contents. So that file has its own extension provided by the vendor. It cannot be...
  2. Norm11

    Designating a Script Engine for Custom File Extension

    Hello all: So far Tek Tips is batting a 1000 as far as I go--I've posted two questions and received two solutions. Let's see if you have one this time. I've written a VBScript that opens an application via an email attachment. Let me explain. I send users an attachment. Let's say the...
  3. Norm11

    Redirecting Standard Output and Hiding Command Prompt

    Well, sure enough, calling it with cscript.exe rather than wscript.exe fixes the problem. Using cscript.exe invokes a command window when the script starts, but subsequent windows do NOT appear, which was my number 1 concern. So thank you very much for your help. You solved my problem. One...
  4. Norm11

    Redirecting Standard Output and Hiding Command Prompt

    How do I check the version numbers?
  5. Norm11

    Redirecting Standard Output and Hiding Command Prompt

    Yeah...I've tried that. Interestingly, I do get different results. When I do it with cscript, it runs. With wscript, it does not. With cscript the message is displayed in the command prompt window, though. I'm changing my file association right now to cscript to see what it does when I...
  6. Norm11

    Redirecting Standard Output and Hiding Command Prompt

    By double clicking.
  7. Norm11

    Redirecting Standard Output and Hiding Command Prompt

    If I comment out the four lines like below, the script runs just fine. With them uncommented, it does not run. Set objShell = WScript.CreateObject("WScript.Shell") Set oShell = WScript.CreateObject("WScript.Shell") 'If Instr(1, WScript.FullName, "CScript", vbTextCompare) = 0 Then '...
  8. Norm11

    Redirecting Standard Output and Hiding Command Prompt

    Yes, this is very interesting. I copied and pasted your code into a new .vbs and ran it. The same thing happened--it doesn't work. I wonder if there's a difference in the scripting engine or something...
  9. Norm11

    Redirecting Standard Output and Hiding Command Prompt

    Thanks for the suggestion. I've already tried this trick, but it doesn't work. It seems to halt standard output all together--not just suppress the command prompt window. My script without your code works perfectly except for the command prompt window showing. When I add this to the script...
  10. Norm11

    Redirecting Standard Output and Hiding Command Prompt

    Hello! I've been working on this problem for days. I've Googled high and low for a solution, but no dice. Here's what I want to do. Through my VBScript I want to execute an external process (program). I want to redirect the standard output of that external process to a string variable. I...
  11. Norm11

    Associating Files with VBS

    Thank you! I did not realize I needed to precede my script name with wscript.exe. That did the trick! Thank you very much.
  12. Norm11

    Associating Files with VBS

    Hello! I'm new here, so I apologize if this has been posted in the past. I want to be able to associate a file type with a VB script I've written. In other words, when my users double click a custom file type (say, .XYZ), my VB Script launches and "consumes" the contents of the file--sort of...

Part and Inventory Search

Back
Top