Strange Behavior, Invalid Field no matter what I name it.

Question

Post reply

Strange Behavior, Invalid Field no matter what I name it.

bob-732781

SSC Rookie

Points: 34
More actions
April 30, 2010 at 1:11 pm

#232233

Hello;
I have a really weird problem, should be simple, but it doesn't seem so. Here's my environment info:
Microsoft SQL Server Management Studio10.0.2531.0
Microsoft Analysis Services Client Tools10.0.1600.22
Microsoft Data Access Components (MDAC)6.0.6002.18005
Microsoft MSXML3.0 4.0 5.0 6.0
Microsoft Internet Explorer8.0.6001.18904
Microsoft .NET Framework2.0.50727.4200
Operating System6.0.6002
First off I have a table like so:
CREATE TABLE [dbo].[FriendReferrals](
[UserGuid] [uniqueidentifier] NOT NULL,
[FriendUserGuid] [uniqueidentifier] NULL,
[FriendEmailAddress] [nvarchar](255) NOT NULL,
[Name] [nvarchar](255) NOT NULL,
[Comment] [ntext] NULL,
[CreatedUTC] [datetime] NOT NULL,
[FromIpAddress] [nvarchar](50) NULL,
[IsRegistered] [int] NOT NULL
CONSTRAINT [PK_FriendReferrals] PRIMARY KEY CLUSTERED
And I have a simple SP to insert to the Table.
INSERT INTO [dbo].[FriendReferrals]
(
[UserGuid],
[FriendUserGuid],
[FriendEmailAddress],
[Name],
[Comment],
[CreatedUTC],
[FromIpAddress],
[IsRegistered])
VALUES
(
@UserGuid,
@FriendUserGuid,
@FriendEmailAddress,
@Name,
@Comment,
@CreatedUTC,
@FromIpAddress,
@IsRegistered
)
Now, in Query Analyzer, the last field "IsRegistered" is called "Invalid Column Name 'IsRegistered'". ( bold is for emphasis).
1. I have dropped and recreated the table.
2. Dropped and created the table with a DIFFERENT column name
3. added new fields after IsRegistered.
4. Dropped and recreated the Insert SP.
And still have the same ""Invalid Column Name" for IsRegistered, any different named field, or any new field.
I've cycled SQL server as well.
Any Ideas? I'm stumped....

Viewing 4 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic. Login to reply

Lamprey13 SSCertifiable Points: 6210 More actions · Answer 1

I assume that the create script you posted is in error because of a cut-n-paste error?

Just wanted to check that the table is actually being created. 🙂

Lowell SSC Guru Points: 323546 More actions · Answer 2

the script you pasted, assuming a missing closing-parenthesis, makes [IsRegistered] the table's primary key; was that the desired results? was there something missing like a comma and the rest of the constraint? the name of the column implies a 0/1 kind of boolean-type data as expected values.

Lowell

--help us help you! If you post a question, make sure you include a CREATE TABLE... statement and INSERT INTO... statement into that table to give the volunteers here representative data. with your description of the problem, we can provide a tested, verifiable solution to your question! asking the question the right way gets you a tested answer the fastest way possible!

bob-732781 SSC Rookie Points: 34 More actions · Answer 3

Well thanks anyways guys. I figured it out.

And yes I omitted stuff in the paste for brevity.

What the issue ended up being is that the Intellisense ( there's an Oxymoron) stopped working. In all my machinations of the database and the SP I assumed ( yeah I know), that the Intellisense would keep up.

Anyway, after a Shift+Ctrl+R, things are working. I haven't a clue why the intellisense decided to mess up and cost me half a day.

I can do without a helpful feature like that, and turned it off...

THanks again.