Member Avatar for bassgeek

Hello all. I was hoping maybe someone could help me out with my problem that I am having right now(well not me, but a co-worker at work).

We use Visual Studio.Net 2003 along with Reporting Services here at where I work. Well, all is going good for all the clients that use Visual Studio.Net except for one person(isn't it always like that?)
This one person has the following problem:in the data tab, any change the client makes to the sql select code automatically throws in the word "with" and windings at the end of the phrase. If you try to edit the SQL statment, the wingdings return. Not very useful or fun if you ask me. I haven't been able to find anything on the web yet, and was hopin that maybe someone could shed some light on the situation. And just as an FYI. We have fully uninstalled and then fully re-installed the program. And it is only happening to this one person. :mad: So if you have any ideas, please shoot them this way!

  • 3 Contributors
  • 2 Replies
  • 134 Views
  • 3 Days Discussion Span
  • Latest Post Latest Post by jbennet

Dani AI

Generated

The symptom—SQL text in the Data tab gaining an extra word and then rendering symbol glyphs—points to a localized editor/font or input-hook problem rather than a general Reporting Services bug. Given the thread, follow a short, ordered diagnostic flow to isolate where the substitution comes from (and avoid an unnecessary OS reinstall as suggested by until the cause is known). Also note 's advice about keeping the VS install patched.

A practical isolation sequence:

  • Test the same SQL outside VS (Notepad or SQL Query Analyzer). If the corruption appears there too, the issue is system- or keyboard-level. If it is only inside VS, it is an IDE- or profile-specific setting.
  • Test under a different Windows user account on the same machine. If a new account is clean, the problem is in the user profile or per-user VS settings.
  • Check the editor font and any editor-specific mapping. In VS go to Tools -> Options -> Environment -> Fonts and Colors and confirm the Text Editor / SQL Editor font is a normal monospaced font (Courier New, etc.) rather than Wingdings.
  • Disable add-ins/macros (Tools -> Add-in Manager) and scan for keyboard-hook utilities (AutoHotkey, Macro tools) in Task Manager or startup items.

If the problem persists after those steps, remove or reset per-user Visual Studio state (after backing up registry and folders). Relevant locations include:

HKCU\Software\Microsoft\VisualStudio\7.1
C:\Documents and Settings\<user>\Application Data\Microsoft\VisualStudio\7.1

Backing up those keys/folders, then deleting them and launching VS will force creation of default user settings.

Additional checks: verify the Wingdings font file under C:\Windows\Fonts is not corrupted (copy from a known-good machine if needed) and review installed input languages/IME mappings in Control Panel. If all else fails, creating a fresh Windows profile or re-imaging the workstation is the final step.

Recommended Answers

All 2 Replies

Member Avatar for Member #46692

reformat their hard drive

Member Avatar for jbennet

Have you get the newest service pack for Visual Studio 2003? (dont use the check for updates function , it is broken in that version. Instead run Microsft Update (NOT WINDOWS UPDATE))

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.