I have used MSE (Microsoft Development Environment) to debug scripts
for some time. I upgraded my system to Office 2007. The Microsoft
Development Environment is at version 7.0 and the Microsoft Script
Editor says it is version 10.0. Since upgrading, I am unable to do
any print of variables in the Command Window. In the past, I would do
a ?temp to display the value of the variable temp. No it always comes
back with the message 'No Expression'.
I know I can always watch variables but sometimes I do not want to do
this. I have also tried using Debug.Print but get the same results.
Re: Stupefying Crazy and Insane ... The development environment no longer responds. ... God knows what Microsoft is ...continually reuse Foxpro forms simply by renaming them and changing ... Add a resource to your Project, ... (microsoft.public.vstudio.general)
RE: Problem Upgrading evaluation copy ... 818025 Windows 2003 Server Evaluation Copy Expiration Behavior ... 810613 Supported Paths for Upgrading to Windows Server 2003 or to Windows ...Microsoft CSS Online Newsgroup Support... This newsgroup only focuses on SBS technical issues. ... (microsoft.public.windows.server.sbs)
Re: Is there a Visual C++ Net only product ??? ... I sincerely hope folks at Microsoft read these comments and understand how much we truly ... how bad the VS7 IDE is, and trying to solve their problems. ... "The development environment isn't all that bad, it is only DIFFERENT so you don't like ...MVP Tips: http://www.flounder.com/mvp_tips.htm ... (microsoft.public.vc.mfc)
Re: Visual Basic - Which edition ... What costs is the IDE, the development environment.... some of the non Microsoft IDE are free as well. ... I was just worried that the std edition might not> include the tools and resources that I need to communicate with SQL ... (microsoft.public.sqlserver.programming)
