Hi,

I'm working on an app that will use either a SQL Server database or an MDSE database (depending on the client). I have SQL Server 2000 installed on my development box. Now that I'm halfway through developing the app I figured it might be a good idea to actually use SQL Server logins, roles and permissions to make sure everything works OK :-)

This is a reconciliation application for financial institutions written in VB6 that will parse between 1,000 and 60,000 records a day (again, depending on the client) from ACSII text print files generated from mainframe systems from two different sources (extensive parsing is required), insert the data into tables in a SQL Server database, and perform reconciliation functions via stored procedures and UDF's. All the data access and data manipulation in this app is accomplished via stored procedures (users only have execute priviledges on SP's - there are no Select, Insert, Update and Delete priviledges on individual tables). The approach I took in importing the files was to parse the input files and write the formatted output to the local disk using VB6, and then do a bulk insert. This proved much, much faster than importing the records one at a time into SQL Server.

The problem I've run into is that when logged into the app as as a user with a role that "should" permit bulk inserts, I receive the following error when attempting a bulk import:

"The current user is not in the database or object owner of table dbo.BlahBlah.Txns. Cannot perform set operation"

The current user is definately in the database...

Can anyone shed any light into this error message when attempting a bulk insert? (Note: (1) Everything else works OK with respect to executing all the stored procedures in the app an (2) The owner of the table is 'dbo')

Thanks in advance,

Al