I think you're right - I tend to do dev and debugging on my PC and so it all works fine for me.

No problem about the help - people in this...

When you say 'automatic' - I presume you mean exactly that, ie users do not need to do anything special, they just INSERT to the other fields and the key...

OK - the code is in the right pane and there should be a yellow arrow pointing to the first line of executable code (after any declarations).

Just use the step...

Check out the NEWID() function in BOL and see whether that suits.

There's something fishy going on here - presumably the fields were defined as not null for a reason, in which case you should be populating them with sensible data.  Or...

Sounds promising ...

Debugging: right-click the stored proc in the QA object browser.  'Debug' should be one of the options available to you.

Regards.

OK, no offence intended.

This link may be of interest - they seem to have the same symptoms as you.

http://www.talkaboutdatabases.com/group/comp.databases.ms-sqlserver/messages/123008.html

Other than that, I'm running out of ideas.

Did you use the debugger to track down the NULL problem?  If not, running the stored proc step by step in debug mode might point you in the right direction. ...

Yikes, way too much code for me to trawl through while doing my day job!

Leaving the function as it is, are you able to put the function call (only) in...

No - looks OK from what you've said.  Can you post more info (eg the stored proc definition) so that we can the help further?

OK - so have you run out of growing space?

Use EM if you really have to, but check out this thread first and maybe you'll not worry about it

http://www.sqlservercentral.com/forums/shwmessage.aspx?forumid=5&messageid=98351

Doing this in T-SQL is non-trivial and not recommended.

Does look like a space problem - perhaps with the db itself.  Have you checked to see whether the 'Automatically grow file' property has been set (check the data file...

Seems to me that you might not have gone far enough in your normalisation quest.  I suggest that you should have something like the following tables:

Patient(PatientID, Name, DOB, etc etc)

AandEVisits(VisitID, PatientID,...

Check out this link for some ideas:

http://www.sqlservercentral.com/forums/shwmessage.aspx?forumid=169&messageid=146618