Compatibility issues between SQL 7.0 and SQL 2K

Hi,
We have an application that caters to both SQL 7.0 and SQL 2k.
We use 'suser_id' to get the user Login's identification number. But this
fails in SQL 2k, coz SQL 2k supports only 'suser_sid'.
Is there anyother way out?
TIA
Sundar
Upgrade your code. SUSER_ID is a hold-over from SS 6.5, and before. With
SS 7.0, SIDs replaced SUIDs. SS 7.0 continued to support the function but
SS2K has dropped it.
However, both SS 7.0 and SS2K support SUSER_SID. So, there's your common
point. Make the switch.
Other option is to write your code with path logic using SELECT @.@.VERSION to
tell you which command to execute. However, SUID is an incompatible
attribute with SID. So, it sort of depends on how you are using it.
Sincerely,
Anthony Thomas

"Sundar" <Sundar@.discussions.microsoft.com> wrote in message
news:40344016-CAE0-4437-923A-3852D86CD3C8@.microsoft.com...
Hi,
We have an application that caters to both SQL 7.0 and SQL 2k.
We use 'suser_id' to get the user Login's identification number. But this
fails in SQL 2k, coz SQL 2k supports only 'suser_sid'.
Is there anyother way out?
TIA
Sundar