As already pointed out this proves two things:

1. The local service installed by the application is using one and only one login for all users

If that system is using SQL Authentication instead of Windows authentication you will get that

Correct! it is easier and more efficient to simply add the tableName at generation time.

Now, what I consider no such a good Idea is to create the triggers on the fly...

you can get it from sysobjects using parent_obj:

CREATE TRIGGER ...

select object_name(parent_obj) as Tablename

from sysobjects

where  id = @@procid and xtype ='TR' 

but I don't know why would you do that?

He he its been a while I had to do many many things at once and the light still not at the end...

If you have SP4 installed you need a hotfix

http://support.microsoft.com/default.aspx?kbid=899761

Well, a little bit of clarification was needed because if you look closely, the poster did enable the settings in the code but didn't at creation time

I think your error is at creation time!

try:

SET QUOTED_IDENTIFIER ON

GO

SET ANSI_NULLS ON

GO

SET ANSI_WARNINGS ON

GO

CREATE PROCEDURE [dbo].[sp_ReceiDistributing]

@Transdate datetime

AS

...

looks like your client app is not using SQL authentication and instead you have something runing as local system account ( a service, maybe) which is the one that is...

Windows 2k resource kit

actually is very easy to do it. If you put it on the model all new databases will inherit the procedure but if the databases are already in place you...

Have a look at SETX (on the resource kit)

The easiest way about it is probably to create a global temporary table (##)

then with the same stored procedure in each database call it as:

exec dbname.dbo.procname @param1, @param2 ...

Sorry but I differ:

FROM BOL:

Permissions

DBCC CHECKIDENT permissions default to the table owner, members of the sysadmin fixed server role, and the db_owner and db_ddladmin fixed database role,...

Let me warn you that dbcc checkident requires elevated priviliges