Ya, I switched it to OLEDB first thing. That wasn't my prob.
After 6 or so hours of digging and pulling my hair out, I finally realized
that the user account had access to create and manipulate files in the
directory where the database resided, they just didn't have the right to
delete any files in the containing folder......
ugggg....amazing how when you are so used to not worrying about the minor
issues they will find there way back to you just to remind you that they
need to be paid attention to. 7 years in ASP and I still let something that
simple kick my butt.....just amazing
Another lesson learned in the pay attention to the new permission in w2k3
experience.
"Aaron [SQL Server MVP]" <te*****@dnartreb.noraa> wrote in message
news:#q**************@TK2MSFTNGP10.phx.gbl...
First, try using OLEDB instead of ODBC (see http://www.aspfaq.com/2126).
Next, show us the code that causes a lock, and how you determined that it
was caused by this code.
--
http://www.aspfaq.com/
(Reverse address to reply.)
"Rick Csucsai" <ri**@no-spammm.energyunited.com> wrote in message
news:#w*************@tk2msftngp13.phx.gbl... I have a very simple database call running on a W2K3 server. I moved it over from a W2K box. However, when it is run on the 2K3 server, it leaves a
lock on. It is an ASP page and not and ASPX page. It works perfect on the W2K
box. Anyone else have this probelm or better yet a cure for this
problem? I do not have the time to convert it to ASP.NET yet. The ODBC driver is a
bit different. One is V 4.00.6205 dated 3/2003 the one on the W2K box is
version 4.00.6200 dated 6/2003.