Logn error

I'm having a bizarre error occur with one specific user. For starters, I hav
e
an SQL back-end with an Access data project front end. All of my users are
members of a SQLUSERS group, with the correct permissions.
When one specific user, Zack, logs into the db, he does so under the
SQLUSERS group. Everything runs smoothly until Zack tries to perform a
particular action that imports data from a fixed-width text file on CD. When
he does this, the system adds Zack as a separate user, even though he's
already part of the SQLUSERS group. The new Zack user inherits the
permissions from SQLUSERS, and during the data import process the system
creates new tables for Zack. Some fields don't have the correct data types,
which causes an error. Zack becomes the owner of these new import tables.
When any other member of SQLUSERS performs the same action, the system
deletes the data from, and reuses the existing tables.
Has anyone encountered anything similar to this?Hi
SQL Server will not create new users on it's own, therefore you have some
code that will be doing this. If your code is creating new (staging) tables
then zack will own them if he is not the dbo or a sysadmin. If the tables do
not already exist I would expect the same behaviour for other users that hav
e
the same privileges for Zack unless your code is conditional on who is
running it. If permissions are granted to the SQLUsers group other users may
be able to access and truncate the tables. For these users the code must kno
w
that Zack is the owner and referencing them using it.
You should review the code and/or use profiler to see what statements are
being sent to the database.
John
"mike" wrote:

> I'm having a bizarre error occur with one specific user. For starters, I h
ave
> an SQL back-end with an Access data project front end. All of my users are
> members of a SQLUSERS group, with the correct permissions.
> When one specific user, Zack, logs into the db, he does so under the
> SQLUSERS group. Everything runs smoothly until Zack tries to perform a
> particular action that imports data from a fixed-width text file on CD. Wh
en
> he does this, the system adds Zack as a separate user, even though he's
> already part of the SQLUSERS group. The new Zack user inherits the
> permissions from SQLUSERS, and during the data import process the system
> creates new tables for Zack. Some fields don't have the correct data types
,
> which causes an error. Zack becomes the owner of these new import tables.
> When any other member of SQLUSERS performs the same action, the system
> deletes the data from, and reuses the existing tables.
> Has anyone encountered anything similar to this?