>I found the solution to the problem! Blame FIFA <bg>.
>
>I looked at properties of the tables of my application vs. the TEST table I was creating in Stored Procedure. What I found is that the TEST.DBF had ASPNET as one of the users/user groups in the Property Security page. That is, since the ASP.NET was creating the table it was assigning itself as the "owner" of the table. All my application tables don't have ASPNET as one of the users/user groups. I added ASPNET to a couple of tables and set the Full Permissions to the ASPNET user for those tables and then the tables became editable from the ASP.NET application.
>
>This behaviour is different from the one I experienced before on Win2000 computer. On Win2000 you don't have to do it, that is you don't have add ASPNET to every table. On Win2000 ASPNET automatically had Full Access to every table. The problem I was experience today is on XPPro PC where the rules must have changed.
>
>Thank you ALL very much for your great help!!

Good news! :)