I was doing a ^F to search for .cellback when the IMMEDIATE window grabbed the focus - I just thought it was neat that I could cause VB to blow up with such a simple thing as typing garbage in the IMMEDIATE window.
Then I thought to try it in a "new project" to see if it was a VB issue not related to the .VBP I was working on...
*** Read the sticky in the DB forum about how to get your question answered quickly!! ***
Please remember to rate posts! Rate any post you find helpful - even in old threads! Use the link to the left - "Rate this Post".
Problem appears to be "very local" so I suggest to try to reinstall vb entirely.
It was just a curiosity - no value to the issue at all...
If you knew the amount of VB's and VS's and FW's and compact FW's installed on this laptop you would shudder
Currently I cannot get MANAGEMENT STUDIO for SQL 2005 to work properly - I've started using the old SQL 2000 QUERY ANALYZER to get around the problem...
Next machine I get I have to be better prepared for a nuke-and-reload the OS/app's cycle.
*** Read the sticky in the DB forum about how to get your question answered quickly!! ***
Please remember to rate posts! Rate any post you find helpful - even in old threads! Use the link to the left - "Rate this Post".