Talking to myself...

I just read Rick Strahls article on VFP and it's OleDB (http://west-wind.com/presentations/VfpDotNetInterop/vfpDotNetInterop.htm) , and have decided to move and access all my data in SQL server. VFP OleDB just makes you work way too much work for .NET updates...

Pertti

>I am using MM.NET C# on a web app, with VFP backend.
>
>When I try to save changes from a detail screen, everything SEEMS to go fine, but when I reload the page, my changes are gone.
>
>Here's the code that should do it -- what might I be missing here?
>
>

>DataSet dsPermit = (DataSet)Session["dsPermit"];
>
>   if (this.Save(this.oPermit, dsPermit, this.oPermit.TableName) != mmSaveDataResult.RulesPassed)	
>   {
>	Response.Write("<script language=JavaScript>Alert('Changes could not be saved'))</script>");
>	
>   }
>

>
>I have two way databinding for all controls. While I'm on the detail screen, everything looks ok, no errors when clicking save, but when I exit the detail screen and come back to it later, the data has reverted back to what it was. I can read data fine, but saving it is the problem. Is this a VFP problem? (I do have full access set for ASPNET user on the VFP data folder)