| buy@suntowersystems.com 2006-01-27, 6:55 pm |
| have never seen this before. We have a legacy app which uses the SQL
driver (SQL2k). For all users it works fine--as expected BUT for anyone
with
full admin rights on the server (W2003 R2).
When any browse opens, the window opens, but the records in the initial
browse never display (IOW one sees a browse with no records and an
endless
hourglass.) So... you click the [X] to close the app and get the
Windows
'Not responding' message. You click 'No' to keep the EXE alive and et
voila!
The records are now there. Now try to edit a record or close the
browse...
same dance again: you have to attempt to close the app, then get the
End
Task Window and then the window responds.
My first guess is that the system is waiting endlessly for a response
to a
fetch or open or close from MSSQL.
But here's the wacky part (at least to -me-). If I run the app as
another
user (anyone besides someone with Admin rights), the app again runs
-fine-.
BTW: the db is -not- running in trusted login---the app is supplying a
connection string with the proper db user name and password. Plus the
Admin
has the same rights (and more so) on the network as 'Everyone'.
Anyone got a clue?
TIA,
---JC
|