Problems With Non Deterministic Errors On Calculated Fields

Hi

I am new to SQL Server and am migrating another database

In my original database I have a default(constant) type field and a calculated field both of which call the same user defined function: GetMyUID()

My Function GetMyUID() returns the current date, time and users initials, i.e. "20080522T09:31:15.250LSG"

When a record is first created both fields have identical values

As the record is updated over time my constant field stays constant and my calculated field reflects the time the record was last updated and the initials of that person. So my first field is called 'Created' and my second is called 'Updated'

I would have thought that something like this would be a pretty bog standard and very straightforward requirement in any database

However in SQL I am getting error messages about the return value being non deterministic

I searched the web and found advice that to sort the problem I need to use WITH SCHEMABINDING in my function definition

Unfortunately I am still getting the same 'non deterministic' error

I wonder if (in the quest to not have an overlong field) by looking up the persons initials from a 'STAFF' file rather than leaving the username in full tacked on to the end that this is causing the problem?

I can't imagine that what I am trying to achieve is rocket science but unfortunately have not been able to find any resource on the web that solves this issue for me

In desperation I turn to you

Please help (preferably by letting me have a few lines of code that return the current date/time followed by the username lookup of a Username's initials, here is a snippet of my code...


RETURN (Convert(VarChar(8),@DateTimeNow,112)+ Right(Convert(VarChar(30),@DateTimeNow,126),13)+dbo.myInitials())

Where the dbo.myInitials() calls:

RETURN (SELECT STAFF.Code from dbo.STAFF where STAFF.Login = dbo.myLogin())

and dbo.myLogin() calls

return UPPER(Right(System_User,PATINDEX('%\%',System_User)))