Hi Peter,

Some coments mixed in with your response:

>Well, I checked that or at least tried to.... this is a Windows NT server that I don't have full access to but
>under that assumption that it is NT, permissions shouldn't play a factor like UNIX does.


NT permissions definately do play a role when it is ASP running in IIS accessing files on the web server. The ISUR account on the NT server running IIS has to have read\write permission on the data files. By default, this account does *not* have write permissions.


>
>Here is the current code....
>
> dim DBmiym
> dim DBpath
> set DBmiym=server.createobject("adodb.connection")
> DBpath="sourceDB=" & server.mappath("../new")
> DBmiym.Open "DRIVER={Microsoft Visual FoxPro Driver}; SourceType=DBF; " & DBpath & "; Exclusive=No"
>
> set userSet=server.createobject("ADODB.RecordSet")
> userSet.Open "select * from user",DBmiym,1,3,adCmdText
>
> for each p_del in request("p_del")
> userset.find "userid='" & trim(p_del) & "'"
> userset.delete <<<<<<<<<--------------------------- This is line 20
> userset.update
> next
>
>
>
>Any suggestions?

Does the table have any memo fields in it? While I think this error is permissions related, it could also have a SQL statement length issue. I recall the ODBC driver having problems with either memo fields, or when it generates a SQL statement (as it would for Update or Delete) being longer than 254 characters. Something like this.

I don't think, however, that it would respond with this error. I kid you not, it has to be a permissions issue. A solution is to have your NA verify the permissions on these files for the ISUR account. To be certain it is a permission thing, temporarily give "Everybody" a "Full Control" setting on the files. If this resolves the issue, it is unquestionalbly a permissions thing.