>View|Toolbars|Customize
>Commands|File|Make <Project> and drag it to your toolbar
I've already got this bit, it was the OK and Yes clicks I was trying to
avoid (yup, I'm lazy).
>However VB will always prompt to overwrite an exising file.
I know, that's the annoying bit.
>I guess you could write an add-in but it seems like a lot of work to
>save a click.
I looked at this once when I was messing with creating add-ins, but it
seemed so much work for such a small thing that I never bothered.
Shame, it's a really irritating feature that could easily have been
avoided. Half a moment's thought would make you realise that the vast
majority of compiles must be overwriting an existing file. Why force the
developer to confirm the location and then confirm the overwrite ? Ho
hum.
Thanx for the reply
>> Hello,
>>
[quoted text clipped - 16 lines]
>> http://www.newsfeeds.com - The #1 Newsgroup Service in the World!
>> -----== Over 100,000 Newsgroups - 19 Different Servers! =-----

Signature
Alan Silver
(anything added below this line is nothing to do with me)
Larry Serflaten - 29 Jul 2004 15:06 GMT
"Alan Silver" <alan-silver@nospam.thanx> wrote
> >However VB will always prompt to overwrite an exising file.
>
> I know, that's the annoying bit.
Tools > Options > Environment (tab) > Don't Save Changes
When selected, the program will just compile and run....
LFS
Alan Silver - 29 Jul 2004 17:16 GMT
>> >However VB will always prompt to overwrite an exising file.
>>
[quoted text clipped - 3 lines]
>
>When selected, the program will just compile and run....
I was asking about compiling the program, not running. I have this
setting set to save changes when I run, but that's not the issue here.
ta ra

Signature
Alan Silver
(anything added below this line is nothing to do with me)