I actually honestly believe that this problem might stem from my SQL
2005 Express installation, but since it occurs in Whidbey I figured I'd
post here.
My problem is that I can't create a new datasource in whidbey using the
add new option in the data menu. I get a messagebox with an error such
as the following:
"An unexpected error has occurred.
Please record the following message when seeking support from
Microsoft:
Source:Microsoft.VSDesigner
ErrorCode:-1
Additional Info:None
[OK]"
This error message obviously doesn't help much, and neither has various
search queries with googles been very helpful. Has anyone experienced
this? I've heard suggestions from re-installing VS to re-installing
windows. I've tried the former without any luck. Worth noting is that
the same error is produced either when dragging a table from the server
explorer to the dataset designer window. But get this, it works for ONE
table by dragging from the server explorer, but not any subsequent
tables. Also, adding a TableAdapter produces the same error. This
sounds to me like something might be wrong with the data connection.
However, the event viewer hasn't logged anything which might suggest
something is wrong with my SQL 2005 Express installation, although it
did fail the first time when installing with the VS 2005 installer, so
I downloaded the SQL 2005 Express installation from MSDN. Another thing
worth noting is that I get this dialog before the error (and also
before the first table in the dataset gets added):
"Updating queries can not be automatically generated because your
SELECT query does not include some primary key columns. Do you wish to
add primary key columns to your query?
[Yes] [No]"
Obviously, clicking no aborts the operation. Also, if it's helpful, I'm
connecting to a SQL database file (mdf).
And lastly, I've uploaded a diagram of how my tables looks:
http://hem.bredband.net/b251589/misc/db.png
I'm sorry about the small font. The relationship is as follows:
The Awards and Functions tables have a column called Section which has
a relationship with the Id column in the Sections table. The rest have
a column called Member which has a relationship with the Id column in
the Members table.
Has anyone else experienced this?
