Delphi Programming Diary - Jitendra Kumar

TFDMemTable FDMemTable is FireDAC dataset component that supports in memory table functionality. By using FDMemTable we can store data in a table format in local memory. We don’t need any database connection for this. We just need to add fields with definitions. Then we can create the table and add, edit, delete records. If we are only using FireDAC, then FDMemTable should be used only when we have memory-only data. And also in some special cases; for example, you can load CSV file into FDMemTable, then use LocalSQL to query this CSV data. Lets create the in-memory dataset. Var    FDMemTable1 : TFDMemTable; ……….. with FDMemTable1.FieldDefs do begin    Add(‘EmpID’, ftInteger, 0, True);    Add(‘EmpName’, ftString, 50, False);     CreateDataset;     Open; end; Or with FDMemTable1.FieldDefs.AddFieldDef do begin   Name := 'EmpID';   DataType := ftInteger;   Required := True; ...

What is cloud computing? "Cloud Computing"refers to the on-demand delivery of IT resources and applications via the Internet with pay-as-you-go pricing. You can think of the cloud services as a large scale, publicly accessible collection of compute, storage and networking resources. These are allocated via web service calls using HTTP protocol. In other words it is a „programmable data center” that your applications can integrate with. Cloud Computing providers such as Amazon Web Services own and maintain data centers across the globe with the network-connected hardware required for these application services, while you provision and use only what you need.  Cloud Computing in Delphi RAD Studio provides Cloud components, which allow you to easily use cloud services from Amazon and Microsoft Azure. RAD Studio provides a framework that allows you to build cloud services and easily connect to your back-end services and databases. With the RAD Studio RAD Cloud deployment,...

In my last blog I explained how to migrate from ADO to FireDAC . Here I will show you how to migrate a client-server application using AnyDAC to the FireDAC . Migration from Anydac to FireDAC is very easy in compare to other migration as after acquisition of AnyDAC by Embercadero they renamed it to FireDAC. So most of functionalities are same but naming are different. Difference The API was renamed, including new unit names and new API prefixes. 1. For Class Names the name prefix changed from TADxxxxx to TFDxxxxx etc. 2.  For FireDAC components, the name prefix changed from TADXxxx to TFDXxxx. 3. For global functions, the name prefix changed from ADXxx to FDXxx. 4. For exception classes, the name changed from EADXxx to EFDXxx. 5. For Units, hierarchical namespaces are now implemented. Unit Names are changed from uAD to FireDAC. For examples: uADCompClient -> FireDAC.Comp.Client, uADStanOption -> FireDAC.Stan.Option, uADPhysIB -> FireDAC.Phys.I...