The scene:
SQL 7 on Win2k server - Windows network (no domains)

I exported/saved to VB two DTS's. One imports a tabbed file. The
latter joins the import to the data table and exports the query results
to a fixed-length text file.

The import file is on the server. The export destination is on another
server's shared folder.

I fiddled with the VB into a single app and compiled it with VB 6. The
goal was to make the import file name the variable to a constant process
(export file name derived from the import file name.)

Trouble:
It's worked fine for me for months. Now I've an associate who is to use
this app. When she runs it the import to an SQL server table (1st step)
works fine. However, the export side is resulting in nothing. And it
still works fine for me (my login.)

The app was pretty down and dirty -- it simply reports that it is done
without any information on success or failure.

I thought it was generating reports to the server's application error
log but, subsequence trials result in no new reports.

I can't think of any way it becomes a user level issue. The app has my
identity as it's connection information and the SQL server is constant.

Any ideas?

thx
md

PS- we run it directly on the server via terminal services but the
problem is client terminal independent.

*** Sent via Developersdex http://www.developersdex.com ***