Database References Work - Sometimes
Hi,
I'm having a problem with my database references. When I make changes to my project settings, my database references become invalid, and cease to function. Nothing changes on the database references themselves, but I just get a ton of errors, because it no longer sees the references. It's like they don't exist, and so that other databases don't exist.
My work-around is to remove the references, and then re-add them. This is, however, annoying. Have you seen this bug, and if so, is there a way to keep it from happening?
Thanks,
dcb99
[578 byte] By [
dcb99] at [2008-1-10]
Furthermore, when the reference variables aren't working, there is no good feedback as to what the problem is. So, it might be correct, and it just doesn't work (above use case) or there might actually be a new error that I just introduced somehow. I can't tell the difference from the output window. This essentially makes using database references a trial and error operation. Any way to get better feedback?
thanks,
dcb
I did find that if I right-click and select Validate SQL Syntax I get the following output in the Messages pane:
A fatal error occurred.
Variable LINK could not be found.
Where $(LINK) is the variable name I specify when I setup the reference. Any help on this would be greatly appreciated, because I am dead in the water here.
thanks,
dcb99
I'd be very interested in seeing this. If it's not too much trouble could you send me your solution + project files to
patrick.sirr @ microsoft.com (remove the space from the email)? If you don't want to send your sql source that's ok - I just need the sln and any projects. Also what property are you setting that seems to break your references? thanks,
Patrick Sirr
Patrick,
It seems that for now it is only occuring on one machine. When I get the source to a different machine, then I don't have this problem. If I get the source to a different path on the same machine, I still see the problem. So, it seems unlikley that it is due to any project/solution settings. Shall I send you my vpc image? ;-)
Seriously, let me know if you still think seeing the project and solution would be helpful. Not being able to use one of my machines is painful, and who know when it will happen to me other machine.
BTW, the problem has morphed so that I cannot use the work around anymore. It just doesn't work. I can delete and readd references and it just errors out the same.
Thanks,
dcb99
There's a couple more things we could look at. To get more information could you turn on trace and email me the result?
Windows Registry Editor Version 5.00
[HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\8.0\DBPro\Tracing]
"LogDir"="%APPDATA%\\Microsoft\\VisualStudio\\8.0\\DBPro\\Trace"
"PrefixTime"=dword:00000001
"PrefixPid"=dword:00000001
"PrefixThreadId"=dword:00000001
"TraceSwitch"=dword:00000004
"TraceToLogFile"=dword:00000001
"TraceToEventLog"=dword:00000000
"TraceToDebugOutput"=dword:00000001
"DisplayCallStack"=dword:00000000
"UniqueLogFile"=dword:00000001
"EventIdsToTrace"=dword:0001f7ff
Just run Visual Studio with this tracing enabled, cause and then fix the references problem. The log file will appear in the location specified by "LogDir" above.
Also could you send me the .dbproj file that exhibits this failure and then one that is working correctly? Is there a difference or does the problem go away when you unload/reload the project?
thanks,
Patrick
