The TAstaProvider is a server side component that allows ASTA clients to be deployed using NO SQL. Using a TAstaProvider and server side SQL generation, you will have access to each Insert, Update and Delete statement before they are to be executed on the server. This allows you to customize the SQL or even to ignore any rows that you choose not to update, insert or delete on the server. When using a TAstaClientDataSet connected to a Provider only Cached EditMode is supported. After Post editmode is not supported but posting each row change to the server can be simulated by calling ApplyUpdates in the AfterPost event. When an AstaClientDataSet's SQLGenerated location is changed to gsServer the AstaClientDataSet is automatically put in Cached Edit Mode. The Edit Mode property editor is not functional when using TAstaProviders.
TAstaProviders can also be used to monitor table changes on the server and those changes can be broadcasted to interested clients.
Any TAstaProviders present on ASTA server data modules can be seen by TAstaClientDataSets using the ProviderName property. When a ProviderName is chosen, any parameters present on the TAstaProvider will be streamed back to the client. If the TDataSet attached to the TAstaProvider is of type TParams this will happen automatically, otherwise you would have to code the Providers Param helper events. To support TAstaProviders, you must remember to register the datamodule(s) of your ASTA server.