A DELPHI three-tier example, to share the service side a DATASETPROVIDER, at least for two tables at the same time (such as a purchase order)
Have to say a DATASETPROVIDR on service only, don't make it a table put a DATASETPROVIDER this impossible in practice.

CodePudding user response:

New, modify, delete, query

CodePudding user response:

MIDAS don't want to do this, or just get it,

CodePudding user response:

Do DATASNAP

CodePudding user response:

MIDAS fix a

CodePudding user response:

A table with a DATASETPROVIDER affirmation is unscientific, if 100 tables, it should put remoteData 100 Databaseprovider, too large and spectacular, if they are dynamically generated, looks like is also very strange

CodePudding user response:

Hope to share,

CodePudding user response:

DELPHI three-tier server-side Shared a few DATASETPROVIDER commonly, usually one for temporary calls, setting up a few to open several tables at the same time,