Board index » Visual Studio » Saving VB Startup info without exiting VB

Visual Studio104
I seem to recall there being some kind of shortcut to be able to save the VB

environment settings without having to exit and re-start VB, specifically, I

want the system to save the current state of open code windows.



I've got some kind of exotic bug, most likely with Office 2000, which causes

VB to crash sporadically, usually when I receive an e-mail in Outlook. It

doesn't happen every time, but it's a pain. Usually, I can click the save

button while the error dialog is up, able to save my code, but sometimes it

just flat-out unloads VB completely with no messages. I've search the net

for some time and found a couple others who have the exact same problem, and

it seems to have Office 2000 as the common culprit, but no solutions seem to

exist.



What's most annoying about this, however, is that even in the instance where

I can hit the save button and save the code, and even if I then close VB

myself instead of hitting the OK button in the error dialog, it does not

save my currently open windows. When I start back up, it's restored to the

previously normal shut-down.



Is there some way, say holding ctrl or shift while clicking save, to save it

without exiting?



FWIW, I tried updating Office 2000, but it thwarts my every effort to

install service packs, it doesn't recognize our (legit) CD's.



--

Fris "Stuck in SP1" bee®, MCNGP #13



The MCNGP Team - We're here to help!

www.mcngp.com



Certaholics

groups.yahoo.com/group/certaholics


-

"Frisbee®" <billLASTINIT@dasi-software.com>wrote in message

You're slightly mistaken or have been misinformed. The settings for your

code windows are saved when the project is closed....not when VB closes

(since the project closes when VB closes, however, these settings are saved

then too). I know of no way to explicitly save them. But you could just

save your project, start a new project (or open a different project), and

then re-open your project. It'll be the first project in your MRU (under the

File menu) so it's very quick and easy to re-open.



Here's a trick: if you want your code windows to always initially open

having the same size and position (and even which ones are shown and which

ones aren't), resize and position them accordingly. Save your project,

start a new project, go to Windows Explorer, and set the read-only attribute

for the .vbw file (located in same folder as the .vbp file and also has the

same name except for the extension). This is the file where these settings

are saved. By making it read-only, VB won't overwrite it with different

settings.



Mike





-

MikeD wrote:

Ah, yes, that certainly makes sense, saving the settings with the project.

I do have only about 4-5 projects that I work on, but the main one is

something like 30-40 forms and modules and takes quite a while to load on

this system. I do have, however, a couple of really small projects, and it

would make sense to simply load one of the small ones, then reload the main

one again, thanks for that tip. Oh, well, I don't have the fastest computer

in the world right now, and even that takes a while, but it's at least a

little faster than simply unloading and reloading VB. Hmmm... would "save

project" work, or is that what the diskette icon does anyway?



I've seen that trick posted before, and it's a good one, too.



Thanks for the feedback.



--

Fris "Back to our regularly scheduled system crash" bee®, MCNGP #13



The MCNGP Team - We're here to help!

www.mcngp.com">www.mcngp.com



Certaholics

groups.yahoo.com/group/certaholics">groups.yahoo.com/group/certaholics



-