Looks like it was not fault of ASPDataSource. Me or ASP itself, not sure at the moment:) I'll update you later (I almost got it to work just as I want it to be).

 

Update: For the lurkers, it was not due to change from DevforceDataSource to ASPDataSource but to a glitch in ASP.Net itself. During conversion I unintentionally removed a code line which made it to work before. It doesn't seem logical to me but it works when in Page_Load I have:

 

{

//...

  bool dummy = (grdPerson.SelectedDataKey != null);

}

 

Invoking get is appearantly forcing a kind of refresh for the selected record.

For the Ajax problem I will send you both DevforceDataSource version (3.5.3.1) and the ASPDataSource version (3.5.4.1) along with the partial MSSQL data ASAP so you can reproduce there.

 

The ZIP file I am attaching has the source code for the EntityAdapterManager.cs.

 

 

 

 

public class EntityAM:EntityAdapterManager

{
  public void DoStandardUpdateByPk(PrimaryKey pk,
                IDictionary  newvalues)
  {
     Entity ent = this.PersistenceManager.GetEntity(pk);
     UpdateProperties(newvalues, ent);
   }

   }
}

 

UpdateProperties are used by both UpdateEntity() and InsertEntity().

 

It works. I'm not sure if I'm doing it right ( DoStandardUpdateSingleEntity() was protected so I did mine this way ). Could you tell me if there were a better way.

 

PS: I did first with DevForceDataSource and made it to work with Ajax. Converting to ASPDataSource, lost Ajax behavior I had successfully before.

It was a GridView and DetailsView and what specifically happens:

It updates DetailsView if SelectedIndexChanged but when PageIndexChanged it updates 'with previous record data'.  Before with DevforceDataSource it was working just as I want it to be.

Working on it (actually doing from scratch now) and would appreciate if anyone has an idea what I may be missing.

Thanks in advance.

 

I would like to see a forum section devoted to ASP.