Contact US

Log In

Come Join Us!

Are you a
Computer / IT professional?
Join Tek-Tips Forums!
  • Talk With Other Members
  • Be Notified Of Responses
    To Your Posts
  • Keyword Search
  • One-Click Access To Your
    Favorite Forums
  • Automated Signatures
    On Your Posts
  • Best Of All, It's Free!

*Tek-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail.

Posting Guidelines

Promoting, selling, recruiting, coursework and thesis posting is forbidden.

Students Click Here

Help stop batch run on double-click in Windows

Help stop batch run on double-click in Windows

Help stop batch run on double-click in Windows

I use SAS (8.0) on several different Windows computers at work.  On all except one, the default behavior when a *.sas program file is double-clicked is that SAS opens with the program ready in the Enhanced Editor window.  But on one, a double-click starts the program in batch mode.  This drives me  crazy!  How do I reset this???

I'm not sure if this is a SAS question or a Windows question, but I'm sure there's some simple answer somewhere...

Thanks very much!!

RE: Help stop batch run on double-click in Windows

I think this is more of a windows question.  Here is a pdf that SAS gave me a while back when I was automating the runs of certain SAS jobs.  It gets you to the right place in Explorer (edit file type) and you should be able to see how one computer is doing it instead of the rest.


RE: Help stop batch run on double-click in Windows

Perfect!  This document helps not only with the double-click problem, but gives a good summary of automating SAS jobs-- which I'll be getting to soon.  Thanks!!!

RE: Help stop batch run on double-click in Windows

When I automated a bunch of my SAS stuff about a year and a half ago it was SLICK.  

One batch file with many sas programs in it does most of the work for our plant now.  

One small thing that I did that might help you.  The .log files (one for each SAS program) will be 'plopped' into the directory where the program is.  This is great unless you have a job that runs on a scheduled basis and you want to see why the records did not push from one DB to another last night (fictional example - HA!).  So... I started copying the .log files to someplace else on the server and renaming them with a time/date stamp --- no fun to do (I did mine in SQL 2k because it was easier & then I trigger this to run at the end of each sas program by just adding a record to a table when it starts and ends in a tiny DB - job history)...

make sense?

Red Flag This Post

Please let us know here why this post is inappropriate. Reasons such as off-topic, duplicates, flames, illegal, vulgar, or students posting their homework.

Red Flag Submitted

Thank you for helping keep Tek-Tips Forums free from inappropriate posts.
The Tek-Tips staff will check this out and take appropriate action.

Reply To This Thread

Posting in the Tek-Tips forums is a member-only feature.

Click Here to join Tek-Tips and talk with other members! Already a Member? Login

Close Box

Join Tek-Tips® Today!

Join your peers on the Internet's largest technical computer professional community.
It's easy to join and it's free.

Here's Why Members Love Tek-Tips Forums:

Register now while it's still free!

Already a member? Close this window and log in.

Join Us             Close